docs(workplans): extend RMGR-WP-0004-T08 to canon artifact identifiers

ADR-007 decision 1 governs PREFIX-WP-NNNN only. The 2026-08-17 ADR-008
collision showed ADR numbers, versioned standards, and other repo-local
running numbers have identical exposure and no rule. Same check shape: one
allocator per namespace, forward-only, no reuse; two files claiming one id
is a contradictory finding.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-18 18:24:06 +02:00
parent 2e5fe07775
commit 0dde030ae3
2 changed files with 23 additions and 2 deletions

View file

@ -34,7 +34,7 @@
| task | RMGR-WP-0004-T02 | todo | — | workplans/RMGR-WP-0004-repository-standards-conformance.md |
| task | RMGR-WP-0004-T03 | done | — | workplans/RMGR-WP-0004-repository-standards-conformance.md |
| task | RMGR-WP-0004-T04 | wait | — | workplans/RMGR-WP-0004-repository-standards-conformance.md |
| task | RMGR-WP-0004-T05 | wait | — | workplans/RMGR-WP-0004-repository-standards-conformance.md |
| task | RMGR-WP-0004-T05 | todo | — | workplans/RMGR-WP-0004-repository-standards-conformance.md |
| task | RMGR-WP-0004-T06 | wait | — | workplans/RMGR-WP-0004-repository-standards-conformance.md |
| task | RMGR-WP-0004-T07 | wait | — | workplans/RMGR-WP-0004-repository-standards-conformance.md |
| task | RMGR-WP-0004-T08 | done | — | workplans/RMGR-WP-0004-repository-standards-conformance.md |

View file

@ -170,7 +170,7 @@ flavor-blind template silently re-breaks conformant repos.
```task
id: RMGR-WP-0004-T05
status: wait
status: todo
priority: medium
state_hub_task_id: "8402b8b6-2a1e-4236-b27d-d50b6161a176"
```
@ -188,6 +188,10 @@ guard plus handoff rather than a parallel implementation:
Follow the dual-run strangler pattern already proven in `RMGR-WP-0002` and
`RMGR-WP-0003` rather than a flag-day switch.
**Opened (2026-08-18):** `STATE-WP-0080-T01` now refuses `prj-` scaffolding and
points at `rmgr scaffold`. T03 is done. Cutover / inventory move can start
alongside `STATE-WP-0080-T02`.
## Add compatibility and regression tests
```task
@ -246,6 +250,23 @@ identifiers reused:
Detection only. Remediating the existing collisions is an open ruling in
`ADR-007` § Migration and is not authorized by this task.
Scope is not limited to workplans. `ADR-007` decision 1 is written for
`PREFIX-WP-NNNN`, but **canon artifacts have identical exposure and no rule at
all**. Demonstrated 2026-08-17: `ADR-008` was allocated concurrently by two
authors — `adr-008-multi-tenancy-model.md` and `adr-008-hub-authority-and-local-cache-model.md`,
both `id: ADR-008`, committed the same day. Resolved by renumbering the latter to
`ADR-010`, but only after the collision existed in the repository.
Cover every sequentially allocated identifier in a repository:
- `ADR-NNN` in `canon/architecture/`;
- versioned standards and canon documents (`*_vN.N.md`);
- any other repo-local running number the standard introduces.
The check is the same shape as for workplans — one allocator per namespace,
forward-only, no reuse — and the same detection applies: two files claiming one
`id:` is a `contradictory` finding, not a `missing` one.
**This task gates `RMGR-WP-0005`.** Deterministic identifier derivation from a
non-unique identifier would manufacture UUID collisions rather than remove them.