Roadmap
This describes intended scope, not release readiness. Phase numbers are planning milestones, not release versions. No dates or rollout commitments are promised.
| Phase | User outcome and deliverable | Exit evidence |
|---|---|---|
| 0 — Feasibility and contracts | Native capability inventory, shared client contracts, concrete work/reply/consultation/artifact contracts, reviewed conversational TUI prototype | Reproducible baseline; exact-version native evidence or explicit unavailable results; reviewed terminal interaction and send/stream limits |
| 1 — Complete coordination | Explicit current work, atomic StartWork, peer discovery, correlated question/answer/wait/cancel, durable return delivery, Needs You in TUI and web | Real chats exchange replies across reconnect; strict rollback, competing claims, retry, cancellation/late-answer, restart, and concurrent TUI/web behavior pass |
| 2 — Controlled expert help | Profiles, user-initiated/approve-each/automatic-within-limits modes, frozen context, approvals, bounded runner, status/cancel/results | Atomic allowance accounting, no automatic duplicate of a possibly launched call, retained uncertain reservations, isolation failures denied, revocation/cancellation evidence |
| 3 — Reviewed work and shared workspace | Exact research submissions, safe code evidence, explicit reviewer workflow, linked helper/integration tickets, quiet channels, deliberate idea promotion, continuation | Wrong artifact, drift, stale or unauthorized review, and self-review cannot satisfy acceptance; only accepted work unblocks dependencies |
| 4 — Uncoached validation | Ordinary use across Claude, Codex, and Muse chats, with a smaller model and multiple worktrees | Named core workflows pass without procedural coaching; unauthorized grants, false read/completion labels, duplicate expert launches, or wrong-artifact acceptance block completion |
Cross-machine checkout locks and a hosted multi-user service are outside the local scope.
Current status
Section titled “Current status”Experimental and unreleased. No phase exit is claimed and no release has been cut. The compatibility table stays unverified until adapter contract fixtures for exact harness versions land. The original build brief (PRD revision 1.1) is absent from the checkout; conflicts against it must be resolved before accepting conflicting implementation.