Development record
itd-5 relies on intent-auditor's single-document role checking delivery against itd-5's own criteria; the audit refuses any record in disciplines/
itd-5 relies on intent-auditor's single-document role checking delivery against itd-5's own criteria; the audit refuses any record in disciplines/
A sequencing impossibility (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/disciplines/itd-5-prompt-quality-additions.md:102— "checks delivered reality against this discipline's acceptance criteria when each agent spec ships" - End B:
.abcd/development/brief/04-surfaces/05-intent.md:326— "Takes a shipped intent and nothing else: a record still indrafts/,planned/,disciplines/orsuperseded/is refused by name"
itd-5, a discipline, says the auditor's single-document role checks delivered reality against this discipline's acceptance criteria when each agent spec ships. The intent surface's audit takes a shipped intent and nothing else and refuses a record in disciplines/ by name. No audit run can judge a discipline's criteria, so the check itd-5 depends on cannot be issued by the surface as written.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 459.
Frontmatter
| id | iss-2610262033586792 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033586792-itd-5-relies-on-intent-auditor-s.md
open on GitHub ↗ · commit history ↗
References1
- itd-5Every Agent Prompt Carries Its Version, Earns Its Lock, And Survives Injectionrelated