Development record
Phases are history on the scope page, yet the intent chapter defines planned/ as scoped into a roadmap phase
Phases are history on the scope page, yet the intent chapter defines planned/ as scoped into a roadmap phase
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/01-product/04-scope.md:3— "The phase documents underroadmap/phases/are history." - End B:
.abcd/development/brief/04-surfaces/05-intent.md:12— "a committed capability, scoped into a roadmap phase and awaiting its Go build"
04-scope states the phase documents under roadmap/phases/ are history (the phase was retired), while 05-intent defines a planned/ intent as one scoped into a roadmap phase whose spec_id is set once the spec layer schedules it in Phase 4, although its own plan step mints the spec at planning. A planned intent cannot be scoped into a unit the record has retired.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 30.
Frontmatter
| id | iss-2610262030401652 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262030401652-phases-are-history-on-the-scope-page-yet.md
open on GitHub ↗ · commit history ↗