prepare fleet identifier completion batch
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
This commit is contained in:
parent
c52d222cc6
commit
8f3b8ac2f6
8 changed files with 4691 additions and 8 deletions
|
|
@ -0,0 +1,63 @@
|
|||
# RMGR-DEC-2026-006 — Fleet-completion identifier cutover batch
|
||||
|
||||
```yaml
|
||||
id: RMGR-DEC-2026-006
|
||||
kind: decision
|
||||
title: Approve deterministic identifier batch 0007 for fleet completion
|
||||
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-fleet-plan-2026-08-31-v2.json
|
||||
source_plan_sha256: ab8ae2e55470553f105c6209d6aa4c7b828085bd6c71cec7b16173b8a19bef7b
|
||||
batch_manifest: docs/evidence/RMGR-WP-0005-batch-0007-fleet-completion-preflight-2026-08-31.json
|
||||
batch_sha256: c0cc496a06d9535a40840a0c7488cf365d8e47c5c58cc29aca72fb6d98273700
|
||||
scope:
|
||||
repositories:
|
||||
- fin-hub
|
||||
- net-kingdom
|
||||
- prj-canon-federation
|
||||
- prj-forgejo-org-refactor
|
||||
- prj-state-hub-retirement
|
||||
- prj-unattended-progress-company
|
||||
- railiance-master
|
||||
- railiance-telemetry
|
||||
- rapp-qonto
|
||||
- soul-frame
|
||||
replacements: 85
|
||||
assignments: 0
|
||||
apply_authorized: false
|
||||
approval_effect: >-
|
||||
Approved authorizes repository-atomic, sequential forward cutover of exactly
|
||||
the pinned batch in the railiance01 primary projection and each authoritative
|
||||
repository file, subject to repeated no-drift checks and stopping at the
|
||||
first failure. Revised or rejected authorizes no mutation.
|
||||
rollback: >-
|
||||
For a failing repository, reverse its file transaction if written, then
|
||||
reverse its primary projection transaction using durable aliases. Repositories
|
||||
already completed in the sequence remain completed unless a separate rollback
|
||||
decision authorizes reversing them.
|
||||
evidence: docs/evidence/RMGR-WP-0005-batch-0007-fleet-completion-readiness-2026-08-31.md
|
||||
created: "2026-08-31"
|
||||
updated: "2026-08-31T14:52:06.664545Z"
|
||||
state_hub_decision_id: "b2b958bc-ecee-46ea-9bd2-6edd6afab7b9"
|
||||
```
|
||||
|
||||
## Decision requested
|
||||
|
||||
Approve, revise, or reject the exact batch manifest and SHA-256 above. Approval
|
||||
is limited to the ten named repositories, 85 replacement mappings, zero
|
||||
assignments, and the `helixforge` namespace. It does not authorize a regenerated
|
||||
plan, additional repositories, assignments, or a changed manifest.
|
||||
|
||||
The manifest remains fail-closed: any source fingerprint, Git state, projection
|
||||
state, plan seal, or batch seal drift before a repository executes voids that
|
||||
repository's execution and stops the sequence. Each successfully completed
|
||||
repository is independently durable, pushed, and verified before the next one
|
||||
begins.
|
||||
Loading…
Add table
Add a link
Reference in a new issue