abcd resolves every layered setting through the shared

Press Release

abcd resolves every layered setting through the shared resolver by the one order adr-2611011332427073 sets: bundled default, the person's home file, the repository's file, the person's gitignored per-repository file, then the invocation; each restriction, capability and personal key declares its class on the key, the rules loader, guard.json, outbound.forge, the status line and the environment variables read outside the resolver move onto it, and the configuration chapter states the rule once with each key's class. A personal spending cap, read as a restriction from any layer, bounds what a repository's model tiers can cost the person. The per-repository layer is read as the person's only while git tracks nothing at its path, no part of its path is a symlink, and the file passes the home file's guarded read, and abcd says so when a pull starts tracking a file at that path.

Why This Matters

Why this matters to the user — replace before planning.

Mechanism

Prompted (the claim-recording gradient): why the authors expect this to work, as a falsifiable "we expect X because Y" — not the outcome restated. Replace this line with the claim, or with the exact token None stated. alone on its line to record the claim as considered and declined.

Scope Conditions

Required (the claim-recording gradient): the population, platform, scale, or assumptions this claim holds under, one per top-level bullet — abcd intent plan stamps each with a persistent identity. Replace this line with those bullets, or with the exact token None stated. alone on its line.

Acceptance Criteria

Required (the itd-1 discipline): add at least one Given-When-Then bullet describing the verifiable bar for "shipped" before this draft can be planned.

Open Questions

None recorded yet.

Audit Notes

Empty. Populated by intent-auditor when intent moves to shipped/.