feat(identifiers): prepare verified cutover batches
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
parent
bdf3af19e2
commit
5e14d09bdf
10 changed files with 3097 additions and 0 deletions
47
decisions/RMGR-DEC-2026-001-whynot-identifier-batch.md
Normal file
47
decisions/RMGR-DEC-2026-001-whynot-identifier-batch.md
Normal file
|
|
@ -0,0 +1,47 @@
|
|||
# RMGR-DEC-2026-001 — Whynot Design identifier cutover batch
|
||||
|
||||
```yaml
|
||||
id: RMGR-DEC-2026-001
|
||||
kind: decision
|
||||
title: Approve deterministic identifier batch 0002 for whynot-design
|
||||
status: open
|
||||
decision_type: pending
|
||||
owner: Bernd Worsch
|
||||
repo: repo-manager
|
||||
workplan: RMGR-WP-0005
|
||||
workplan_task: RMGR-WP-0005-T04
|
||||
requested_dispositions:
|
||||
- approved
|
||||
- revised
|
||||
- rejected
|
||||
source_plan: docs/evidence/RMGR-WP-0005-helixforge-uuid-migration-plan-2026-08-22-v2.json
|
||||
source_plan_sha256: ac97f6e4f0b35db63a0dc1b4a439f0a39738d13c1407f18419f706d780d4eea0
|
||||
batch_manifest: docs/evidence/RMGR-WP-0005-batch-0002-whynot-design.json
|
||||
batch_sha256: 4039224352c6590fdc6b41e739539f1f9c92d098b43ed6e30b3cd9a87b53da65
|
||||
scope:
|
||||
repositories: [whynot-design]
|
||||
replacements: 1
|
||||
assignments: 0
|
||||
apply_authorized: false
|
||||
approval_effect: >-
|
||||
Approved authorizes one repository-atomic forward cutover of exactly the
|
||||
pinned batch in both current projections and the authoritative repository
|
||||
file, subject to repeated no-drift and restore-point checks. Revised or
|
||||
rejected authorizes no mutation.
|
||||
rollback: >-
|
||||
Reverse the file transaction if written, then reverse workstation and
|
||||
production projection transactions using their durable aliases.
|
||||
evidence: docs/evidence/RMGR-WP-0005-batch-0002-readiness-2026-08-22.md
|
||||
created: "2026-08-22"
|
||||
updated: "2026-08-22"
|
||||
```
|
||||
|
||||
## Decision requested
|
||||
|
||||
Approve, revise, or reject the exact batch manifest named above. Approval is
|
||||
limited to `whynot-design` and the single `WHYNOT-WP-0003` UUID replacement; it
|
||||
does not authorize any later fleet batch.
|
||||
|
||||
The manifest remains fail-closed: any Git, source-fingerprint, projection, or
|
||||
plan-seal drift before execution voids the approval and requires a new batch
|
||||
hash.
|
||||
Loading…
Add table
Add a link
Reference in a new issue