13 clusters grouped by code / data-model adjacency. A / B / C / D / K / M can run without the backend split. E / F / G / H / J cannot — that's the parallelism unlock. Click a card to expand.
28 surfaces where the design space is wider than the example. Grouped by cluster.
9 highest-leverage surfaces — one paragraph each on what "good" looks like. These are the ones worth aligning on before commitment.
Backbone track (PLATFORM dependency chain) + parallel frontend track. Phase 0 / A-fx / B-fx / C-fx / D-fx all sit alongside the backbone phase they share resources with.
Dependency chain (tight version)
- Phase 0 is pure polish, ship now
- Phase A gates B+ (FastAPI required for any non-browser surface; SQLite required for cross-surface read)
- Phase B gates C+ (provider abstraction required for non-Ollama; control plane required for cron + push)
- Phase C.5 (RAG) only needs B (embeddings ride the provider layer)
- Phase D needs tool-calling from C to be live
- Phase E needs FastAPI (A) + control plane (B)
- Phase F needs ~4 weeks of telemetry data (per PLATFORM §7)
15 things the inventory doesn't capture. Top 5 highlighted as actual gaps (vs. smaller adds).