Development record
The configuration chapter stages itd-50's audit loop as a per-intent frontmatter mode, while itd-50 rules that the loop is build's last stage for every intent, not a per-intent mode
The configuration chapter stages itd-50's audit loop as a per-intent frontmatter mode, while itd-50 rules that the loop is build's last stage for every intent, not a per-intent mode
A premise contradiction (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-50-loop-toward-acceptance.md:98— "not a per-intent mode; every intent the run ships goes through it." - End B:
.abcd/development/brief/05-internals/03-configuration.md:417— "one intent can loop while another stays record-only"
The configuration chapter says the audit-loop mode and budget are elected per intent in the intent's own frontmatter (audit_mode, audit_budget default 3), so that one intent can loop while another stays record-only. itd-50's decisions of 2026-09-21 rule that the loop is not a per-intent mode: every intent a build run ships goes through it, and the round count is a per-run value (--fix-rounds, pace.fix_rounds, bundled 3). A builder following the brief would add per-intent frontmatter keys and a per-intent opt-in that the intent's own rulings replaced.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 864.
Deferral 2026-10-27
Deferred past v0.15.1: Deferred by the product thinker on 2026-10-27 (dcn-2610271112330536): the brief's single-home rewrite (dcn-2610271112339516, dcn-2610271112330235) rewrites or removes most of the passages this record quotes.
Frontmatter
| id | iss-2610262039297157 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | major |
.abcd/work/issues/open/iss-2610262039297157-the-configuration-chapter-stages-itd-50.md
open on GitHub ↗ · commit history ↗
References1
- itd-50The Audit Loop Drives An Intent To Acceptance — Or Calls For A Replanrelated
mentions3
- dcn-26102711123302352026-10-27 — The product thinker ruled on 2026-10-27 that the design brief shows the target design, in the present tense, with a status tag where a part is built, rather than the shipped state. With the ruling that behaviour lives in the command pages, the brief holds the product as aimed for and why, and the command pages hold what abcd does today. This reverses itd-147's currency rule, so a superseding ADR is owed, and the brief's checks are rebuilt around the status overlay.
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- dcn-26102711123395162026-10-27 — The product thinker ruled on 2026-10-27 that each abcd command's behaviour is written once, in its command page, which agents follow when they run it. The brief's chapter for the command keeps why the command exists, its trade-offs and why it refuses what it does, with its sub-verb table and generated appendix, and points to the command page for behaviour. The documentation-fidelity check moves to the command pages. This reverses the behaviour half of adr-2609231028044006 and invariant 18, so a superseding ADR is owed.