3.2 KiB
Mission Manifest — Mosaic Mission Control Plane
Persistent document tracking scope, status, and handoff history for the combined PRD / mission / Kanban workflow.
Mission
ID: mission-control-plane-20260506
Statement: Combine Mosaic PRDy, coord, and Kanban into one durable workflow so an agent can move from feature idea to PRD to mission to task board and keep working across session rotation, compaction, and restarts with minimal context loss.
Phase: planning — MC-01 complete, MC-02 next
Current Milestone: MC-02
Progress: 1 / 6 milestones
Status: active
Last Updated: 2026-05-06
Parent Mission: None — new mission
Context
This mission exists because overnight autonomy breaks when the working session short-cycles. The system needs durable artifacts and a mechanical coordinator that can:
- keep a canonical PRD,
- atomize the PRD into board tasks,
- track mission state separately from the chat session,
- detect churn or compaction pressure,
- rotate to a fresh session, and
- re-enter from a structured handoff.
Operational convention: repo worktrees and long-lived working directories should use /src/<repo>-worktrees instead of /tmp.
Design references:
docs/mission-control/PRD.md— product requirementsdocs/mission-control/BOARD.md— feature discussion boarddocs/mission-control/TASKS.md— atomized execution plan
Success Criteria
- AC-1: A feature idea can be converted into a PRD, mission, and task board.
- AC-2: The coordinator can load a mission and its board from durable storage.
- AC-3: The coordinator can detect short-cycling and rotate sessions automatically.
- AC-4: A rotated session can resume from a handoff packet without manual re-prompting.
- AC-5: The board remains traceable back to the PRD user stories.
- AC-6: Operators can inspect mission state, task state, and latest handoff from one place.
- AC-7: The system can run overnight without losing the mission goal.
Milestones
| # | ID | Name | Status | Branch | Started | Completed |
|---|---|---|---|---|---|---|
| 1 | MC-01 | PRD + mission schema foundation | in-progress | docs/mission-control-* | 2026-05-06 | — |
| 2 | MC-02 | Mission runtime model | not-started | — | — | — |
| 3 | MC-03 | Board atomization and task linkage | not-started | — | — | — |
| 4 | MC-04 | Short-cycle detector and rotation engine | not-started | — | — | — |
| 5 | MC-05 | Handoff generation and re-entry | not-started | — | — | — |
| 6 | MC-06 | Operator surface and E2E validation | not-started | — | — | — |
Budget
| Milestone | Est. tokens | Parallelizable? |
|---|---|---|
| MC-01 | 16K | No |
| MC-02 | 20K | No |
| MC-03 | 24K | Mostly after MC-01 |
| MC-04 | 20K | After MC-02 |
| MC-05 | 18K | After MC-04 |
| MC-06 | 26K | After MC-04/05 |
| Total | ~124K |
Session History
| Session | Date | Runtime | Outcome |
|---|---|---|---|
| S1 | 2026-05-06 | hermes | PRD, board, task plan, mission manifest, and worktree convention drafted |
Next Step
Kick off MC-02: implement the durable mission runtime model and wire the mission state into the coordinator.