Evidence Vault
An immutable evidence ledger: prompt hashes, tool parameters and gate decisions./A log nobody can quietly change.
Each decision is chained to the last by hash, so any edit or gap is visible. Records export for regulators and auditors./Every entry is linked to the one before it. If someone changes history, it shows.
What goes wrong without it
Logs can be altered after an incident./Records can be rewritten later.
Evidence is scattered across systems./Proof is spread everywhere.
Auditors cannot reproduce a decision./Nobody can replay what happened.
Four steps, in order
Capture
Record prompt hash, parameters, gate and outcome./Save the key facts.
Chain
Link each record to the previous hash./Tie each entry to the last.
Attest
Commit cryptographic attestation (step 08, ASSURE)./Seal it.
Export
Provide records for review./Hand them over when asked.
Key capabilities
Hash chain
Tamper-evident by construction./Edits are obvious.
Evidence ladder
L0 none to L4 independently certified./Five levels of proof.
JSON export
Machine-readable records./Easy to share.
Framework mapping
Supports NIST AI RMF, EU AI Act, ISO/IEC 42001 evidence (not a certification)./Helps with audits.
Before and after
After an incident, logs disagree and nobody can tell what ran./After a problem, nobody can say what happened.
The chain replays the exact sequence with each gate decision./The log shows each step in order.
Illustrative scenarios. Controls shown are design intent, confirmed by the gates on your own infrastructure.
Related
See it on your own agents.
Architecture by Salem Salah bin Omair AlShamsi. Delivered with our technology partner.