Development record
The naming register marks the PRD-freeze vocabulary as machinery abcd neither ships nor plans; the intent chapter specifies it as a later-phase plan front end
The naming register marks the PRD-freeze vocabulary as machinery abcd neither ships nor plans; the intent chapter specifies it as a later-phase plan front end
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/02-constraints/04-naming.md:162— "Some names entered this register from the retired predecessor implementation and describe machinery abcd neither ships nor plans" - End B:
.abcd/development/brief/04-surfaces/05-intent.md:485— "The later-phase PRD-freeze front end for planning runs this ordered sequence"
04-naming marks frozen_content_hash, planning_attempt_id, prd_grandfathered and the planning-attempt modes as predecessor vocabulary for machinery abcd neither ships nor plans, while 05-intent sets out a later-phase PRD-validating and freezing front end for plan that computes frozen_content_hash and writes planning_attempt_id. The same machinery cannot be both unplanned and a later phase.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 60.
Frontmatter
| id | iss-2610262030547982 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262030547982-the-naming-register-marks-the-prd-freeze.md
open on GitHub ↗ · commit history ↗