| What it governs | The business decision/action at the point of execution — authorize / block / escalate / restrain on this refund, payout, order margin, or payment-authorization message | The compute environment the agent runs in — process isolation, network egress, credentials, CPU (the sandbox) |
|---|
| Semantic awareness | Understands the action’s economic/business content — margin, refund amount, payroll variance, duplicate invoice — and evaluates it against a versioned policy bundle | Blind to business meaning by design — governs approved endpoints and spend ceilings, not policy on the action itself |
|---|
| Interception point | Intercepts and consumes the action inline at the semantic boundary — ISO-8583 payment authorization, native bot actions, workflow pre-commit | Intercepts at the process/syscall/network boundary — the microVM sandbox around the agent |
|---|
| Core artifact / proof | Signed, reproducible Ed25519 Decision Dossier, offline-verifiable by a third party against a public JWKS | Replayable execution records — a process trace rather than an independently verifiable signed verdict |
|---|
| Relationship | Complementary — an agent inside a Runta sandbox can call Decionis for the verdict and a single-use, action-bound execution grant | A runtime-isolation substrate that composes beneath a decision-authority layer, not a replacement for one |
|---|
| Policy-gated execution before money moves or system state changes | Yes. Your team gets the policy answer before a workflow, approval, transaction, or system state change continues. | Runta enforces egress allow-lists and spend caps on the agent’s process, but does not return a policy verdict on whether a specific business action is allowed before the workflow, transaction, or state change continues. |
|---|
| Decision Dossier and audit trail | Yes. Every certified execution can return a portable signed Decision Dossier plus broader org-level validation packs. | Runta markets replayable execution records (process replay) rather than a portable, cryptographically signed Ed25519 Decision Dossier a third party can independently verify offline. |
|---|
| Confidence-scored single verdicts | Yes. Decionis returns one certified verdict such as authorize, block, escalate, or restrain rather than leaving multiple interpretations at the point of action. | Runta governs process, network, and credential access rather than returning a single certified verdict (authorize / block / escalate / restrain) carrying the policy version and business math for the action. |
|---|
| Do-nothing / restraint logic | Yes. Decionis can deliberately hold or restrain action when confidence, evidence, or policy is insufficient. | Runta contains the runtime by construction (isolation, egress control) rather than deliberately holding or restraining a specific business action when policy inputs like cost basis, entitlement, or variance are missing. |
|---|
| Execution-before-money-moves governance | Built as the execution authority layer before spend, approvals, routing, or high-stakes operations proceed. | Runta caps spend and restricts endpoints at the process boundary rather than evaluating the business action itself — this refund, this payout, this payment-authorization message — before money moves. |
|---|
| Org-wide and per-decision kill switches | Available. Decionis keeps both org-wide and per-decision kill switches with audit logging. | Runta offers process-level isolation and egress control rather than a governed org-wide and per-decision monitor→enforce kill switch over business actions, backed by a signed audit record. |
|---|