# RMGR-DEC-2026-005 — Reef Railiance identifier cutover batch ```yaml id: RMGR-DEC-2026-005 kind: decision title: Approve deterministic identifier batch 0006 for reef-railiance status: resolved decision_type: approved 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-fleet-plan-2026-08-31.json source_plan_sha256: af3c8e3fe6f423845a97258a10322eeded4b7814d13bf9541b5d550c285cc0b9 batch_manifest: docs/evidence/RMGR-WP-0005-batch-0006-reef-railiance-preflight-2026-08-31.json batch_sha256: 102061f3ed93eac091e9ceb05d9d3130241a23134b9f7d5a624d91c4ef824759 scope: repositories: [reef-railiance] replacements: 2 assignments: 0 apply_authorized: true approval_effect: >- Approved authorizes one repository-atomic forward cutover of exactly the pinned batch in the railiance01 primary projection and authoritative repository file, subject to repeated no-drift checks. Revised or rejected authorizes no mutation. rollback: >- Reverse the file transaction if written, then reverse the primary projection transaction using its durable aliases. evidence: docs/evidence/RMGR-WP-0005-batch-0006-reef-railiance-preflight-2026-08-31.json created: "2026-08-31" updated: "2026-08-31T11:23:46.601904Z" state_hub_decision_id: "a0616e13-cd0c-441a-8339-f0e502bb2bbf" approved_batch_sha256: 102061f3ed93eac091e9ceb05d9d3130241a23134b9f7d5a624d91c4ef824759 approval_source: operator chat approval on 2026-08-31 rationale: >- Bernd Worsch approved exactly batch SHA-256 102061f3ed93eac091e9ceb05d9d3130241a23134b9f7d5a624d91c4ef824759 for the reef-railiance-only cutover. No assignments, later fleet plan, or broader repository scope is authorized. decided_by: Bernd Worsch decided_at: "2026-08-31T11:23:46.601904Z" ``` ## Decision requested Approve, revise, or reject the exact batch manifest named above. Approval is limited to `reef-railiance`, `REEF-RAILIANCE-WP-0003`, and `REEF-RAILIANCE-WP-0003-T04`; it does not authorize assignments, another repository, or any later fleet plan. 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.