Maia coordinator

Status: Project context notes are implemented; autonomous coordinators are planned (ROADMAP R3, R4, R8, R9a, R10).

Coordinator work is Node-owned. The CLI and @maiaos/sdk are the interface; Desktop, mobile and voice only project those operations. There is no standalone web control app and no second scheduler.

Implemented: Project context notes

project.context.record, project.context.list and project.context.show persist user-authored notes that outlive Sessions. The authenticated CLI --body-stdin is the confirmation. Notes are not Workspace rules, not .maia intent and not the Project page.

maia project context record --project <project-id> --body-stdin [--command-id <id>]
maia project context list --project <project-id> [--limit <1..100>] [--after <cursor>]
maia project context show <note-id>

Planned: scoped coordinators

Maia, Workspace and Project coordinators share one scoped implementation (LLM + Jev) with separate owners, context, grants and budgets (decision); execution workers stay LLM-only. The contracts live in:

• Swarm routing and feedback: roles, bounded plans, parallel work, acknowledgements and attention.
• Node context and journals: authoritative records, scoped context preparation and linked journals.
• Presentation runtime: SDK-driven json-render views and admitted text and voice delivery.

Today an external brain (Claude Code or Codex) coordinates workers through the public CLI, MCP and the maia-orchestration Skill (coordination).