Promotion Engine

Gate promotions across environments with promote_plan / promote_enforce.

What you will learn

Configure promotion ladder
promote_plan
promote_enforce

Prerequisites

Deployment Engine

Surface

MCP	promote_get · promote_validate · promote_enforce · promote_plan
Config	.ags/promotion.yml

What this feature does

Promotion Engine consumes deployment order plus promotion-specific items/approvals. Agents plan a promotion, attach evidence, then enforce.

Configuration

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

.ags/promotion.yml (sketch) yaml

schemaVersion: 1
enabled: true
items: []
graphArtifact: docs/promotion-map/latest.json

How to call it

Call these MCP tools through your AGS / tower-gov host — promote_get, promote_validate, promote_enforce, promote_plan.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

promote_get
promote_plan
Collect check evidence
promote_enforce

MCP: promote_enforce json

{ "from": "staging", "to": "production" }

What success looks like

promote_enforce ok with evidence

Ladder step advances

Common failure modes

Promote without health_check

Wrong from/to pair

Missing approval on production

Related reference

Deployment