aios/docs/gitops/APPROVED_PRODUCTION_EXECUTOR.md

AIOS Approved Production Release Executor

Status: implementation artifact for governed protected-PR integration.

Why this exists

The deployed aios-silent-release-controller is intentionally shadow-only. It rejects production execution unless a trusted builder/orchestrator factory is wired. V2R1C7 already completed post-merge deterministic build, staging, rollback, evidence closure and exact Owner approval, so rebuilding inside the production executor is both unnecessary and a deadlock source.

This patch adds a separate one-shot production executor. It does not turn the shadow controller into a production service.

Exact V2R1C7 binding

• target: c7adece1cc8beffe7c718d53c775898b45d6c7f8
• evidence: 8c2898baf07195b9861ed2ff74f03a71674ec9e9
• artifact: ce09a46f28b453634784abceda4597fd51c3aa0838e72a5ad5fefd03d58b949e
• approval plan: sha256:c8199d638c2bb2e4896ca9b219ca52db79713bee007df05653ab348905d6cf28

The executor requires a root-owned accepted authorization receipt that matches all five fields. It does not accept caller-supplied replacement evidence.

Execution order

1. exact authorization + artifact + Git lineage preflight
2. annotated V2R1C7 Tag publication and Authority/network/Gitea verification
3. deploy exact artifact; health must report ACTIVE and exact target/digest
4. Registry atomic finalization
5. authoritative Production Baseline CAS finalization last
6. read back Tag/runtime/Registry/Baseline and require exact consistency

Tag implementation

governed_tag_adapter.py is a thin adapter over the repository's existing gitea_tag_publication.TagPublisher. It intentionally calls only the existing tag verification/publication subroutine and never calls legacy TagPublisher.publish() because that legacy operation finalizes Baseline before the product runtime is ACTIVE.

Runtime finalization

release_metadata_adapter.py writes no Git refs. Registry and Baseline are runtime state only and are atomic/CAS guarded. Baseline apply independently requires exact ACTIVE health, exact formal tag, exact Registry, and the exact previous Baseline SHA-256.

For this release the previous production baseline is V2R1C5. V2R1C6 has a formal tag but was never deployed, so rollback must return to V2R1C5.

Governance

• force push: forbidden
• tag rewrite/delete: forbidden
• direct main push: forbidden
• V2R1C5/V2R1C6 mutation: forbidden
• plaintext secrets in Git: forbidden
• exact binding replacement: manual Owner review required
• after a verified Tag, uncertain errors become reconciliation-required
• global AIOS_GITOPS_WRITES_ENABLED stays false; this executor is a narrow, separately installed production capability.