Roadmap
| Document version | Date | Summary |
|---|---|---|
| v1 | 2026-07-24 | Add a place for non-authoritative release direction notes |
Status: Planning notes
Authority: None. Roadmap documents are not product commitments and must not justify implementation by themselves.
This directory records candidate release direction before it is accepted into the source of truth. It preserves useful planning context that is larger than one idea, but less authoritative than milestones, epics, PBIs, version architecture, or ADRs.
Rules
- a roadmap entry may describe a likely release sequence, rationale, trigger, and open question
- a roadmap entry does not create an active release
- a roadmap entry does not reserve a version number permanently
- accepted work must still move into
docs/01-milestones.md,docs/02-epics.md,docs/03-pbis.md, and a version architecture document before implementation - conflicting product specification, architecture, ADR, milestone, epic, or PBI text wins
Promotion Path
A candidate is promoted through the release planning process, which
selects the candidate, adds it to docs/01-milestones.md, accepts its version architecture document
under docs/arch/, opens its epic map with a dependency diagram in docs/02-epics.md, and adds its
PBIs to docs/03-pbis.md under the permanent identifier sequences. A durable decision with real
alternatives becomes an ADR.
Roadmap documents describe candidate direction without tracking which release is currently open, so they do not need rewriting after every release.
Contents
- V0 candidate roadmap, the open candidate directions inside the V0 milestone