Development record
itd-50 calls the per-criterion auditor intent-fidelity-reviewer; the brief names the same role intent-auditor (Role 1).
issueopenminoriss-2610262031563379
itd-50 calls the per-criterion auditor intent-fidelity-reviewer; the brief names the same role intent-auditor (Role 1).
A naming conflict (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-50-loop-toward-acceptance.md:25— "theintent-fidelity-reviewerrecords aNOT_METverdict" - End B:
.abcd/development/brief/01-product/01-press-release.md:26— "/abcd:intent audit(Role 1 ofintent-auditor)"
itd-50's press release says 'the intent-fidelity-reviewer records a NOT_MET verdict'. The brief's press release names the same role as '/abcd:intent audit (Role 1 of intent-auditor)'. That is two names for one agent role, and work built from the planned intent would look for an agent the brief does not name.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 199.
Frontmatter
| id | iss-2610262031563379 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262031563379-itd-50-calls-the-per-criterion-auditor.md
open on GitHub ↗ · commit history ↗
References1
- itd-50The Audit Loop Drives An Intent To Acceptance — Or Calls For A Replanrelated
mentions4
- iss-2610262037438474itd-50 calls the fidelity verdict's agent intent-fidelity-reviewer; 34-build names the same validator intent-auditor
- iss-2610262039302287itd-50 names the fidelity auditor `intent-fidelity-reviewer`; the agent catalog names the same agent `intent-auditor`
- iss-2610262041338234itd-50 says the `intent-fidelity-reviewer` records today's NOT_MET verdicts; the verification matrix names that role `intent-auditor`
- iss-2610262045054264The agent that writes per-criterion audit verdicts is the intent-fidelity-reviewer in itd-50 and the intent auditor in itd-24