Rollback Engine
Plan and enforce rollbacks with version tracking when health or promotion fails.
What you will learn
- rollback_plan
- rollback_enforce
- Use deploy_plan_rollback
Prerequisites
Surface
| MCP | rollback_get · rollback_validate · rollback_enforce · rollback_plan · deploy_plan_rollback |
|---|---|
| Config | .ags/rollback.yml |
What this feature does
Rollback Engine records prior known-good versions and required verification after revert. Pair with deploy_plan_rollback for environment-aware plans.
How to call it
Call these MCP tools through your AGS / tower-gov host — rollback_get, rollback_validate, rollback_enforce, rollback_plan, deploy_plan_rollback.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.
- rollback_get
- rollback_plan / deploy_plan_rollback
- Execute revert
- health_check → rollback_enforce
{ "environment": "production", "toVersion": "1.0.0" }What success looks like
Plan cites prior version
rollback_enforce ok after verify
Common failure modes
Rollback without health re-check
Unknown toVersion
Skipping integrity_enforce on artifacts