Development record
The rules-loader intent rejects a user-level rules.json and keeps rules per repository; the guard chapter counts a rules.json in abcd's home folder as part of the user layer.
The rules-loader intent rejects a user-level rules.json and keeps rules per repository; the guard chapter counts a rules.json in abcd's home folder as part of the user layer.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/shipped/itd-3-modular-rules-loader.md:41— "explicitly rejected. Keeping a personal cross-repo rules file recreates exactly the" - End B:
.abcd/development/brief/04-surfaces/17-guard.md:452— "its trusted-roots, rules.json, config.json and the rest of the user layer"
itd-3 marks a global rules.json in abcd's home as explicitly rejected and keeps rules per repository only, because a cross-repository rules file recreates the failure the loader exists to fix. The guard chapter names rules.json, beside trusted-roots and config.json, among the files of abcd's own folder in the home directory, part of the user layer. One document says the file must not exist and the other treats it as part of abcd's home.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 669.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262045266820. Same A statement and same root cause: itd-3 rejects a user-level rules file that itd-117 later introduced and the loader reads (internal/core/rules/layerfile.go).
Frontmatter
| id | iss-2610262036437864 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262036437864-the-rules-loader-intent-rejects-a.md
open on GitHub ↗ · commit history ↗
References1
- itd-3abcd Loads Its Own Rules On Demandrelated
mentions3
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- iss-2610262045266820itd-3 rejects a user-level rules.json outright; itd-2610030720038073 records that every managed project's block names the home's top-level rules.json
- itd-117A Machine's Shared Conventions Are Declared Once In The User Scope — And Every Managed Repo Inherits Them