Development record
itd-82 requires a remedy on every new issue; the brief's acceptance criterion has /abcd:capture "< text>" alone produce a structured issue.
itd-82 requires a remedy on every new issue; the brief's acceptance criterion has /abcd:capture "< text>" alone produce a structured issue.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-82-drain-ledger-triage.md:44— "and requires it of every new issue (ruling BX3 of 2026-09-29)" - End B:
.abcd/development/brief/01-product/01-press-release.md:43— "the user runs/abcd:capture "<text>", when the command completes"
itd-82 says capture gains the remedy field 'and requires it of every new issue (ruling BX3 of 2026-09-29)'. The brief press release's acceptance criterion begins: Given 'the user runs /abcd:capture "<text>", when the command completes', then a structured issue exists in open/. No remedy is supplied in that criterion. Under itd-82's rule that invocation is refused, so the criterion cannot pass as written.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 200.
Frontmatter
| id | iss-2610262031575425 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262031575425-itd-82-requires-a-remedy-on-every-new.md
open on GitHub ↗ · commit history ↗
References1
- itd-82`abcd drain` fixes the issues that need no decision, and hands the rest back by kindrelated