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

Adopt reviewed InterfaceCanon projection terminology

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a087d8-d22d-7d11-8169-bf22a729dff1
This commit is contained in:
tegwick 2026-09-09 22:42:31 +02:00
parent 3db3e7e297
commit 84df076e95
4 changed files with 123 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

13
intakes/intakes.md
View file

@ -37,8 +37,19 @@ description: Before any new workplan is allocated under WHYNOT-WP, OPS-WP, or RE
finished/archived files remain frozen. Re-run rmgr prefix-uniqueness and identifier
preflight after assignment.
created: '2026-08-21T20:34:42.177493+00:00'
updated: '2026-08-21T20:34:42.177493+00:00'
updated: '2026-09-09T20:42:09.617881Z'
state_hub_intake_id: "01a02611-a663-7712-bd4b-e39c13e7bf20"
notes:
- content: >-
2026-09-09 review: the registry already assigns WHYNOT-WP to whynot-design,
WNCTL-WP to whynot-control, OPS-WP to ops-hub, and BRIDGE-WP to ops-bridge.
Fleet prefix scan reports no sharing or reused identifiers for these
prefixes. However whynot-control/AGENTS.md still advertises WHYNOT-WP,
despite its WNCTL-WP workplan files. Align that repository's instructions
before its next allocation. REPO-WP remains unassigned in the registry. Current instructions advertise
CORE-WP for core-hub, DISCTL-WP for disaster-control, and REPO-WP for
repo-seed; finalize these registry assignments before reuse.
author: codex
```
## RMGR-IN-0003 — Scope normal sync identity validation to actionable records