roadmap-phaseslisted

<!-- roadmap-phases-version: 3 --> # Roadmap phases ## What this is, and what it is not **Rolling wave planning.** Detailed planning is limited to the work about to begin; later work is elaborated as uncertainty falls. The method exists because plans drift: writing every phase's plan up front produces plans that are wrong by the time they are read, and filing every ticket up front produces tickets for work the project has since decided against. It is **not project management**. No dates, no estimates, no burndown, no reporting. It answers four questions and refuses four mistakes, and a fifth of either is how it becomes something nobody runs. ## Source of truth `docs/roadmap.md` owns **which phases exist and what state each is in**. The host owns **which phase each ticket is in**, as the milestone field. These are different facts, so neither store duplicates the other and there is nothing to drift. Never record a ticket's phase in the roadmap, and never record a phase's existence only on the host. ## The four states | state | plan required | milestone | tickets may be assigned | meaning | |---|---|---|---|---| | `planned` | no | open | **yes** | declared and ordered, not started: a bucket | | `open` | **yes** | open | yes | in progress | | `done` | yes | closed | yes (all closed) | finished, closed in both places | | `backlog` | no | open | yes | the permanent holding phase; never closes | **`planned` to `open` is what makes "the plan is written at the start" mechani