This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

The reserved review-verdict enum is SHIP/NEEDS_WORK/MAJOR_RETHINK, but the build loop parses SHIP/FIX FIRST and APPROVE/BLOCK/NEEDS-INPUT as review verdicts

issuewontfixminoriss-2610262030597155

The reserved review-verdict enum is SHIP/NEEDS_WORK/MAJOR_RETHINK, but the build loop parses SHIP/FIX FIRST and APPROVE/BLOCK/NEEDS-INPUT as review verdicts

A terminology drift (severity minor) found by the cross-document consistency pass.

  • End A: .abcd/development/brief/02-constraints/04-naming.md:187 — "Review verdicts ∈ {SHIP, NEEDS_WORK, MAJOR_RETHINK} | Carmack-style review verdicts"
  • End B: .abcd/development/brief/04-surfaces/34-build.md:696 — "stating one verdict of its role (SHIP or FIX FIRST; APPROVE, BLOCK or NEEDS-INPUT)"

The naming register lists review verdicts as a controlled enum of exactly SHIP, NEEDS_WORK and MAJOR_RETHINK. The build chapter has the loop read each reviewer's one verdict as SHIP or FIX FIRST (and APPROVE, BLOCK or NEEDS-INPUT), tokens the register does not hold. Either the enum is not the closed list of review verdicts, or the loop parses verdicts outside it. A builder working from the register would reject the loop's tokens.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 70.

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262030580466. Same A end and same root cause: the register's closed review-verdict list is lifeboat-only while the build loop parses SHIP/FIX FIRST and APPROVE/BLOCK/NEEDS-INPUT, which 01-agents.md already calls each role's own words.

Frontmatter

idiss-2610262030597155
typeissue
lifecyclewontfix
severityminor

mentions2