Commerce checkout
Point of sale
Catches: A stacked coupon, price-drift, or rogue agent pushes an order below the cost-basis margin floor.
Verdict: BLOCK before the checkout token is issued — signed dossier attached.
Loading…
The Point of Execution
Start where the money moves. Then govern every point of execution.
Decionis owns one thing decisively today: margin protection at the point of sale. But the gate that blocks a bad checkout is not a commerce feature — it is a deterministic decision layer for any high-stakes action. The wedge is checkout. The platform is the point of execution: vendor deals, visa applications, code deploys — anywhere an agent or a person is about to commit something you cannot cleanly undo.
Live wedge
Where the money moves — checkout
Cost-basis margin floors enforced inline at the point of sale in under 120ms. Proven on Shopify with 100+ installs and thousands of governed gates.
The expansion
Every point of execution — any workflow
The same signed, deterministic verdict — proceed, hold, block, or escalate — in front of any decision where authority moves and mistakes are expensive.
You do not need to be on Shopify or an ERP
Commerce and ERP are the surfaces where we proved it, not the requirement. The Universal Action Gate is a single API/webhook call: any agent, service, or workflow that asks the gate before it acts is governed by the same policy graph and produces the same signed Decision Dossier. No native integration required — just a call at the moment of execution.
Agent-error templates beyond checkout
The same gate catches the expensive mistake in each domain. Checkout is live today; the rest are deployable policy patterns on the Universal Action Gate — the pattern is ready, not a pre-packaged one-click template yet.
Live
Code deploy / infra change
Point of deploy
Catches: An agent or CI action ships a config change that violates a hard policy — disabling auth, opening a security group, or flipping a production flag.
Verdict: BLOCK or ESCALATE before the change applies, with the violated rule cited.
Vendor deals & procurement
Point of commitment
Catches: An agent or rep commits spend or contract terms beyond policy before a vendor reaches production.
Verdict: ESCALATE to the named approver with reason codes; restrain the commitment.
Visa & eligibility submissions
Point of submission
Catches: A managed workflow would submit an application that fails eligibility or completeness policy.
Verdict: HOLD or ESCALATE before submission so an ineligible filing never leaves the door.
One policy graph across many workflows
Point-of-execution governance is not one gate at a time. A Decision Chain links related verdicts across domains into a single accountable record, so a later action can depend on an earlier decision instead of trusting a scattered trail of tickets and logs.
Step 1
Vendor onboarding
Supplier qualification decision — signed, with policy version and evidence.
Step 2
Purchase-order approval
PO checked against spend policy and the qualified-vendor decision above.
Step 3
Payment release
Disbursement gated on both prior verdicts — no orphaned approval, no silent bypass.
Every step is its own signed Decision Dossier; the chain links them into one Decision Ledger record for cross-domain accountability.
Open, queryable Decision Ledger API
RoadmapToday the Decision Ledger is the durable, signed record behind every verdict. The next step — on our roadmap, not shipped yet — is to expose it as an open, queryable API that AI workflows can consume directly: ask the ledger whether a decision was made, which policy governed it, and how authority moved, so cross-domain agents share one accountable source of truth instead of re-deriving trust per system. We will label it live here the day it ships, and not before.