Development record
itd-1 says reviews of implementations return SHIP / NEEDS_WORK / MAJOR_RETHINK; the build's implementation reviewers return SHIP or FIX FIRST.
itd-1 says reviews of implementations return SHIP / NEEDS_WORK / MAJOR_RETHINK; the build's implementation reviewers return SHIP or FIX FIRST.
A terminology drift (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/disciplines/itd-1-acceptance-gates.md:47— "(SHIP/NEEDS_WORK/MAJOR_RETHINK) which score changes/runs" - End B:
.abcd/development/brief/04-surfaces/34-build.md:696— "stating one verdict of its role (SHIPorFIX FIRST"
itd-1 fixes one set of review verdicts, kept separate from criterion verdicts, for reviews of plans, implementations and completions: SHIP / NEEDS_WORK / MAJOR_RETHINK. In 34-build the validators review a lane's implementation, and the loop reads one verdict per role: SHIP or FIX FIRST. The two documents give different words for the same set of verdicts, so a reader built from itd-1 would reject what the build's reviewers return.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 709.
Frontmatter
| id | iss-2610262037142878 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262037142878-itd-1-says-reviews-of-implementations.md
open on GitHub ↗ · commit history ↗
References1
- itd-1Every Intent Has Acceptance Criteria; Every Audit Verifies Themrelated
mentions1
- iss-2610262038399413itd-1 says the SHIP/NEEDS_WORK/MAJOR_RETHINK review verdicts score plan and implementation reviews; 01-agents limits them to a packed lifeboat