This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-44 has capture write an ADR as adr-< next-free>-< slug>.md; the decide chapter mints ADR ids from a timestamp that reads no maximum, and names the file < stamp>-< slug>.md.

issueopenmajoriss-2610262036171679

itd-44 has capture write an ADR as adr-< next-free>-< slug>.md; the decide chapter mints ADR ids from a timestamp that reads no maximum, and names the file < stamp>-< slug>.md.

A premise contradiction (severity major) found by the cross-document consistency pass.

  • End A: .abcd/development/brief/04-surfaces/24-decide.md:127 — "The mint reads no maximum: not the store's, not the"
  • End B: .abcd/development/intents/drafts/itd-44-fourth-intent-kind-decision.md:122 — "adr-<next-free>-<slug>.md into .abcd/development/decisions/adrs/"

24-decide says an ADR id is adr-< yymmddHHMMSS>< rrrr> and the mint reads no maximum, neither the store's nor the citations'. It also says a hand-numbered ordinal allocated by reading the directory is exactly the collision the ruling closed. itd-44 allocates adr-< next-free> and writes adr-< next-free>-< slug>.md into the same store. That is allocation by reading the directory, and a filename shape the store does not use. Building itd-44 as written brings back the duplicate-number collision.

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

Deferral 2026-10-27

Deferred past v0.15.1: Deferred by the product thinker on 2026-10-27 (dcn-2610271112330536): the brief's single-home rewrite (dcn-2610271112339516, dcn-2610271112330235) rewrites or removes most of the passages this record quotes.

Frontmatter

idiss-2610262036171679
typeissue
lifecycleopen
severitymajor

References1

mentions3