86edb16947
Aligns mosaic.config tier vocabulary with the federation PRD: - Adds `federated` to the tier enum (Postgres + Valkey + pgvector) - Renames `team` → `standalone` in StorageTier / GatewayStorageTier - Keeps `team` as a deprecated alias that warns to stderr and maps to standalone - Adds DEFAULT_FEDERATED_CONFIG (port 5433, pgvector memory) - Corrects DEFAULT_STANDALONE_CONFIG.memory to keyword (PRD line 247) - Wizard interactive promptTier offers local/standalone/federated - Wizard headless env path now hard-rejects unknown MOSAIC_STORAGE_TIER values with a message naming all three valid tiers - Interactive DATABASE_URL pre-fill is tier-aware: standalone→5432, federated→5433 - 10 new unit tests for the validator + 3 new wizard headless tests No new behavior beyond the enum and defaults — pgvector enforcement, tier-detector, and docker-compose overlays land in FED-M1-02..04. Refs #460 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 | in-progress | Kick off W1 / FED-M1 — federated tier infrastructure | Session 16 (2026-04-19): FED-M1-01 in-progress on `feat/federation-m1-tier-config` |
|
||
| 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
|