2.9 KiB
2.9 KiB
BUILD_PLAN → Milestone Map
Every BUILD_PLAN.md tier item mapped to a milestone. Rule D015: every new milestone must cite which BUILD_PLAN tier/item it implements.
This file answers where work belongs, not whether code is done. "Mapped" means a BUILD_PLAN item has a milestone/slice home. It does not mean the implementation is verified in the current repo.
Mapping vs. code truth
- Mapped — the item has a milestone/slice destination.
- Verified in code — the behavior exists in the repo and has evidence/tests/artifacts.
- Open — still planned or partially folded in, but not yet verified as complete.
- Deferred — intentionally out of the active plan.
High-level milestone direction
These are the strategy bands above the itemized mapping:
- Core foundation — UOK, purpose-driven TDD, eight-field PDD gate, repo-local state
- Single-repo sharpening — adopt the best execution/workflow ideas from pi-mono, gsd-2, Claude Code, Codex, Aider, and Plandex where they strengthen Forge
- Autonomous reliability — evidence, recovery, verification, and self-improvement loops
- Surface coherence — CLI, TUI, docs, and workflow language all reflect the same UOK-driven model
- ACE convergence prep — keep concepts compatible with ACE Coder without turning Forge into the multi-repo system
Tier 0 — Pi-mono ports → M006
Tier 0.5 — gsd-2 ports → M006 + M007
All mapped. See BUILD_PLAN.md for item-level status.
Tier 1 — ESSENTIAL → ALL MAPPED
| Item | Milestone | Slice | Status |
|---|---|---|---|
| 1.1 Vault secret resolver | M017-yf67h6 | S01-S03 | ⬜ NEW |
| 1.2 Singularity Memory integration | M017-jpw5jo | S01-S03 | ⬜ NEW |
| 1.3 Schema reconciliation (spec rewrite) | M013 | S12 | ⬜ Folded in |
| 1.4 Config schema alignment | M013 | S13 | ⬜ Folded in |
Tier 2 — STRONG → ALL MAPPED
| Item | Milestone | Slice | Status |
|---|---|---|---|
| 2.1 Persistent agents v1 | M012 | S01-S05 | ⬜ |
| 2.2 Doc-sync sub-step | M009 | S08 | ⬜ |
| 2.3 Intent chapters | M013 | S08 | ⬜ |
| 2.4 PhaseReview 3-pass | M016 | S01-S02 | ⬜ |
| 2.5 turn_status marker | M013 | S09 | ⬜ |
| 2.6 last_error cap | M013 | S10 | ⬜ |
| 2.7 cost_micro_usd | M013 | S11 | ⬜ |
Tier 3+ → Deferred by design
Summary
| Tier | Mapped | Gap |
|---|---|---|
| Tier 0 | 10 (M006) | 0 |
| Tier 0.5 | 17 (M006+M007) | 0 |
| Tier 1 | 4 (M017×2, M013×2) | 0 |
| Tier 2 | 7 (M012, M009, M013, M016) | 0 |
| Tier 3+ | 0 | deferred |
Zero mapping gaps. Every BUILD_PLAN tier item is either mapped to a milestone or explicitly deferred.
That does not mean zero implementation gaps. Open TODO, NEW, and ⬜ markers in BUILD_PLAN.md, this map, and milestone artifacts still represent real work until they are reconciled against code evidence.