# RMGR-DEC-2026-002 — Markitect identifier cutover batch

```yaml
id: RMGR-DEC-2026-002
kind: decision
title: Approve deterministic identifier batch 0003 for markitect-main
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-helixforge-uuid-migration-plan-2026-08-22-v2.json
source_plan_sha256: ac97f6e4f0b35db63a0dc1b4a439f0a39738d13c1407f18419f706d780d4eea0
batch_manifest: docs/evidence/RMGR-WP-0005-batch-0003-markitect-main.json
batch_sha256: 494db8e101aeae7f8488082565dec3b4dd5c9c6ccb5f8812aaf233f813768f67
scope:
  repositories:
  - markitect-main
  replacements: 2
  assignments: 0
apply_authorized: true
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 production and workstation
  projection transactions using their durable aliases.
evidence: docs/evidence/RMGR-WP-0005-batch-0003-markitect-readiness-2026-08-22.md
created: '2026-08-22'
updated: '2026-08-22T14:27:29.112964Z'
state_hub_decision_id: 370d370c-4f7c-4314-b7d3-74c5bc78bc7e
approved_batch_sha256: 494db8e101aeae7f8488082565dec3b4dd5c9c6ccb5f8812aaf233f813768f67
approval_source: operator chat approval on 2026-08-22
rationale: Bernd Worsch approved exactly batch SHA-256 494db8e101aeae7f8488082565dec3b4dd5c9c6ccb5f8812aaf233f813768f67
  for the markitect-main-only cutover. No later or broader batch is authorized.
decided_by: Bernd Worsch
decided_at: '2026-08-22T14:27:29.112964Z'
```

## Decision requested

Approve, revise, or reject the exact batch manifest named above. Approval is
limited to `markitect-main`, `MARKITECT-WP-0002`, and
`MARKITECT-WP-0002-T01`; it does not authorize any later or broader 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.