This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-117 puts the user-scope rules layer at ~/.abcd/rules.json; 30-inbox says the rules loader reads ~/.abcd.noindex/rules.json

issuewontfixminoriss-2610262037458871

itd-117 puts the user-scope rules layer at ~/.abcd/rules.json; 30-inbox says the rules loader reads ~/.abcd.noindex/rules.json

A naming conflict (severity minor) found by the cross-document consistency pass.

  • End A: .abcd/development/intents/shipped/itd-117-development-instructions-live-in-the.md:19 — "now live once in ~/.abcd/rules.json and inject into every"
  • End B: .abcd/development/brief/04-surfaces/30-inbox.md:143 — "the stance the rules loader takes on ~/.abcd.noindex/rules.json behind a symlinked"

Shipped itd-117 says the machine's shared conventions live in ~/.abcd/rules.json and inject into every managed repository. 30-inbox describes the rules loader's stance on ~/.abcd.noindex/rules.json behind a symlinked ~/.abcd.noindex. These are two names for the one user-scope home and its rules file. A builder or user following itd-117 would write a file that the loader, as the brief describes it, never reads.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. internal/core/rules uses abcdhome.Rel for the user layer, so the loader reads the renamed path.

Frontmatter

idiss-2610262037458871
typeissue
lifecyclewontfix
severityminor

References1

mentions1