Same install everywhere we ship: GitHub Action, LangChain (Python & JS), Azure API Management, Slack, Shopify. The gate observes, records a signed Decision Dossier, and never changes caller behaviour β until you decide to enforce. One-line change to flip, reversible without uninstalling.
You don't have to wire every surface β start with the one whose audit you'd be asked about first. Tabs below swap the install snippet to that surface verbatim.
Wraps any LangChain BaseTool. The LLM still picks the tool on the same prompt; Decionis decides if the call fires.
# pip install decionis-langchain
from decionis import DecionisClient
from decionis_langchain import DecionisGateTool
client = DecionisClient(api_key="...", base_url="https://api.decionis.com")
gated_refund = DecionisGateTool.wrap(
inner_tool=send_refund,
client=client,
tenant_id="org-uuid",
workflow_key="refund_execution",
shadow_mode=True, # β every verdict recorded; inner tool always runs
site_base_url="https://decionis.com",
)
agent.bind_tools([gated_refund])
Every gated call produces a signed Decision Dossier. Nothing changes for callers.
Every wrapped invocation produces a signed Decision Dossier. Watch the verdict mix in your Decionis audit log; on enforce, blocks raise DecionisGateRefusal back to the agent.
/verify/decision-dossiers/<id>.One-line change. Reversible without uninstalling.
gated_refund = DecionisGateTool.wrap(
inner_tool=send_refund,
client=client,
tenant_id="org-uuid",
workflow_key="refund_execution",
- shadow_mode=True,
+ shadow_mode=False, # β enforce: inner tool only runs on an ALLOW verdict;
+ # BLOCK / REVIEW / ESCALATE now hold the call
site_base_url="https://decionis.com",
)
Same dossier id, same verify URL, same audit log β the only difference is that blocked verdicts now actually hold the action. If a real workflow regresses, swap back to shadow: the rollback is the same one-line edit, in reverse.
Every dossier ID you record in shadow opens to a public verification page and unfurls with the OG verdict card in Slack / Teams / LinkedIn. Use them in the rollout review packet β the same signed artifact is the proof your CFO, your security reviewer, and your customer's auditor all want.