Deployment Engine

Define environment ladders, required checks/tests, and enforce deploy order.

What you will learn

• Author .ags/deployment.yml
• deploy_status
• deploy_enforce

Prerequisites

• Mount PluginHost and merge MCP tools

Surface

What this feature does

Environments declare requiredChecks, requiredTests, and approvals. deploymentOrder is authoritative; requireBeforeMerge lists envs that must be green before mergeTarget.

Configuration

Wire these surfaces first: .ags/deployment.yml.. Treat them as the contract agents must not invent around.

schemaVersion: 1
environments:
  - id: local
    requiredChecks: []
    requiredTests: [unit]
    requiredApprovals: 0
  - id: staging
    requiredChecks: [build]
    requiredTests: [unit]
    requiredApprovals: 0
  - id: production
    requiredChecks: [build, publish-dry-run]
    requiredTests: [unit]
    requiredApprovals: 1
deploymentOrder: [local, staging, production]
mergeTarget: master
requireBeforeMerge: [staging]
graphArtifact: docs/deployment-map/latest.json

How to call it

Call these MCP tools through your AGS / tower-gov host — deploy_get, deploy_validate, deploy_enforce, deploy_status, deploy_plan_rollback.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. deploy_get
2. Satisfy checks/tests
3. deploy_status
4. deploy_enforce

{ "environment": "staging" }

What success looks like

deploy_status shows ladder progress

deploy_enforce ok

Common failure modes

Skipping staging into production

Missing requiredTests evidence

Approvals < requiredApprovals

Related reference

• Deployment
• Configuration