Loading…
Execution pattern
Safe code deployment
Require the approval a deploy assumes it already has.
What executes
A pipeline — or an agent with repo access — ships to production, force-pushes, or runs a migration.
What normally goes wrong
The gate is a branch rule that the automation holds the credentials to satisfy. The change lands, and the review that was supposed to precede it happens during the incident.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Environment being targeted
- Whether a human review is attached to the change
- Blast radius of the diff (schema, secrets, infra)
- Change-freeze windows in effect
The gate
Hold any change to a protected environment that lacks a recorded human approval, and treat schema and secret changes as always requiring one.
ALLOW
The deploy proceeds and the dossier records the approval it ran under.
ESCALATE
The deploy waits on a reviewer, with the diff and blast radius attached.
BLOCK
The deploy does not run — for example during a change freeze.
Four stages left to right. Input signals — user or agent identity, context and data, tools and resources, spend and budget, policies, history and reputation, and environment — enter the Decionis Protocol. Inside, the protocol normalizes context and intent, evaluates policies and rules, runs a deterministic risk and policy engine, and explains the reason and evidence. It emits a verdict: ALLOW (authorized), ESCALATE (needs approval or more info), or BLOCK (high risk or out of policy). The verdict drives an enforcement action: allow, block, require approval, or throttle and limit. Every decision is recorded for audit, learning, and continuous improvement.
4 policies implement this pattern
Fork one and change the thresholds. Available today on 3 platforms.
GitHub Deploy Approval Gate
Blocks production deploys during a freeze, escalates out-of-hours releases, and stamps the verdict on the PR.
github
Cursor Protected-Branch Guard
Never force-push to a protected branch, never rewrite shared history — the agent has to open a PR instead.
cursor
GitHub Branch-Protection Gate
Require review before a force push. Blocks history rewrites on protected branches and escalates protection-setting changes.
github
Claude Code Migration & Infra Gate
Holds agent-authored database migrations and `terraform apply` runs until a human signs the blast radius.
claude code
Related concepts
This pattern is one answer to each of these.
What to do next
The same five steps for every pattern in the library.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.