Check the signature
Confirm that the file inventory carries the expected export signature.
Tamper-evidence walkthrough
Give reviewers evidence they can verify
Has this record changed since it was exported? Your reviewer can answer that alone, offline, with a verifier that needs no VeriProof account and takes nothing on trust from us.
An evidence pack arrives for review
An evidence pack for an AI-assisted claims decision lands with your reviewer. Before reading a word of the case, they want to know one thing: are these the files that were exported, or has something been touched since?
The verifier answers that in seconds. It checks the files and the export signature on the reviewer's own machine, with no VeriProof login involved.
Three checks connect the files to their source
Compare the files
Are any files changed, missing, or extra? The verifier compares the package contents with the signed inventory.
Verify the source proofs
Trace the export back to its source records through Azure SQL Database Ledger or Solana proofs, whichever your environment uses.
A changed decision leaves a mismatch
Suppose someone edits the decision file after export. Its content no longer matches the signed inventory, and the verifier reports the mismatch.
Adding or removing files also changes the inventory. Replacing the inventory itself requires a valid signature from the trusted key.
Azure SQL Database Ledger by default, Solana when you choose
Azure SQL Database Ledger
Keep the integrity record in Azure. The verifier checks the source record against protected database digests through authorized access.
Solana
An environment set up with Solana publishes a public fingerprint. The verifier checks it against the referenced transaction.
A result your reviewers can act on
Verified
The signed inventory and external source proofs passed their checks. The pack is ready for its content review.
Mismatch
A file or proof differs from the expected value, giving the reviewer a specific discrepancy to investigate.
Verification incomplete
Missing access, an unavailable provider, or a fingerprint not yet recorded can prevent verification. These results identify what needs attention; they do not establish tampering.
Integrity and accuracy answer different questions
Verification proves the files are the ones that were exported and that they trace back to the source records. Whether the business facts inside them were right is a different question, and that one is still the reviewer's job.
The redaction report shows what was removed or changed for export, so nobody mistakes a deliberate redaction for tampering.
Why the business owner cares
A pack that verifies is what lets a risk committee approve an agent without taking anyone's word for it. When you raise the agent's limits later, the question "can we show what it did?" is already answered. Integrity is the part an auditor checks. What it pays for is getting agents live, and keeping every one of them under control.
Verification questions
Yes. Reviewers can check the exported files, signature, and source proofs independently, without using the VeriProof portal.
A transaction is one part of the evidence. The verifier also checks the package signature, file inventory, and connections to the source records.
Follow the verification guide to run the checks and understand the results.
Open a sample pack
Hand your risk team a real pack and let them walk through what a reviewer receives. If it does not answer their questions, you will know quickly.