From 127c8655a6d7a237fd0d4279f5405eac237a8e17 Mon Sep 17 00:00:00 2001 From: Kris McGinnes Date: Tue, 16 Jun 2026 15:51:19 -0500 Subject: [PATCH] Adopt date-prefixed ADR filenames Name ADRs YYYYMMDD-kebab-title.md instead of a sequential 0001-style number. The date prefix stays sortable while avoiding the renumbering churn two branches hit when each adds an ADR from its own branch point. Refer to ADRs by their slug. --- docs/agents/domain.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/agents/domain.md b/docs/agents/domain.md index 16af79946..2e3ed2001 100644 --- a/docs/agents/domain.md +++ b/docs/agents/domain.md @@ -18,11 +18,16 @@ Single-context repo (most repos): / ├── CONTEXT.md ├── docs/adr/ -│ ├── 0001-event-sourced-orders.md -│ └── 0002-postgres-for-write-model.md +│ ├── 20260612-event-sourced-orders.md +│ └── 20260704-postgres-for-write-model.md └── src/ ``` +ADR files are named `YYYYMMDD-kebab-title.md`, where the date is when the +decision was accepted. The date prefix keeps them sortable chronologically and +avoids the renumbering churn that sequential IDs cause when two branches add an +ADR at once. Refer to an ADR by its slug, e.g. ADR `event-sourced-orders`. + ## Use the glossary's vocabulary When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids. @@ -33,4 +38,4 @@ If the concept you need isn't in the glossary yet, that's a signal — either yo If your output contradicts an existing ADR, surface it explicitly rather than silently overriding: -> _Contradicts ADR-0007 (event-sourced orders) — but worth reopening because…_ +> _Contradicts ADR `event-sourced-orders` — but worth reopening because…_