Loading…
The Decision Dossier Blueprint
Prove why every automated payout fired — before your auditor asks.
For engineering and risk leads at fintechs running automated money movement. When SOC 2 or an auditor asks “who approved this,” the answer should already be a signed record.
No signup to run the trace. It executes entirely in your browser — no data leaves the page.
decision_dossier.json
{
"dossier_id": "dsr_3f9a21c7",
"surface": "shopify",
"action": "a high-risk checkout or refund exception",
"verdict": "BLOCKED",
"policy_version": "global_spend_control_v4.3.0",
"reason_code": "velocity_ceiling_exceeded",
"signature": "ed25519:6f7a…3e92",
"evidence_chain": "verifiable — tamper-evident",
}
Every Decionis decision emits a record like this — portable, signed, and verifiable.
If this sounds like your week
Automated payouts and refunds fire with no portable proof of why.
“Who approved this?” turns into a week of log archaeology.
Auditors want evidence, not screenshots of a dashboard.
The blueprint, in three moves
1
Run the trace
Pick Shopify and watch the policy evaluate a high-risk checkout or refund exception in real time. Nothing leaves your browser.
2
Deploy in shadow
Point Decionis at the same flow in listen-only mode. It measures what it would catch without touching your live pipeline.
3
Flip to enforce
When the evidence convinces you, switch one policy to enforce. Every decision from then on emits a signed dossier.
Start with the trace. The rest follows.
Or fork a ready-made policy pack from the Open-Policy Exchange.
Runs in shadow mode — zero live pipeline risk
Signed, portable, verifiable records
No signup to try the trace