Evidence

A self-contained packet your auditor verifies without us.

Download

Two artifacts, two readers. The bundle is the raw evidence — events, signed checkpoints, public keys, and a README for someone who has never heard of us; it is what the verifier consumes. The examiner packet is the same record rendered for a human: FINRA/17a-4 framing, EU AI Act Article 12 fields, Colorado retention, and the AIUC-1 underwriter controls, each answered from the chain.

Evidence bundle (.json)Examiner packet (.html)

Scoped to tenant_acme/prod. The packet prints to PDF from any browser. These are the sample record's real artifacts — verify them yourself.

How they check it

No account, no network, no registry, nothing from us — the bundle carries its own dependency-free verifier:

node -e "const b=require('./evidence.json');\
  require('fs').writeFileSync('verify.mjs',b.verifier)"
node verify.mjs ./evidence.json

0 verified and anchored

1 tampered, or unreadable

2 usage error

3 chain intact, nothing anchors it

With npm available, npx auditant verify ./evidence.json --offline is the same verifier — the embedded copy exists so the evidence never depends on a registry.

What this packet proves

That the records have not been altered since their checkpoint was signed. Events recorded after the most recent checkpoint sit inside the exposure window and are not yet anchored — the verification report names exactly which those are.

It does not prove completeness. An action that never reached Auditant does not appear here, and no signature can say otherwise. Coverage is a question about your deployment configuration, not about this file.