Control room · Founders & PMs
Keep every initiative decision-ready.
This is the calm surface for partners: watch the swarm’s progress, confirm which calls you owe, and rally the next move without digging through threads. Decisions, tasks, and documents stay in lockstep so you can brief stakeholders with confidence.
Initiatives
Data wiring
Fetched from /organizations/:org/initiatives and driven via NEXT_PUBLIC_DEFAULT_ORGANIZATION_ID.
Create initiative
Give your swarm a new mission
Title the initiative, outline its goal, add context, then jump straight into the workspace.
Developer setup
Still wiring systems? You can also seed initiatives via POST /api/v1/organizations/11111111-1111-1111-1111-111111111111/initiatives or by setting NEXT_PUBLIC_DEFAULT_ORGANIZATION_ID and calling the API directly.
Swarm ask (manual)
Builder shortcut
Paste an initiative ID, type a prompt, and the Next.js app will call POST /initiatives/:id/swarm/ask.
Responses are structured per the Swarm spec: answer, proposed decisions/tasks, agent chips.
Document Library
Stage the research you trust—board updates, discovery notes, exports—so the swarm can cite hard evidence when it proposes decisions.
Recent Documents
1 total- readytext/plain
Documents automatically move from processing to ready; stay with the partner thread while we prep the evidence in the background.
Developer ingestion tips
Need to monitor the worker locally? Run make worker to ingest files and stream logs while documents flip to ready.
Next steps
- Pipe recent decisions/tasks into the right-hand context panel (per UX spec D9).
- Swap the Echo-based coordinator with your real multi-agent prompts + provider wiring.
- Plumb document ingestion status and GitHub scans once integrations land.
Builder references
Specs live in `/references`. Keep this UI opinionated: one partner, many specialists.