Evidence pack
Give reviewers the records behind the decision
A review should start with evidence, not a search across systems. One pack holds the decision records a reviewer asked for, the context around them, and a way to check that none of it has changed since export. Download the sample and open it yourself.
What you get in the sample
Own the agent rather than review it? See the same work from the business side: what the agent handled, where it needed a person, and what that saved.
The sample follows a supplier-invoice agent through three decisions. One invoice was paid without anyone stepping in, one went to a person for review, and one was stopped by a rule before payment. It's a small zip file, and everything in it is readable JSON or plain text.
Scroll horizontally to see all columns.
| File | What your reviewer finds there |
|---|---|
manifest.json | The package ID, when it was built, how many decisions it covers, and whether redaction was applied |
sessions/ | One record per decision, with the rule context, the outcome, and the fingerprint that ties it to the integrity proof |
redaction-report.json | What was removed from the export and why |
integrity-proof.json | The references a reviewer uses to check each record against Azure SQL Database Ledger or Solana |
README.txt | How the package is organized and how to verify it |
This sample comes from a VeriProof test environment that uses Solana as its proof provider. In the managed service, Azure SQL Database Ledger is the default. Packages from your own deployment are also signed with your evidence-signing key.
Give reviewers an independent integrity check
The verifier checks the package signature and its external proof references, then reports the result. Your reviewer runs it on their own machine, not in VeriProof's portal.
Each environment uses one proof provider, set when it is created. Azure SQL Database Ledger is the default in the managed service, Solana is the public alternative, and each pack names the provider it used.
Bring decision evidence into your compliance work
The same decision may matter to a privacy review, a model risk assessment, or an audit. Framework mappings help each team connect the records to the requirements it works with.
Put it in front of the people who will read it
Send the sample to your risk lead or internal audit and ask whether it answers the questions they ask today. If it does, we can build the same pack around your agent.
Evidence-pack questions
Yes. It was exported from a VeriProof test environment for a supplier-invoice agent. The companies and people in it are test data.
Yes. A reviewer outside your team can check the exported files and signature with a public key, and each record's fingerprint against Azure SQL Database Ledger or the Solana blockchain. They don't have to trust VeriProof.
No file changed after export, and each record matches the proof recorded for it. Your reviewers use the evidence to assess the decision and reach their own conclusions.
Export permissions and redaction settings determine what the pack contains. Its redaction report shows your team what will be shared.
Each pack covers the records selected for that review, listed in its inventory.