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

docs(workplans): record RAILIANCE- retirement and completed prefix migration

Browse source 
RPF/RAPPS/RFORGE/RTELE assigned; four live plans migrated keeping running
numbers; six repos' conventions repointed. Executed centrally as an
authorized exception to ADR-007 decision 4, with the reason recorded.

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

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

@ -261,11 +261,54 @@ Assignments:
- `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. Assignment still to be
confirmed, following the `RAIL-BS-` pattern.
- `RAILIANCE-WP-` → **retired; none of the four keep it** (decided 2026-08-17).
`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-`. Successors: `railiance-platform` → `RPF-WP-`,
`railiance-apps` → `RAPPS-WP-`, `railiance-forge` → `RFORGE-WP-`,
`railiance-telemetry` → `RTELE-WP-`.
### Execution (2026-08-17) — completed as an authorized exception
Executed centrally rather than by a worker in each repository, as an explicit
exception to `ADR-007` decision 4, authorized by Bernd. Recorded here because
decision 4 requires exceptions to carry a stated reason: six repositories needed
one coordinated change with a shared numbering rule, and sequencing six
independent workers would have risked partial adoption.
Live plans migrated (prefix changed, running number preserved):
```text
railiance-cluster RAIL-BS-WP-0007 (backlog) -> RCLUSTER-WP-0007
RAIL-BS-WP-0014 (ready) -> RCLUSTER-WP-0014
railiance-forge RAILIANCE-WP-0002 (ready) -> RFORGE-WP-0002
railiance-telemetry RAILIANCE-WP-0001 (proposed) -> RTELE-WP-0001
```
Next allocations, each above the repo's historical maximum:
`RCLUSTER-WP-0015` · `RBS-WP-0010` · `RPF-WP-0018` · `RAPPS-WP-0017` ·
`RFORGE-WP-0003` · `RTELE-WP-0002`.
Also updated: each repo's `.claude/rules/workplan-convention.md` (and `AGENTS.md`
where it declared the prefix), which governs what future agents allocate;
`railiance-bootstrap/docs/POINTER-RAIL-BS-WP-0007.md` renamed and rewritten;
`railiance-forge/.custodian-brief.md`.
Deliberately left unchanged: `state-hub/reports/recently-on-scope/**` are dated
point-in-time snapshots and must keep the identifiers current when they were
written. `railiance-master`'s `REEF-RAILIANCE-WP-0001` is a different prefix and
was a false positive in the reference sweep.
Hub UUIDs were preserved in every migrated file, so reconciliation matches on
`state_hub_workstream_id` (C-03/C-06 join on that field, not the filename) and
will update slugs in place rather than registering duplicates. **Not yet
reconciled** — the workstation is not the registrar under `ADR-007` decision 2.
Two collisions surfaced during execution and remain as historical record under
option 2: `railiance-cluster` carries its own copies of `RAIL-BS-WP-0008` and
`0009`, which also exist in `railiance-bootstrap`; and `railiance-forge` holds an
archived `RAILIANCE-WP-0001` that duplicated `railiance-telemetry`'s live one
until this migration separated them.
### RAIL-BS- retirement detail