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
..
assistant-provenance.yaml	feat: advance repository records and provenance	2026-08-21 22:07:48 +02:00
dual-run.pilot.example.yaml	feat(RMGR-WP-0003): production pilot dual-run config, bulk, push	2026-08-11 02:32:14 +02:00
fleet-namespace.yaml	feat(identifier): declare helixforge fleet namespace	2026-08-21 23:57:03 +02:00
hub-record-authority.yaml	feat: finish register receiving and authority routing	2026-08-21 23:15:48 +02:00
work-record-types.yaml	fix(identity): enforce qualified ad-hoc identifiers	2026-08-23 14:45:26 +02:00
workplan-prefix-registry.yaml	chore(registrar): register 14 repository prefixes, retire NET-WP and OPS-WP	2026-08-28 00:28:47 +02:00