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:
2.**Single-repo sharpening** — adopt the best execution/workflow ideas from pi-mono, gsd-2, Claude Code, Codex, Aider, and Plandex where they strengthen Forge
3.**Autonomous reliability** — evidence, recovery, verification, and self-improvement loops
4.**Surface coherence** — CLI, TUI, docs, and workflow language all reflect the same UOK-driven model
5.**ACE convergence prep** — keep concepts compatible with ACE Coder without turning Forge into the multi-repo system
**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.