Development record
The brief at .abcd/development/brief/04-surfaces/05-intent.md:571-572 says record-only is 'the default, and today's behaviour' and that an absent audit_mode key resolves to record-only, in a section not marked staged. No shipped code reads audit_mode or audit_budget (no match outside tests in internal/ or cmd/), and the backing intent itd-50 is in intents/planned/.
issueresolvedminoriss-2610160608394392
The brief at .abcd/development/brief/04-surfaces/05-intent.md:571-572 says record-only is 'the default, and today's behaviour' and that an absent audit_mode key resolves to record-only, in a section not marked staged. No shipped code reads audit_mode or audit_budget (no match outside tests in internal/ or cmd/), and the backing intent itd-50 is in intents/planned/.
Frontmatter
| id | iss-2610160608394392 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610160608394392-the-brief-at-abcd-development-brief.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610160855131633The brief's staged audit-loop section (05-intent.md, the per-intent audit_mode and audit_budget keys) and 05-internals/03-configuration.md:353-363 still describe the audit loop as a per-intent mode, while itd-50 records that on 2026-09-21 the loop was re-scoped to the last stage of abcd build, not a per-intent mode; the staged text contradicts the intent it cites. Found while fixing iss-2610160608394392, 2026-10-16.
- itd-50The Audit Loop Drives An Intent To Acceptance — Or Calls For A Replan