the-custodian/workplans/CUST-WP-0066-repository-qualified-ad-hoc-identifiers.md
repo-manager 1f56ce55fe
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
chore(registrar): assign State Hub identifiers
2026-08-23 14:54:34 +02:00

79 lines
2.7 KiB
Markdown

---
id: CUST-WP-0066
type: workplan
title: "Repository-qualified ad-hoc work-record identifiers"
domain: infotech
repo: the-custodian
status: finished
owner: codex
topic_slug: custodian
created: "2026-08-23"
updated: "2026-08-23"
related:
- CUST-ADR-007
- CUST-ADR-011
- RMGR-WP-0005
state_hub_workstream_id: "58080276-8e38-57fa-963b-42819ce66c34"
---
# Repository-qualified ad-hoc work-record identifiers
Two repositories created the canon-prescribed `ADHOC-2026-08-23` workplan and
task identifiers on the same day. Deterministic UUID derivation correctly
refused the second registration because ADR-007 requires identifiers to be
unique within the fleet namespace. Repair the naming convention rather than
weakening collision protection or treating repositories as namespaces.
## Correct the canonical identifier scheme
```task
id: CUST-WP-0066-T01
status: done
priority: high
state_hub_task_id: "2710fb1c-2f11-54ce-aea9-5e90f5c46a05"
```
Make `{PREFIX}-WP-ADHOC-YYYY-MM-DD` and its task suffixes canonical. Retain the
unqualified historic form as grandfathered compatibility only.
Completed in the machine-readable registry, prose standard, project-repository
standard, repository instructions, and regression tests. This preserves
ADR-007/ADR-011 namespace semantics and does not reinterpret repositories as
namespaces.
## Synchronize enforcement and authoring guidance
```task
id: CUST-WP-0066-T02
status: done
priority: high
state_hub_task_id: "63bbc176-f8e5-53fb-9d77-2df6e2861309"
```
Update Repo Manager's canon copy and State Hub's repository instruction
templates and validators so newly authored records use the collision-free form.
Repo Manager now classifies qualified daily ids as canonical and unqualified
ones as grandfathered. State Hub's two instruction templates and legacy ADR
validator use the same scheme; the validator explicitly permits the unchanged
`ADHOC-YYYY-MM-DD.md` filename.
## Repair and register the colliding Activity Core record
```task
id: CUST-WP-0066-T03
status: done
priority: high
state_hub_task_id: "119ae481-ccd5-56b3-b839-75db8abe996a"
```
Rename the not-yet-registered Activity Core record, reconcile it through the
governed registrar, and preserve the successful ACTIVITY-WP-0035 and
ACTIVITY-WP-0036 identifier writebacks from the partial attempt.
The partial writeback was verified against the central projection and pushed as
Activity Core revision `4d7623a`. The renamed daily record then registered as
workplan `32d157b1-94b2-5d29-9b41-d3d9130cbb32` and task
`330907a0-2899-5cbf-a056-4835c2f6faf8`; the registrar returned `applied` with
correlation `f272ab73-35fb-44e7-aabd-23b124e3c135` and pushed revision
`13aea81`. No actionable residual remains.