coulomb/repo-manager
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(workplans): record RAIL-BS- retirement and numbering rule in T09

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-17 10:41:04 +02:00
parent 52cd6d7a1b
commit 390b6256d7
1 changed files with 37 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

42
workplans/RMGR-WP-0004-repository-standards-conformance.md
View file

@ -254,17 +254,49 @@ so historical files keep their identifiers and are not renamed.
| `RAIL-BS-WP-` | railiance-cluster (6), railiance-bootstrap (2) | **growing** — `RAIL-BS-WP-0014` ready |
| `RAILIANCE-WP-` | railiance-platform (12), apps (2), forge (1), telemetry (1) | **growing** — forge `0002` ready, telemetry `0001` proposed |
Recommended assignments, to be confirmed with each owning repo:
Assignments:
- `CUST-WP-` → `the-custodian`. `state-hub`'s canonical prefix is already
`STATE-WP` (`C-26` says so today); its four legacy files stay as history.
- `RAIL-BS-WP-` → needs a call. The name reads as *railiance-bootstrap*, but
`railiance-cluster` holds more plans and is the active user. Whichever repo
does not keep it takes a new prefix from its own identity.
- `RAIL-BS-WP-` → **retired; neither repo keeps it** (decided 2026-08-17).
`railiance-cluster` adopts **`RCLUSTER-WP-`**, `railiance-bootstrap` adopts
**`RBS-WP-`**.
- `RAILIANCE-WP-` → recommend **none of them keep it**. `RAILIANCE` names a
family, not a repository, so it fails decision 1's requirement that prefixes
derive from project or repository identity — the same defect as `PRJ-WP-`.
Give each of the four repos a prefix from its own name.
Give each of the four repos a prefix from its own name. Assignment still to be
confirmed, following the `RAIL-BS-` pattern.
### RAIL-BS- retirement detail
`railiance-cluster` switches **active and future** plans to `RCLUSTER-WP-`;
`railiance-bootstrap` takes `RBS-WP-` for future plans. Finished and archived
files keep `RAIL-BS-WP-` as historical record, per the option 2 ruling.
Migrating plans keep their running numbers — prefix changes, number does not:
```text
railiance-cluster RAIL-BS-WP-0007 (backlog) -> RCLUSTER-WP-0007
RAIL-BS-WP-0014 (ready) -> RCLUSTER-WP-0014
next allocation = RCLUSTER-WP-0015
finished 0010-0013 stay as RAIL-BS-WP-
railiance-bootstrap no live plans to migrate (0008, 0009 both finished)
next allocation = RBS-WP-0010
```
Preserving numbers keeps traceability and cannot violate forward-only
allocation, since neither new prefix has prior history.
`railiance-bootstrap` starts at **0010**, above its historical maximum of 9,
rather than at 0001. This keeps `RBS-WP-0001`–`0009` free in case its two
finished plans are ever adopted into the new prefix; starting at 0001 would make
that adoption collide later.
Execution belongs to workers in `railiance-cluster` and `railiance-bootstrap`
per `ADR-007` decision 4 — this task records the assignment and the numbering
rule, and does not perform the rename. Each repo also needs the hub records and
any inbound references updated with the file rename.
Per `ADR-007` decision 4, the rename of a repository's own convention is
executed by a worker in that repository. This task assigns and records