roadmap-buildlisted

# Roadmap: build one agents can execute Derived from rebuilding the PLUR roadmap, 2026-09-01 to 2026-09-03: five drifted documents to one validated source of 93 epics, 750 tasks, and three checks that catch regressions nobody would notice by reading. ## The one thing that matters **A roadmap is good when it is CHECKABLE, not when it is well written.** Every structural finding in that rebuild came from a script, never from reading the file: five areas built and invisible, eleven epics whose repo state contradicted them, fourteen agent-doable tasks parked behind a wrong flag. The prose was fine throughout. The prose is always fine. So: build the checks early and let them find the work. Do not write the whole roadmap and validate at the end. --- ## Phase 1 — Find what is already true Before writing anything, read the repos. Roadmaps decay by omission far more than by error, and the omissions are invisible from inside the document. ```bash gh issue list --repo <org>/<repo> --state open --limit 200 gh pr list --repo <org>/<repo> --state open git -C <repo> log --oneline -40 ls <repo>/src/<subsystem>/ # whole subsystems with no roadmap presence ``` **Expect to find work that shipped and work that is invisible.** In the PLUR rebuild: a provenance subsystem shipped in a repo the roadmap represented with two gated lines; eleven modules and three shipping tools with zero items; a 49-route admin surface with no coverage at all. Ask of every subsystem: *does the roadma