Where does Decionis sit in the stack, and how does it gate execution? #3
|
A question we've been asked by founders more than once: architecturally, where does Decionis really sit? Is it a dashboard humans check, workflow middleware, a logging layer? |
Replies: 1 comment
|
At the runtime layer, consuming the execution call itself. The high-stakes action flows through the decision. Decionis evaluates the intent against the current policy version, and:
It is not an advisory check sitting beside the code path, and not a log written after the fact — the gate is inline, between intent and effect. Every outcome, whichever branch it takes, emits a Decision Dossier. In code, using import { createDecionisExecutionClient } from "@decionis/sdk";
const decionis = createDecionisExecutionClient({
authorityBaseUrl: process.env.DECIONIS_AUTHORITY_URL,
});
await decionis.enforceAndExecute({
request: {
tenant_id: "tenant_demo",
actor: { id: "research_agent", type: "AI_AGENT", runtime: "mcp" },
action: { type: "SEND_PAYMENT", resource: "wallet.usdc", amount: 0.25, currency: "USD" },
policy_refs: ["autonomous-spend-policy-v0.1"],
downstream_target: { system: "payment_api", operation: "send_payment", endpoint: "POST /payments" },
},
execute: async ({ executionToken }) => {
// Runs only if policy allows. The execution token binds this call to the decision,
// so the downstream system can confirm it was authorized.
},
});The The same gate is reachable from several surfaces, so you don't have to hand-wire it everywhere: Related: What is Decionis, in plain terms? · How policies are managed and versioned · Can Decionis govern AI agent tool calls? · How Presence relates to Decionis Have a different architecture or integration question? Start a new discussion — we answer publicly whenever we can. |
At the runtime layer, consuming the execution call itself.
The high-stakes action flows through the decision. Decionis evaluates the intent against the current policy version, and:
It is not an advisory check sitting beside the code path, and not a log written after the fact — the gate is inline, between intent and effect. Every outcome, whichever branch it takes, emits a Decision Dossier.
In code, using
@decionis/sdk: