repo-manager/config/workplan-prefix-registry.yaml
tegwick 906cc2d7a9 fix(registrar): OPS-WP belongs to ops-hub, not retirement
I retired OPS-WP on the reasoning that it names an ops family rather than a
repository, without checking whether a repo owns it. ops-hub does: all 14 of
its workplans use it. The anomaly is the reverse of what I wrote - the 16
OPS-WP ids in ops-bridge are the strays, against its 73 BRIDGE-WP ids.

Recorded as debt rather than fixed here: re-keying those 16 to BRIDGE-WP is a
separate migration with its own hub retirements, and today's pass is scoped to
ad-hoc identifiers.

WHYNOT-WP stays with whynot-design (26 ids vs whynot-control's 6), ruled by
Bernd. whynot-control's 6 are the same class of stray.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 00:58:57 +02:00

73 lines
2.2 KiB
YAML

# RMGR-WP-0004-T08 / ADR-007 decision 1
# One prefix, one repository. Prefixes derive from repo or project identity,
# never from a flavor marker or family name. Detection only — historical
# collisions stay until ADR-007 § Migration is ruled.
standard: workplan-prefix-ownership
version: "0.1"
canon:
- the-custodian/canon/architecture/adr-007-workplan-identity-and-repo-worker-topology.md
- the-custodian/canon/standards/project-repository-flavor_v0.1.md
retired:
- prefix: NET-WP
reason: second prefix in net-kingdom; NK-WP is the repository's form (229 ids vs 49)
successors: [NK-WP]
- prefix: PRJ-WP
reason: flavor marker; never a valid prefix
- prefix: RAIL-BS-WP
reason: shared family name, not a repository
successors: [RCLUSTER-WP, RBS-WP]
- prefix: RAILIANCE-WP
reason: family name, not a repository
successors: [RPF-WP, RAPPS-WP, RFORGE-WP, RTELE-WP]
owners:
RMGR-WP: repo-manager
CUST-WP: the-custodian
STATE-WP: state-hub
CFED-WP: prj-canon-federation
SHR-WP: prj-state-hub-retirement
RCLUSTER-WP: railiance-cluster
RBS-WP: railiance-bootstrap
RPF-WP: railiance-platform
RAPPS-WP: railiance-apps
RFORGE-WP: railiance-forge
RTELE-WP: railiance-telemetry
RMASTER-WP: railiance-master
RAIL-K8S-WP: rail-kubernetes
RAPP-OPENBAO-WP: rapp-openbao
RAPP-USER-ENGINE-WP: rapp-user-engine
RAPP-TENANT-ENGINE-WP: rapp-tenant-engine
RAPP-POLICY-NEXUS-WP: rapp-policy-nexus
USER-WP: user-engine
TEN-WP: tenant-engine
ACTIVITY-WP: activity-core
ADAPTIVE-WP: adaptive-pricing
AGENTIC-WP: agentic-resources
GROUND-WP: ground-game
ITC-WP: info-tech-canon
KAIZEN-WP: kaizen-agentic
LLM-WP: llm-connect
NK-WP: net-kingdom
BRIDGE-WP: ops-bridge
WARDEN-WP: ops-warden
QONTO-WP: qonto-assistant
RAIL-HO-WP: railiance-infra
SECRETS-WP: secrets-engine
TAMQ-WP: tmux-amq
RAIL-FAB-WP: railiance-fabric
WHYNOT-WP: whynot-design
OPS-WP: ops-hub
historical_collisions:
- id: RAILIANCE-WP-0015
repos: [railiance-platform, railiance-apps]
- id: RAILIANCE-WP-0016
repos: [railiance-platform, railiance-apps]
- id: CUST-WP-0000
repos: [the-custodian]
- id: CUST-WP-0010
repos: [the-custodian]
- id: CUST-WP-0045
repos: [the-custodian]