itd-50 describes the implementation-grain fix loop as SHIP/NEEDS_WORK; 34-build's validators return SHIP or FIX FIRST, and APPROVE, BLOCK or NEEDS-INPUT

itd-50 describes the implementation-grain fix loop as SHIP/NEEDS_WORK; 34-build's validators return SHIP or FIX FIRST, and APPROVE, BLOCK or NEEDS-INPUT

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

• End A: .abcd/development/intents/planned/itd-50-loop-toward-acceptance.md:47 — "Mirrors the implementation-grain SHIP/NEEDS_WORK fix-loop, lifted to the intent grain."
• End B: .abcd/development/brief/04-surfaces/34-build.md:704 — "did not pass (FIX FIRST, BLOCK, NEEDS-INPUT, a criterion NOT_MET)"

itd-50 models its intent-grain loop on an implementation-grain SHIP/NEEDS_WORK fix loop. In the build loop it would extend, 34-build names the verdicts that fail a round: FIX FIRST, BLOCK, NEEDS-INPUT, or a criterion NOT_MET. No validator there returns NEEDS_WORK. The verdict vocabulary that itd-50 assumes is not the one the shipped loop parses.

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