aios/docs/autonomous-release/EXECUTION_PACKAGE.md

AIOS Autonomous Release Execution Package

Release Strategy

V2R1C4 uses a two-stage model:

1. Dormant code deployment.
2. Capability activation through a separate approved release.

Dormant Deployment

The first production release must keep autonomous execution disabled:

AIOS_GITOPS_WRITES_ENABLED=false
AIOS_TASK_PLANE_EXECUTION_ENABLED=false
AIOS_SILENT_RELEASE_EXECUTION_ENABLED=false

Required mode:

deployment_mode=dormant_shadow_only

Required properties:

production_side_effects=false
native_openclaw_enabled=false
native_codex_enabled=false
automatic_release_enabled=false

Deployment Sequence

Verify Integration
        |
        v
Owner Dormant Release Approval
        |
        v
Merge Pull Request
        |
        v
Read final main merge OID
        |
        v
Build Production Artifact
        |
        v
Deploy Dormant Runtime
        |
        v
Create Version Tag
        |
        v
Verify Registry and Baseline

Capability Activation (Separate)

The following require separate approval and evidence:

• OpenClaw native provider
• Codex app-server provider
• Gitea Admin API lifecycle
• Secret Manager V2
• Autonomous production execution

Hard Governance Rules

Never:

• direct write main
• force push
• rewrite tags
• export credentials
• enable autonomous production execution without approval
• use integration OID as production target OID
• update Baseline before remote tag verification