Development record
roadmap
Superseded on 2026-09-21 (adr-2609212115255771): the rendered Now / Next / Later status block on the
abcdboard and the site's Status page replaces the roadmap document and the word. See record-families.
The roadmap is .abcd/development/roadmap/: two things and
no others — phases/, the ordered build plan, and
rfcs/, where a proposal is argued before it becomes an ADR. It carries no dates and no
estimates. What has shipped is defined by which phases are complete and which intents sit in
shipped/.
Senses
| Sense | The one spelling | Where it lives |
|---|---|---|
| The folder: phase docs plus RFCs | the roadmap | development/roadmap/ |
| The live status render at that folder's README | the roadmap dashboard | roadmap/README.md |
The dashboard does not read the roadmap. This is the trap the word sets. The phase docs are editorial prose about sequence; the dashboard's per-spec truth is read live from the native spec store and from the intent buckets on disk, because hand-maintained counts drift the moment work ships. So "what the roadmap says" and "what the roadmap dashboard shows" answer different questions from different sources, and only the second is current by construction. Per-phase progress on the dashboard stays coarse and editorial for exactly that reason.
A phase doc carries no status. Status is never stored in a design doc (adr-5), so the dashboard is the only place a reader should look for state.
When to use
Use "the roadmap" for the folder and its contents when the subject is sequence — what is bundled into which phase, in what order, and why. Use "the roadmap dashboard" whenever the subject is current state.
When NOT to use
Do not use "roadmap" for the intent corpus: most intents are not phased, and an intent listed
in no phase doc's ## Scope is unscheduled, which is a valid state
(adr-34 makes scheduled
and planned orthogonal axes). Do not use it for a release timeline — a release version is
derived from what shipped, never an input that organises work.
Examples
- "The roadmap holds phases and RFCs; an accepted RFC produces an ADR."
- "The roadmap dashboard reads the native spec store, so its spec counts are whatever the store reports right now."
Related terms
Frontmatter
| term | roadmap |
|---|---|
| bounded_context | core |
| status | superseded |
| aliases | roadmap folder |
| definition | The sequencing folder .abcd/development/roadmap/, which holds the phase docs and the RFCs. Its README is the roadmap dashboard, a separate sense — a live status render that reads the native spec store and the intent buckets rather than the phase docs. |
.abcd/development/brief/glossary/core/roadmap.md
open on GitHub ↗ · commit history ↗