For evidence recipients
They send the evidence.
You check it.
A vendor’s decision is your review question. Take the source record, recover its context and check the proof outside their application.
Free verification runs now. Scoped review portal: Roadmap.
Available in the preview
Verify. Don't trust.
Download the synthetic receipt and the separately published development trust pin. The offline verifier checks the envelope hash, chain link, inclusion proof and signature against the trust material you choose.
No recipient subscription is needed to run the verifier. It checks cryptographic integrity; it does not establish that a recorded claim is true or that the collection is complete.
Development signer means integrity under a published dev key and no independently trusted time.
A public key included in a receipt is not its own reason to trust it. Check the separately published pin and the limits of the selected signer.
Roadmap · Recipient portal
Review the shared scope, free.
A producer will share an examination pack with a defined scope. The recipient will review the included records, collection cutoff, missing evidence and verification instructions without buying a seat.
Recorded facts will stay separate from generated interpretation. Imported history will show its claimed event dates alongside the dates Recourse received and sealed it.
The recipient’s view
The shared pack and its evidence boundary. Scoped review is not access to the producer’s whole ledger. Access enforcement and reviewer identity are part of the planned portal.
The producer’s workspace
Capture, prepare the pack and manage evidence work. Producers pay for these capabilities; the person asked to examine their evidence does not pay a reviewer seat fee.
A downloaded copy can travel beyond a portal. The planned access scope must not be mistaken for control over copies already exported.
One handover can change the next request.
The intended distribution loop starts with a useful pack. The recipient can ask another vendor for the same evidence structure, without joining the first vendor’s system.
A vendor sends a pack.
Source records, dates, collection boundary, missing evidence and a way to check the proof.
The customer reviews it.
Verify outside the vendor’s application. Ask about the evidence gaps and the meaning of the recorded decision.
The customer asks other vendors.
Request the same structure for their AI-assisted risk decisions. Compare evidence on a boundary the reviewer can see.
This is the intended adoption path, not a claim about existing customers or a live recipient network.
Start with one reviewable pack.
One workflow, one integration and one mock examination. Pilot price is agreed separately.