Evidence from the ledger
Every finding is grounded in a transaction record and dispute filing. Reviewers and auditors can trace any claim back to where it came from - not to a model's recollection.
A governed transaction-dispute run, replayed end to end: source-grounded evidence from the ledger, deterministic checks, then a human approval gate where a reviewer approves a partial refund - the customer action stays in preview until approved.
Read-only replay of an illustrative run - no inputs, no production credentials.
A real governed run, replayed in full below - ending in a human refund approval and an auditable proof packet.
Eight events, exactly as the platform recorded them - from intake to a human approval gate that owns the refund. Nothing is simulated past what you see here.
A cardholder dispute was submitted for governed review. The run is registered against flow txn-dispute/v2 and begins under the workspace's controls - every step from here is recorded.
The transaction and its history were parsed and ledger-grounded evidence was extracted - each finding carries a citation back to the record it came from.
Rule-based checks ran against the network chargeback rules. Most passed - one finding caps the refundable amount the gate later approves.
Workspace policies were evaluated against the extracted evidence. One policy trigger fired on cross-border settlement.
The findings were combined into a composite dispute score. The score lands in the partial-refund band, so the run is routed to a human reviewer rather than auto-cleared.
In the partial-refund band -> routed to a human approval gate. No refund is issued automatically.
A reviewer examined the run and approved a partial refund at the gate. The customer-facing refund action stays in preview - a dry-run - until this approval, and only the approved amount is released.
The run ended exactly where governance required: a person decided, the decision is logged, and there is a proof packet anyone can audit later. The refund stayed in preview until a human approved it.
The replay is not a chatbot demo. It is the control plane doing its job: grounding, gating, and proof - the parts a regulator asks about.
Every finding is grounded in a transaction record and dispute filing. Reviewers and auditors can trace any claim back to where it came from - not to a model's recollection.
A partial-band score routes to a person, not an auto-refund. Here the reviewer approved EUR 148.00 - and the customer-facing action stayed in preview until that approval. Nothing is released without it.
The decision, the reviewer, the reasons, and the cited evidence are written once to an append-only audit trail. Months later, you can prove exactly why this refund amount was approved.
PrivateFlow is not certified under any compliance framework. Controls are designed to support compliance preparation. This run is an illustrative, synthetic example.
We'll stand up a governed pilot on your own data - sandbox first, no production credentials required. You decide what the gates do.