codex 8253276bdd docs(canon): retire RAIL-BS-WP-; cluster takes RCLUSTER-WP-, bootstrap RBS-WP- ... Neither repo keeps the shared prefix. railiance-cluster switches active and future plans (0007 backlog, 0014 ready) to RCLUSTER-WP- preserving running numbers; railiance-bootstrap takes RBS-WP- starting at 0010, above its historical maximum, so its finished plans could be adopted later without collision. Finished files keep RAIL-BS-WP- per the option 2 ruling. RAILIANCE-WP- should be retired the same way rather than awarded to one repo; successor prefixes still outstanding. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-08-17 10:41:03 +02:00
..
adr-001-workplans-as-repo-artefacts.md	feat(terminology): prose sweep tool and custodian workplan cleanup (CUST-WP-0055 T04)	2026-07-08 16:35:37 +02:00
adr-002-custodian-agent-runtime-design.md	feat(CUST-WP-0001): implement Custodian Agent Runtime bootstrap	2026-03-12 22:36:24 +01:00
adr-003-materialized-derived-state.md	docs(adr): ADR-003 — Materialized Derived State with Fingerprint Invalidation	2026-03-20 01:54:21 +01:00
adr-004-connectivity-first-network-posture.md	ADR and Runbook artefacts	2026-03-27 00:16:09 +01:00
adr-005-cross-repo-workplans-project-repos.md	docs(canon): define prj- project repository flavor	2026-08-09 17:24:07 +02:00
adr-006-canon-federation-concept-ownership.md	docs(canon): ADR-006 accepted — R7 places evidence pair in dedicated itc-evid	2026-08-17 10:03:15 +02:00
adr-007-workplan-identity-and-repo-worker-topology.md	docs(canon): retire RAIL-BS-WP-; cluster takes RCLUSTER-WP-, bootstrap RBS-WP-	2026-08-17 10:41:03 +02:00