Shadow Mode
Evaluate real actions while your workflow continues. Review the results with your team, then enforce one supported boundary when you are ready.
Decionis products
Decionis is the Execution Authority platform. AgentSafe applies it to agent and infrastructure actions. Commerce Gate applies it to commerce. Presence verifies a named human when policy requires approval. All use the same decision and evidence model.
Decionis · Execution Authority
Your policy → ALLOW, ESCALATE or BLOCK → signed decision evidence
Presence verifies the person when your policy requires approval for a specific action.
Decision Dossier preserves the verdict, policy context and signed evidence for independent verification.
AgentSafe is open-source. It enforces the hosted Decionis authority’s verdict; it does not decide policy locally. Hosted authority and production Enforcement are commercial services.
Customers start in Shadow Mode, where Decionis evaluates real actions without blocking them. Teams review which actions would have been allowed, escalated, or blocked, tune policy, and then enable Enforcement Mode for one boundary. The same integration can be returned to Shadow Mode if necessary.
Shadow Mode measures policy outcomes. A would-have-blocked result is not a prevented loss or a realized saving.
Review representative actions, exceptions and failure cases together. Agree on the policy and approval owners before you enable enforcement.
1
Connect a supported workflow and collect its shadow decisions.
2
Inspect verdicts, policy versions and incorrectly escalated or blocked actions.
3
Confirm approval owners, failure behavior and the return-to-shadow procedure.
4
Enable the reviewed policy at one boundary and assess the results before expanding.
No. Shadow Mode records how your policy would decide while the connected workflow continues. ALLOW, ESCALATE and BLOCK describe evaluation results in this mode. They become enforced outcomes only after you enable enforcement for a supported boundary.
Understanding shadow reportsThere is no fixed duration. Collect enough representative traffic to review routine actions, exceptions and failure cases with the workflow owner. Approve the policy thresholds, escalation owners and rollback procedure before you enforce one boundary.
Policy review and rolloutReview evaluated actions, the shares that would allow, escalate or block, and the underlying action mix over a stated time window. For a rate, use the same evaluated-action population as the denominator. Treat associated transaction value or exposure separately from prevented loss and realized savings.
Metric definitions and methodologyInspect the signed decision and policy version for actions your team considers incorrectly escalated or blocked. Review the rule, approve any change through your policy process, and observe the revised policy before enforcement. Changing a policy does not change the evidence already recorded for earlier decisions.
Policy change controlsYes. Return the connected workflow to Shadow Mode using its documented configuration. Include that procedure in the rollout plan and test it for the specific integration. Shadow Mode resumes observation without blocking; it does not undo actions that have already executed.
Check your integration’s behaviorUpdated · Published by Decionis, Inc. · Contact the team
