ACTION TYPE · SHIP A CHANGE
Changes that reach production because the pipeline said yes.
Configuration pushes, releases, infrastructure changes, feature flags. Coding agents and release bots already ship; the change-management rules exist, and the pipeline is where they are supposed to hold.
Who runs it today: AI coding agents, release bots, infrastructure-as-code pipelines.
The rules that usually govern it
- Only inside an approved change window
- Reviewed by someone other than the author
- A signed rollback plan for critical systems
- No change during a declared freeze
Typical rule shapes, not a claim about any one organisation. A pilot starts from yours.
Where rules like these break
What the gate does
- 01
Checks each request against the proven policy before it executes. What fails never reaches the system.
- 02
Refuses when a window or population the rule depends on is missing or does not reconcile, instead of guessing.
- 03
Seals every decision, allow or block, so it can be re-checked without us.
