Octa OS · target scenario

A typical workday with a Personal Agent

One chat runs the whole system — calendar, mail, company knowledge, and dev teams. No client work at this stage: we build Octa OS, infrastructure, and public sites. You decide — AI proposes and executes.

Personal Agent — L0 layer

Maja's planning persona plus Anna's interface warmth. Full access to calendar, mail, reminders, and knowledge — with the CEO's personal context.

Chatbot Octa Personal Agent
Calendar & mail No integration EventKit + Mail — triage and daily plan
Company knowledge No memory across sessions Knowledge + Qdrant — citations with paths
Dev teams Generic answers Delegation to automation, security, frontend, UX
Decisions No oversight HITL — approvals in the Review block

Workspace — conversation opens a view

Same UX as Octadecimal Workspace. Sidebar hash = panel: plan, board, wiki, retro.

Timeline — CEO Monday

From morning briefing to evening retro. No client delivery — focus on Octa OS and infrastructure.

07:00

Start — Body & Meaning

PA: "3 meetings, 12 emails, 2 reminders." CEO asks "What's important?" → summary from #Planning. Optional journal entry.

Maja Personal Agent + Calendar
08:30

Mail triage

Read-only mail — recruitment, infra, newsletters. PA proposes 2 "reply today" emails; tasks go to #Board.

09:00

#Planning — internal sprint

Weekly plan: embed MVP, macOS TCC audit, site fixes. Split across 4 dev teams. CEO approves in chat.

Maja Maja Wojciechowska — Chief of Staff
10:00–12:30

#Dev — deep work

CEO in Cursor with BMAD (Amelia, Winston). PA in background: embed watchdog, alerts only on failure. automation-team async on #Board.

13:30

#Review — HITL

Approval queue: merge PR, deploy site, policy tier change. security signs off on infra actions. Full audit trail.

Paweł Paweł Dąbrowski — Security Agent
17:00

#Retro — end of day

Summary: done / carry-over / tomorrow. CEO retro in 3 sentences → journal. Lessons learned promoted to knowledge base.

Katarzyna Katarzyna Mazur — Knowledge Agent

Active dev teams (MVP)

Four teams at launch — no client delivery. Each mapped to a profile from the Octadecimal team.

Wilson White

automation-team

Wilson White · Team Lead

Octa OS: embed, macOS MCP, octa CLI. Stack: octadecimal.pro + BMAD Amelia.

Paweł Dąbrowski

security

Paweł Dąbrowski · Security Agent

Tailscale, Authelia, policy tiers, AI Act. Review on every infra action.

Karolina Wieczorek

frontend-team

Karolina Wieczorek · Scrum Master

octadecimal.pro, .studio, .pl — public sites and Workspace.

Joanna Wiśniewska

ux-design-team

Joanna Wiśniewska · Business Advisor

Figma, design system, graphic assets for chat + hash UI.

Three memory layers in practice

Same model as on the homepage — mapped to internal Octa OS.

Layer 1

Team memory

BMAD session context and dev agents. Amelia remembers Octa OS stories across tasks.

Layer 2

Operational data

#Board, SQLite ledger, git, HITL Review queue — status of every PR and approval.

Layer 3

Company knowledge

Knowledge + Qdrant (#Wiki). Runbooks, research, ops docs — with path citations.

Good day metrics

< 15 minto daily plan from first chat message
< 5emails requiring manual CEO reply
100%HITL approvals in Review block
≥ 1meaningful canon commit (docs or code)

See it live

Workspace is the operational demo — chat, agent team, and SCRUM panels. This page describes the scenario we are building as Octa OS.

Enter Workspace