Loading…
Execution pattern
Procurement approval
Check delegated authority before the purchase order posts.
What executes
A purchase order, vendor onboarding, or supplier change is submitted for release.
What normally goes wrong
Authority is expressed in a delegation matrix nobody reads at the moment of release. Segregation of duties is assumed rather than checked, so the same person can raise and approve.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Amount against the requester's delegated limit
- Whether requester and approver are distinct
- Vendor risk and onboarding status
- Budget remaining on the cost centre
The gate
Refuse release above the requester's delegated limit, and refuse any release where requester and approver are the same person.
ALLOW
The order posts, and the dossier records the authority it posted under.
ESCALATE
The order routes to whoever holds the limit it exceeded.
BLOCK
The order does not post — for example when duties are not separated.
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.
9 policies implement this pattern
Fork one and change the thresholds. Available today on 5 platforms.
SAP Procurement PO Release Gate
Stops a purchase order releasing to an unapproved supplier or past the requester's authority limit.
sap
Slack Discretionary-Spend Gate
Every spend approval ping above $5k carries the policy snapshot, the requester's authority, and a public verify URL.
slack
IT Ops Pack
Access, change, and procurement gates for internal automation — prove every sensitive change followed the approved path.
servicenow
SAP Vendor Payment Release Gate
Holds a vendor payment run until the bank details, sanctions evidence, and dual approval all check out.
sap
ServiceNow Software Procurement Gate
Blocks unapproved OAuth grants and SaaS signups before anyone clicks through the terms.
servicenow
Slack Refund-Approval Dossier
Turns the refund approval that happens in a Slack thread into a signed verdict carrying the policy version and reviewer authority.
slack
Workday Payroll Circuit Breaker
Catches an out-of-band payroll run — a bank-detail change, an off-cycle payment, a headcount jump — before the money leaves.
workday
Zapier Spend-Approval Gate ($500+)
Require a named approver before any Zap releases spend over $500 — the approval becomes a signed verdict, not a thumbs-up.
zapier
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.