Deployment

The Deployment Engine reads .ags/deployment.yml: ordered environments, required checks / tests / approvals per stage, and what must pass before merging to the protected branch.

Config

schemaVersion: 1
environments:
  - id: local
    requiredChecks: []
    requiredTests: [unit]
    requiredApprovals: 0
  - id: bench
    requiredChecks: [build]
    requiredTests: [unit]
    requiredApprovals: 0
  - id: staging
    requiredChecks: [build, health]
    requiredTests: [unit, e2e]
    requiredApprovals: 1
  - id: production
    requiredChecks: [build, health]
    requiredTests: [unit, e2e]
    requiredApprovals: 1
deploymentOrder:
  - local
  - bench
  - staging
  - production
mergeTarget: main
requireBeforeMerge:
  - bench
  - staging

• environments[] — id + requiredChecks / requiredTests / requiredApprovals
• deploymentOrder — promotion sequence (no skipping)
• mergeTarget — protected branch name
• requireBeforeMerge — environments that must be green before merge

Promotion flow

1. Agent work lands on a feature branch under CAP + staging.
2. Versioning records the bump / changelog for the release candidate.
3. Promotion engine advances local → bench → staging → production only when that environment’s checks pass.
4. Merge to mergeTarget requires the listed environments.

# Promotion check
# environment: staging
# requiredChecks: [build, health]
# requiredTests: [unit, e2e]
# requiredApprovals: 1
# → ok: false until health endpoint + e2e + approval recorded

Works with

• Versioning — what version you are promoting
• Health / Observability / Rollback engines — runtime signals and undo paths
• Deployment showcase — animated pipeline