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
Pick the product for the actions you want to stop first. AgentSafe checks your agents' API calls, MCP tools and deployments. Commerce Gate checks prices, orders, promotions and refunds on your store and marketplaces. Presence verifies a named human when policy requires approval. Both products use the same policy decisions and signed records.
One policy check before the action commits
Your policy → allow, escalate to a person, or block → a signed record you can check
Presence verifies the person who approves, when your policy asks for one, for that exact action.
Decision Dossier keeps the verdict, the policy in force and the signature, so you can check it without asking us.
AgentSafe is open source. It enforces the verdict of a Decionis authority: the hosted service, or one you run in your own cloud under a commercial licence (Private beta). The open-source gateway never decides policy by itself.
You start in Shadow Mode: every action on the workflow you connect is checked, and nothing is blocked. You see what would have been allowed, held for a person or blocked, adjust your policy, then switch on enforcement for one action. You can put the same integration back into Shadow Mode at any time.
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
