Step 1: Roadmap view. High-level initiatives with rolled-up status. Each row expands to show phases and children. Click any row to drill in. user expands "Vision Tracker" then clicks the Specification phase
Compose Roadmap
Vision Tracker 6/18 done
in progress ›
● Planning complete
● Specification 7 decisions (2 approved) in progress click
● Architecture planned
● Implementation planned
Agent Monitoring 1/5 done
in progress ›
Persistence Connector 0/8 done
planned ›
Git/File Connector 0/4 done
planned ›
Standalone App 0/6 done
planned ›
Step 2: Specification phase. User clicked "Specification" under Vision Tracker. All children of this phase shown as expandable rows — decisions, specs, tasks. Same uniform pattern. Click any row to expand inline. user clicks D1
Roadmap›Vision Tracker›Specification
design Vision Tracker — Specification Phase 2/9 approved in progress
9 design decisions to make before planning can begin. 2 approved so far. Spec: product-realignment.md
Children 12
D1: Tracker is primary, markdown is generated planned › click
D2: New fields — priority, effort, planLink planned ›
D3: New entity types — feature, initiative approved ›
D4: Typed edges — blocks, informs, implements, supports planned ›
D5: Compose-loop reads tracker as work queue planned ›
Migrate vision-state schema to v2 planned ›
+ 6 more items...
Step 3: D1 expanded — shows options. Clicking D1 reveals: a Discuss button and artifact links at the top, then options A-D. Each option is expandable (D is open showing pros/cons). Compare options, then Approve one or Discuss the whole decision. user approves Option D
Roadmap›Vision Tracker›Specification
design Vision Tracker — Specification Phase in progress
Children 12
D1: How should project status be tracked? 4 options ›
Should the Vision Tracker replace ROADMAP.md as the single source of truth?
| product-realignment.md source doc D8: Markdown export depends on this
OPTIONS
A ROADMAP.md only — agent reads/writes natural language ›
B Vision Tracker only — queryable, filterable, visual ›
C Both, kept in sync — manual sync will fail ›
D Tracker primary, markdown generated recommended ›
Single source of truth in the tracker. Markdown snapshots generated on demand for git diffability. The agent's work queue IS the tracker — self-interest keeps it current.

#### Pros

- Single source of truth
- Agent self-maintains
- Git-diffable snapshots
- Queryable and visual

#### Cons

- Markdown easier to hand-edit
- Tracker must be reliable first
- Generated markdown may drift

user approves Option D
D2: New fields — priority, effort, planLink planned ›
D3: New entity types approved ›
+ 9 more items...
Step 4: D1 approved. User expands D4. D1 collapses and shows "approved". Now D4 is expanded — same pattern: rationale, pros/cons, linked dependencies. The linked item "D8: Markdown export" has a "depends on" edge — D4's typed edges enable D8's export logic. user clicks "D8: Markdown export" link
Roadmap›Vision Tracker›Specification
design Vision Tracker — Specification Phase in progress
Children 12 3 approved
D1: Tracker is primary, markdown is generated approved ›
D2: New fields — priority, effort, planLink planned ›
D3: New entity types approved ›
D4: Typed edges — blocks, informs, implements, supports planned ›
Rationale: Every connection between items needs a semantic type. Without typed edges, "this blocks that" and "this informs that" look identical — the graph can't drive scheduling or render meaningful dependency lines.

#### Pros

- Dependency-aware scheduling
- Graph renders different edge styles
- Enables the informs deliberation pattern
- Fixed set keeps complexity bounded

#### Cons

- Fixed types may not cover future needs
- More complex than generic connections
- Migration required for existing data

Linked items
Product realignment — DAG data model informs
D8: Markdown export depends on this click to drill in
Implement edge validation implements
+ 8 more items...
Step 5: Drilled into D8 via dependency link. User clicked "D8: Markdown export" inside D4's expansion. Breadcrumb grows. D8 has its own children, links, and actions. Same pattern at every depth. The "blocked by" link back to D4 shows the relationship. user clicks Back (or "Board" breadcrumb)
Roadmap›Vision Tracker›Specification›D8: Markdown Export
decision D8: Markdown export — on-demand ROADMAP.md generation planned
Generate ROADMAP.md from tracker state on demand. Human runs a command (or it auto-generates on commit), producing a git-diffable snapshot. Depends on D4 (typed edges) for rendering dependency info in the export.
Linked items 3
D4: Typed edges planned blocked by ›
D1: Tracker is primary approved informs ›
Build export CLI command planned implements ›
Step 6: Back to roadmap. Breadcrumb jump returns to the top level. Vision Tracker's Specification phase now shows "3 approved" (D1 was just approved). Progress bar updated. The full flow: roadmap → expand initiative → click phase → see decisions with options → approve → follow dependency → drill deeper → jump back.
Compose Roadmap
Vision Tracker 7/18 done
in progress ›
● Planning complete
● Specification 3 approved / 7 decisions in progress
● Architecture planned
● Implementation planned
Agent Monitoring 1/5 done
in progress ›
Persistence Connector 0/8 done
planned ›