ADR 0002: Roadmap threads, milestones and identifiers¶
- Status: Proposed; merging the pull request that carries this ADR records acceptance
- Date: 2026-10-08
- Owners: Roadmap owner (@fmuia) with the dev meeting
- Scope: the structure of
roadmap/, its identifiers and its work board; no package code
Decision summary¶
- Domain threads replace activity workstreams. The roadmap is organised by who carries the work, not by the kind of activity: Technical development, Agentic integration and governance, Business development and reach (proposed), and Lab operations and access. Each thread has one accountable owner and serves named outcomes.
- Milestones are conditions, not phases. Each thread declares milestones with their own completion tests. A milestone counts as reached only when the board snapshot shows its items done. Its position on a thread page is the owner's intended path; it is never a date, a sprint or a phase.
- Outcomes are data. The vision statement and each outcome (title,
statement, completion test, gaps closed) live in
roadmap.toml, so the renderer can show, per thread, the path from today to the outcomes it serves and the evidence-backed progress along it. - Thread-prefixed identifiers. Items are
TECH-01,AI-01,BIZ-01,OPS-01; decisions areDEC-01and up. Every migrated item and decision keeps its 2026-09 id aslegacy_id, and the renderer emits it as an alias anchor, so existing links resolve. No id is ever reused. - ClickUp is the work board (DEC-22, recorded 2026-10-08: proposed by
Krishn and agreed by the roadmap owner and organization admins; workspace
HSSM Ecosystem, Free plan). Git owns intent; ClickUp owns live state; no field is owned by both. The adapter is specified inplans/roadmap-threads-and-clickup-sync.md.
Why¶
The six workstreams of the 2026-09 roadmap mixed two axes: four were kinds of activity (Stabilize, Deliver, Verify, Throughput) and two were domains (Connect, Access and navigation). Nobody could own "Stabilize" across every domain, so the question of who owns each workstream stayed open; the vision and outcomes were written by domain and could not be rendered against the workstreams; and the marketing and business-development proposals of 2026-09-30 had no place in the scheme at all. The stakeholder review of 2026-09-29 had already removed horizons and the critical path because hand-set stages go stale; milestones defined as evidence-tested conditions keep that decision intact while giving each thread a readable path.
Consequences¶
- Links by former id keep working through alias anchors; links by file name
(
roadmap/items/A1-…) break, and none exist outside the roadmap. - The weekly-report index on the open report branches
(
.claude/skills/dev-weekly-report/roadmap_index.py) accepts only ids matching[A-Z][0-9]{1,3}. It must accept[A-Z]{2,5}-[0-9]{2,3}before those branches merge, or the deck will group no roadmap items. - Threads marked
adoption = "proposed"and their outcomes await the dev meeting under DEC-18; their milestones may be empty until then. - The generated pages gain one page per thread under
roadmap/threads/.
Identifier map¶
| Former | New | Thread | Milestone |
|---|---|---|---|
| A1 | TECH-01 | Technical development | Stable |
| A2 | TECH-02 | Technical development | Stable |
| A3 | TECH-03 | Technical development | Stable |
| A4 | TECH-04 | Technical development | Stable |
| A6 | TECH-05 | Technical development | Stable |
| A8 | TECH-06 | Technical development | Stable |
| A7 | TECH-07 | Technical development | Released |
| B3 | TECH-08 | Technical development | Released |
| B4 | TECH-09 | Technical development | Released |
| B1 | TECH-10 | Technical development | Complete model surface |
| B2 | TECH-11 | Technical development | Complete model surface |
| B6 | TECH-12 | Technical development | Complete model surface |
| B7 | TECH-13 | Technical development | Complete model surface |
| B8 | TECH-14 | Technical development | Complete model surface |
| B9 | TECH-15 | Technical development | Complete model surface |
| B10 | TECH-16 | Technical development | Complete model surface |
| C1 | TECH-17 | Technical development | Trustworthy artifacts |
| C2 | TECH-18 | Technical development | Trustworthy artifacts |
| C3 | TECH-19 | Technical development | Trustworthy artifacts |
| C4 | TECH-20 | Technical development | Trustworthy artifacts |
| C6 | TECH-21 | Technical development | Trustworthy artifacts |
| B5 | TECH-22 | Technical development | Trustworthy artifacts |
| B11 | TECH-23 | Technical development | Trustworthy artifacts |
| E1 | AI-01 | Agentic integration and governance | Proposed |
| E6 | AI-02 | Agentic integration and governance | Proposed |
| E7 | AI-03 | Agentic integration and governance | Proposed |
| A5 | AI-04 | Agentic integration and governance | Proposed |
| C5 | AI-05 | Agentic integration and governance | Proposed |
| E2 | AI-06 | Agentic integration and governance | Shadow |
| E4 | AI-07 | Agentic integration and governance | Shadow |
| D2 | AI-08 | Agentic integration and governance | Shadow |
| — (new) | AI-09 | Agentic integration and governance | Shadow |
| E3 | AI-10 | Agentic integration and governance | Live behind approvals |
| E5 | AI-11 | Agentic integration and governance | Live behind approvals |
| F1 | OPS-01 | Lab operations and access | Reachable |
| F2 | OPS-02 | Lab operations and access | Reachable |
| F3 | OPS-03 | Lab operations and access | Reachable |
| F4 | OPS-04 | Lab operations and access | Reachable |
| F5 | OPS-05 | Lab operations and access | Reachable |
| D1 | OPS-06 | Lab operations and access | Governed delivery |
| D3 | OPS-07 | Lab operations and access | Governed delivery |
| D4 | OPS-08 | Lab operations and access | Governed delivery |
| D5 | OPS-09 | Lab operations and access | Governed delivery |
| D6 | OPS-10 | Lab operations and access | Governed delivery |
| D7 | OPS-11 | Lab operations and access | Governed delivery |
| F6 | OPS-12 | Lab operations and access | Navigable |
| F7 | OPS-13 | Lab operations and access | Navigable |
| F8 | OPS-14 | Lab operations and access | Navigable |
| F9 | OPS-15 | Lab operations and access | Navigable |
| F10 | OPS-16 | Lab operations and access | Navigable |
Decisions D-01 through D-22 became DEC-01 through DEC-22 with the same numbers.