Decionis
Shadow mode for internal approvals

A 👍 in Slack isn't an audit trail.

High-stakes internal approvals — vendor payments, refunds, access changes, exceptions — get decided in Slack threads and buried in ERP approval logs. When it matters, nobody can prove which policy allowed it or why. Run Decionis in shadow mode and every approval leaves a signed Decision Dossier — before anything changes in production.

The ambiguity problem

A $40k vendor payment is approved with a 👍 in a Slack thread — no policy version, no reason on record.
An ERP approval log says “approved by jdoe” but not which exception rule applied or whether due-diligence was complete.
Six months later an auditor asks “why was this allowed?” and the answer is a screenshot hunt.

How shadow mode resolves it

1

Run in shadow mode

Decionis evaluates each internal approval against your policy in parallel — it records a verdict without blocking anything in Slack or your ERP.

2

Every decision is signed

Each approval produces a signed Decision Dossier: requester, policy version, reason codes, blast radius, and the verdict the dossier records: AUTHORIZED, ESCALATE, or BLOCKED.

3

Compare and promote

Review where the human approval and the governed verdict diverge. When you trust it, promote one workflow from shadow to enforcement — day zero, in your own VPC.

What the signed dossier proves

A generic ERP approval log records that someone clicked approve. A Decision Dossier records the institutional authority behind it — verifiable without an account.

Who decided & what was requested
Requester, action, amount, counterparty.
Which policy applied
Exact policy version + the rule digest that governed it.
Why it was allowed / held
Reason codes + a Decision Chain linking related approvals.

Prove your next high-stakes approval

Generate a policy pack for your vertical, run one approval workflow in shadow mode, and hand the signed dossier to risk, compliance, and finance.

Run it in your VPC