Sample Audit Bundle
What a KairoNull evidence package looks like.
This is an anonymised example of the audit output produced by the Umbra Trust Protocol for a regulated financial institution. Every field shown below would be present in a real export. Hashes and identifiers are illustrative but structurally accurate.
All records in this sample are synthetic. No real AI decisions or personal data are included. The cryptographic structure, field names, and verification process shown are identical to what enterprise customers receive in production.
Contents
1. Bundle header and chain state
Every audit export begins with a bundle header that identifies the ledger, the export range, and the chain height at time of export. This header is itself hashed and included in the signed manifest.
2. Evidence record (policy pass)
A standard AI decision record where all governance invariants were satisfied. This is the normal-state record that would appear in the vast majority of an organisation's decision volume.
Policy gate results
Chain link hashes
3. Evidence record (policy block)
A record where a governance invariant was not satisfied. The AI decision was blocked before it reached the end user. The record of the block is itself sealed to the ledger, creating auditable proof that governance controls operated correctly.
Policy gate results
Note: block records are sealed to the ledger with the same SHA-256 chain as pass records. The evidence that a block occurred is tamper-evident. A regulator can verify both that the AI produced the output and that it was correctly prevented from reaching the end user.
4. Independent verification
Every record in the bundle can be verified at kaironull.com/verify by pasting its output hash. The tool returns the chain position, the policy gate state, and the RFC3161 timestamp, with no account required and no data sent to KairoNull servers beyond the hash itself.
Try verifying one of the records above
No account required. Verification is stateless. Your query leaves no trace.
5. OpenSSL verification command
For technical teams and auditors who prefer command-line verification, every audit bundle includes a verification manifest that can be checked with a single OpenSSL command. No KairoNull tooling required.
openssl dgst -sha256 -verify kaironull_public_key.pem \
-signature bundle_manifest.sig \
KN-BUNDLE-2026-0601-EMEA-FIN-001.json
# Expected output:
Verified OK
echo -n '{"record_id":"KN-REC-1284941","output_hash":"c5e9d1f4..."}' \
| openssl dgst -sha256
# Compare to chain entry at position 1,284,941
a1f5c9d3b7e2a4f8c1d6b3e9f2a7c4d8b1e5f3a9c2d6b4e8f1a3c7d2e9f5a8b4
The public key used for verification is provided to every customer at onboarding and can be stored independently. You do not need a KairoNull account or backend access to run this verification at any future point.
Ready to see this with your own AI decisions?
A single AI call is instrumented in under 60 seconds. Standard Deployment goes live in 1 to 5 days; Enterprise engagements run a structured 90-day pilot before full production sign-off. Every path starts with a 30-minute scoping call.