70f7c49336
Replace the install-ux-v2 manifest at docs/MISSION-MANIFEST.md with a top-level MVP rollup that tracks workstream-level missions instead of sub-mission scope. install-ux-v2 substantively shipped (IUV-M03 via PR #446 + releases 0.0.27 → 0.0.29) and is archived under docs/archive/missions/install-ux-v2-20260405/ with status corrected to complete. The new MVP manifest: - Names federation v1 as workstream W1 (planning-complete, 7 milestones, manifest at docs/federation/MISSION-MANIFEST.md, issues #460-#466) - Encodes three-surface parity (webUI/TUI/CLI) as cross-cutting requirement MVP-X1 so it cannot be silently dropped - Pre-stages additional workstreams (PRD-derived candidates) without committing execution capacity to them — scope creep is named and accommodated, not denied - Preserves Phase 0–8 history from sessions 1-14 in the scratchpad as prior execution context, not as the active control plane docs/TASKS.md becomes a rollup pointing at workstream task files; workers operating inside W1 read docs/federation/TASKS.md as their primary task source. Session 15 entry appended to docs/scratchpads/mvp-20260312.md (the existing scratchpad, active since 2026-03-13). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
41 lines
3.4 KiB
Markdown
41 lines
3.4 KiB
Markdown
# Tasks — MVP (Top-Level Rollup)
|
||
|
||
> Single-writer: orchestrator only. Workers read but never modify.
|
||
>
|
||
> **Mission:** mvp-20260312
|
||
> **Manifest:** [docs/MISSION-MANIFEST.md](./MISSION-MANIFEST.md)
|
||
>
|
||
> This file is a **rollup**. Per-workstream task breakdowns live in workstream task files
|
||
> (e.g. `docs/federation/TASKS.md`). Workers operating inside a workstream should treat
|
||
> the workstream file as their primary task source; this file exists for orchestrator-level
|
||
> visibility into MVP-wide state.
|
||
>
|
||
> **Status values:** `not-started` | `in-progress` | `done` | `blocked` | `failed`
|
||
|
||
## Workstream Rollup
|
||
|
||
| id | status | workstream | progress | tasks file | notes |
|
||
| --- | ----------------- | ------------------- | ---------------- | ------------------------------------------------- | --------------------------------------------------------------- |
|
||
| W1 | planning-complete | Federation v1 (FED) | 0 / 7 milestones | [docs/federation/TASKS.md](./federation/TASKS.md) | M1 task breakdown populated; M2–M7 deferred to mission planning |
|
||
|
||
## Cross-Cutting Tracking
|
||
|
||
These are MVP-level checks that don't belong to any single workstream. Updated by the orchestrator at each session.
|
||
|
||
| id | status | description | notes |
|
||
| ------- | ----------- | -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
|
||
| MVP-T01 | done | Author MVP-level manifest at `docs/MISSION-MANIFEST.md` | This session (2026-04-19); PR pending |
|
||
| MVP-T02 | done | Archive install-ux-v2 mission state to `docs/archive/missions/install-ux-v2-20260405/` | IUV-M03 retroactively closed (shipped via PR #446 + releases 0.0.27→0.0.29) |
|
||
| MVP-T03 | done | Land federation v1 planning artifacts on `main` | PR #468 merged 2026-04-19 (commit `66512550`) |
|
||
| MVP-T04 | not-started | Sync `.mosaic/orchestrator/mission.json` MVP slot with this manifest (milestone enumeration, etc.) | Coord state file; consider whether to repopulate via `mosaic coord` or accept hand-edit |
|
||
| MVP-T05 | not-started | Kick off W1 / FED-M1 — federated tier infrastructure | First execution task in MVP |
|
||
| MVP-T06 | not-started | Declare additional workstreams (web dashboard, TUI/CLI parity, remote control, etc.) as scope solidifies | Track each new workstream by adding a row to the Workstream Rollup |
|
||
|
||
## Pointer to Active Workstream
|
||
|
||
Active workstream is **W1 — Federation v1**. Workers should:
|
||
|
||
1. Read [docs/federation/MISSION-MANIFEST.md](./federation/MISSION-MANIFEST.md) for workstream scope
|
||
2. Read [docs/federation/TASKS.md](./federation/TASKS.md) for the next pending task
|
||
3. Follow per-task agent + tier guidance from the workstream manifest
|