repo-manager/config/workplan-prefix-registry.yaml
tegwick 5acb21a0de chore(registrar): register 14 repository prefixes, retire NET-WP and OPS-WP
Qualifying ad-hoc identifiers requires every repo to own a registered prefix,
and 13 of the 17 affected repos were absent from the registry despite using a
prefix consistently across dozens of files. None collided with an existing
owner or a retired prefix.

net-kingdom and ops-bridge each used two forms. NK-WP (229 ids vs NET-WP's 49)
and BRIDGE-WP (73 vs OPS-WP's 16) are the owners, ruled by Bernd. OPS-WP is
additionally retired for naming an ops family rather than a repository - the
same defect ADR-007 retired RAILIANCE-WP and PRJ-WP for. Existing NET-WP and
OPS-WP ids stay as they are; only their prefixes are closed to new work.

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:28:47 +02:00

73 lines
2.3 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: OPS-WP
reason: names an ops family, not a repository; collides in spirit with ops-warden and ops-mason
successors: [BRIDGE-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
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]