Development record
The intent chapter says the audit loop was re-scoped into the last stage of the build, while the configuration chapter still stages it as a per-intent mode.
The intent chapter says the audit loop was re-scoped into the last stage of the build, while the configuration chapter still stages it as a per-intent mode.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/05-intent.md:578— "This per-intent shape predates itd-50's 2026-09-21 re-scope, which makes the loop the last stage ofabcd buildrather than a per-intent mode" - End B:
.abcd/development/brief/05-internals/03-configuration.md:415— "Audit-loop mode and budget (staged: itd-50) are elected per intent, in the intent's own frontmatter rather than inconfig.json"
05-intent records that the per-intent audit-mode shape predates a re-scope that makes the loop the last stage of abcd build rather than a per-intent mode. 03-configuration presents the staged audit-loop mode and budget as chosen per intent, in each intent's own frontmatter. Anyone building the loop from the configuration chapter would build the shape the intent chapter calls superseded.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 418.
Frontmatter
| id | iss-2610262033328180 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033328180-the-intent-chapter-says-the-audit-loop.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-50The Audit Loop Drives An Intent To Acceptance — Or Calls For A Replan