Export an evidence bundle for auditors

When an examiner asks, the answer is an evidence bundle — a slice of the hash-chained ledger, verified on their machine, not yours.

1. Choose the scope#

Open Evidence → Ledger and select either:

• A run — all events in that run’s range
• A date range — all events between two dates
• A graph version — all events produced by a specific version

2. Export#

Click Export evidence bundle. Orkena assembles the archive: ledger slice, anchors covering the slice, public key, a readable HTML report, and verify.py.

3. Verify before you send it#

On any machine with Python:

python verify.py bundle.zip

chain: 417 events verified · anchors: 3 signatures valid
RESULT: OK

4. Hand it off#

Send the archive to your auditor, their examiner, or store it per retention policy. The bundle is self-contained:

• It does not call any Orkena endpoint
• It does not require Orkena to be online
• It is tamper-evident — any modification returns FAILED with the exact failing event

5. A note for the auditor#

The verifier is dependency-free Python from the standard library. It runs on a fresh machine with no network access. If the examiner wants to see tamper detection, alter a byte in the ledger slice and re-run — the hash mismatch identifies the exact event.