Roadmap

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

When a candidate release is accepted:

1. add the release to docs/01-milestones.md
2. create its version architecture document under docs/arch/
3. add its epic map under docs/02-epics.md
4. add its PBIs under docs/03-pbis.md, continuing from the next permanent identifier
5. move any durable decision into an ADR when there were meaningful alternatives

Contents

• V0 candidate roadmap, a candidate path from v0.3.0 through v0.7.0