Development record
05-intent names the phase plan as the canonical build order, but 08-abcd orders what gets built by build next's pick order.
05-intent names the phase plan as the canonical build order, but 08-abcd orders what gets built by build next's pick order.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/05-intent.md:74— "ID number is not an execution-order guarantee — the canonical build order is the phase plan at" - End B:
.abcd/development/brief/04-surfaces/08-abcd.md:338— "read in build next's pick order (itd-2609211116005482): each READY intent is"
05-intent says the canonical build order is the phase plan at roadmap/phases/, although elsewhere it records that phases are retired. 08-abcd says the head of Now and the Next list are read in build next's pick order (readiness score, then age), and that the head is the intent the pick would start. The build order cannot be both the phase plan and the pick order.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 400.
Frontmatter
| id | iss-2610262033248041 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033248041-05-intent-names-the-phase-plan-as-the.md
open on GitHub ↗ · commit history ↗
mentions4
- iss-2610262033451641The intent chapter names the phase plan under roadmap/phases/ as the canonical build order; the glossary marks phase superseded, with sequencing now dependencies plus the lifecycle shelves.
- iss-2610262034479574The intent chapter names the phase plan as the canonical build order; itd-24 records that phases are retired.
- iss-2610262034508480The intent surface page names the roadmap phase plan as the canonical build order; itd-2609211913453478 retires phases and puts sequencing in dependencies and the lifecycle shelves.
- itd-2609211116005482`abcd build next` picks the readiest planned intent itself, and writes down why