Loading…
Execution pattern
Cloud spend increase
Commit infrastructure budget deliberately, not by autoscale.
What executes
An autoscale event, a new cluster, or a provisioning script commits ongoing cloud spend.
What normally goes wrong
Infrastructure spend is committed by systems reacting to load, at a rate nobody chose. The decision to spend is made by a scaling rule and reviewed by a monthly bill — a different shape from an agent looping on tokens, and one that compounds.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Delta against current daily burn
- Contract value of the workload being served
- Whether the increase is temporary or structural
- Budget remaining for the period
The gate
Escalate increases that move daily burn past the agreed threshold, and refuse those that would exceed the contract they serve.
ALLOW
The resource provisions and the commitment is recorded.
ESCALATE
A large increase waits on whoever owns the infrastructure budget.
BLOCK
The increase does not proceed.
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 4 platforms.
AWS Agent Egress & Spend Gate
Opens sandbox egress only for the exact target the grant covers, and stops a run that would blow the account budget.
aws
Claude Code Migration & Infra Gate
Holds agent-authored database migrations and `terraform apply` runs until a human signs the blast radius.
claude code
Copilot Token-Budget Guard
Reserves projected model spend before the prompt is forwarded and restrains runs that would blow the project wallet.
copilot
SaaS Ops Pack
Cloud spend, discount, and entitlement gates — stop runaway burn, margin leakage, and unsupported entitlement changes.
sdk
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.