The AI Tutor will answer grounded in this lesson's cited source (portal_guide: PRD-101) and key concepts — authority Informational. Not yet enabled.
Evidence Vault
What it is. Independently verifiable evidence for your AI governance: every piece of evidence your governance runs capture is anchored in a tamper-evident, hash-chained ledger, and exported as a regulator-ready dossier.
Who it's for. Compliance officers and audit leads who have to prove — to an internal auditor, an external auditor, or a regulator — that governance records existed at a point in time and have not been altered since.
Features and what they mean
| Feature | What it means |
|---|---|
| Tamper-evident ledger | Every record is hash-chained to its predecessor. Editing, deleting or reordering history breaks verification — that is the audit claim. |
| Signed dossier export | One click produces a regulator-ready PDF dossier of your evidence, stamped with its signing source. |
| Selective disclosure | Prove one control to an auditor without exposing your whole ledger — a cryptographic proof covers just the records you share. |
| Offline verification | The dossier can be verified without access to the platform — the proof travels with the document. |
What you put in, what you get out
| You put in | You get out |
|---|---|
| Nothing extra — evidence accumulates automatically as governance runs execute | A growing, verifiable evidence library per control |
| A dossier request (one click or one API call) | A regulator-ready PDF with an integrity seal and signing-source header |
| A record selection for an auditor | A selective-disclosure proof for exactly those records |
Your first session
- Open Evidence in your workspace — the library, expiry tracking and review cycles live there.
- Run any governance activity (or AI Discovery) — watch evidence rows appear against controls.
- Export a dossier and check its signing-source stamp.
- Hand the dossier to a colleague and have them verify it — that is the product's core promise, exercised.
Honest limits
Exports are currently stamped UNSIGNED until the managed signing key (KMS) is configured in production — the chain of custody is captured either way, but third-party non-repudiation switches on with the key.
Access: granted with the Governance Platform; dossier API at /api/v1/evidence-vault/dossier.