itd-2609292109214516 puts its setting in the rules configuration's layered files; itd-3 rejects any personal cross-repo rules file

itd-2609292109214516 puts its setting in the rules configuration's layered files; itd-3 rejects any personal cross-repo rules file

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/drafts/itd-2609292109214516-a-person-who-already-runs-carl-can-route.md:40 — "in the rules configuration the layered files already carry"
• End B: .abcd/development/intents/shipped/itd-3-modular-rules-loader.md:41 — "Keeping a personal cross-repo rules file recreates exactly the"

The CARL draft adds rules.backend to the rules configuration the layered files already carry, presupposing more than one rules file. itd-3 explicitly rejects a global rules.json, because keeping a personal cross-repo rules file recreates the failure it exists to fix, and says per-repo only. Either a user-level rules layer exists or it was rejected; the two records cannot both describe the loader.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1146.

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. The loader ships three layers (bundled, user, repo) and the repository's own instructions document the user file; itd-3 was true when written and is history.