coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs(canon): retire RAIL-BS-WP-; cluster takes RCLUSTER-WP-, bootstrap RBS-WP-
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
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>
This commit is contained in:
codex 2026-08-17 10:41:03 +02:00
parent e3699ebc89
commit 8253276bdd
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md
View file

@ -239,6 +239,28 @@ produces, and it will recur at the next concurrent allocation.
`CUST-` is dormant on the `state-hub` side — four legacy plans, one in
`backlog` — and needs no split, only a prefix-ownership assertion.
### Prefix assignments
`RAIL-BS-WP-` is **retired** (2026-08-17). Neither repository keeps it:
`railiance-cluster` adopts `RCLUSTER-WP-` for active and future plans;
`railiance-bootstrap` adopts `RBS-WP-` for future plans. Finished and archived
files keep `RAIL-BS-WP-` as historical record, consistent with option 2.
Migrating plans keep their running numbers — the prefix changes, the number does
not. This preserves traceability and cannot violate forward-only allocation,
because neither new prefix has prior history. `railiance-bootstrap` begins at
`RBS-WP-0010`, above its historical maximum, leaving the lower range free should
its finished plans ever be adopted into the new prefix.
`RAILIANCE-WP-` should follow the same pattern — retired rather than awarded to
one repository, since it names a family rather than a repository and so fails
decision 1 for the same reason `PRJ-WP-` does. Assignment of the four successor
prefixes is outstanding.
Execution of each rename belongs to a worker in the owning repository under
decision 4. `RMGR-WP-0004-T09` records assignments and the numbering rule; it
does not perform renames.
**Consequence.** Prefix ownership must be assigned for all three shared prefixes
before the next workplan is created in the affected repositories. This is
forward conformance under decision 1, not migration, and is tracked as