From 1aed222ae2804e7ec25e1239f899497c7f6e76c7 Mon Sep 17 00:00:00 2001 From: sami Date: Thu, 10 Sep 2026 15:31:01 +0400 Subject: [PATCH] =?UTF-8?q?docs:=20ADR-number=20convention=20in=20CLAUDE.m?= =?UTF-8?q?d=20=C2=A77=20=E2=80=94=20second=20merger=20renumbers?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Six lanes pick ADR numbers with no allocator. This lane dodged one collision by taking 0012 while DAEMON drafted 0011, and just hit a real one — two 0014s in the same integration round. Codify what already happened in practice: take the next free number in main's docs/adr/, and on collision whoever merges second renumbers and fixes cross-refs rather than round-tripping. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_012fgjnqFCS5h5L7gZTZo3rV --- CLAUDE.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index d6ce8df..b9364af 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -68,3 +68,8 @@ you change observable behaviour, update the doc in `docs/` that describes it in Ask in the PR rather than guessing at the interface. A day of clarification is cheaper than an M2 integration rewrite. And record real decisions as an ADR in `docs/adr/` — the next agent to touch this will have none of your context. + +**ADR numbers:** there is no allocator. Take the next free number in `main`'s +`docs/adr/` (gaps from reserved-but-unwritten entries are fine to fill). Lanes draft in +parallel, so collisions happen: whoever merges **second** renumbers, updates any +cross-references, and keeps going — it is not worth a round trip.