Development record
itd-44 writes the diverted ADR as `adr-<next-free>-<slug>.md`; the intent chapter names the same ADR-store file `NNNN-<slug>.md`, zero-padded.
itd-44 writes the diverted ADR as adr-<next-free>-<slug>.md; the intent chapter names the same ADR-store file NNNN-<slug>.md, zero-padded.
A naming conflict (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-44-fourth-intent-kind-decision.md:122— "adr-<next-free>-<slug>.mdinto.abcd/development/decisions/adrs/" - End B:
.abcd/development/brief/04-surfaces/05-intent.md:93— "(.abcd/development/decisions/adrs/,NNNN-<slug>.md, zero-padded)"
Both documents describe the same diversion: a confirmed decision verdict is written into .abcd/development/decisions/adrs/ instead of an intent draft. They give that file different shapes. itd-44 uses an adr- prefix and the next free number, while 05-intent.md uses a bare zero-padded NNNN- number. A builder cannot write both.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 487.
Frontmatter
| id | iss-2610262034191519 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262034191519-itd-44-writes-the-diverted-adr-as-adr.md
open on GitHub ↗ · commit history ↗
References1
- itd-44A Capture-Time `decision` Verdict That Routes Infrastructure Choices Into The Existing ADR Storerelated
mentions3
- iss-2610262037334466itd-44 files ADRs as adr-< next-free>-< slug>.md; the drain brief cites the store's ADRs as < timestamp id>-< slug>.md
- iss-2610262044038958itd-44 writes ADRs under a next-free ordinal; itd-114 makes every minted id collision-proof across branches
- iss-2610262044191365Two routes mint an ADR: the draft's capture writes adr-< next-free>, and the shipped decide verb mints ADRs with --adr