Two ADR files claiming one id are read first-wins: recordid's resolver kept the first path in name order for an id two files claim, and record-lint had unique-id rules for intents, issues and specs only, so an accepted 0037-a.md beside a proposed 0037-x.md settled every reader of adr-37 (abcd adr-37 rendered the twin; a start-blocker check reading the status would settle on it).

Two ADR files claiming one id are read first-wins: recordid's resolver kept the first path in name order for an id two files claim, and record-lint had unique-id rules for intents, issues and specs only, so an accepted 0037-a.md beside a proposed 0037-x.md settled every reader of adr-37 (abcd adr-37 rendered the twin; a start-blocker check reading the status would settle on it).

Grounds

• pursued: two files answering to one ADR id fail record-lint and make abcd adr-N refuse naming both; a duplicate that passes record-lint, or a lookup that returns one of two claimants, would show it wrong