roadmaplisted

# ROADMAP: single sequencing authority <HARD-GATE>An approved, commit-bound WhitePaper must exist; otherwise return to `brainstorm`. If ROADMAP work exposes a WhitePaper premise that must change, use `brainstorm` revision mode instead of redefining it here. ROADMAP must not contain R-AC IDs, quantitative requirement metrics, or executable test cases. It precedes Milestone requirements, so acceptance pictures stay qualitative.</HARD-GATE> ## Language and contract Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing contract. Use the active locale for artifact prose. Use `ROADMAP.md`, `type: roadmap`, `nature: normative`, and `status: draft` until approved. ## Create - Restate only the WhitePaper boundary and invariants needed for sequencing. - Define ordered Milestones with one qualitative objective, explicit **Milestone deliverables**, one **Milestone acceptance picture**, dependencies, and work state `not-started`. - Derive each deliverable from the approved WhitePaper and that Milestone's expected outcome; never infer ROADMAP deliverables backward from a downstream Goal. - Name what will exist at the end, not how well it must perform. Choose only the concrete objects appropriate to the Milestone: a specification, repository state, release, running network or environment, tool, report, ledger, or a realized product/operational E2E when that path itself is the final result. The acceptance picture states qualit