Skip to main content
Use the evidence verifier for portable ZIP packages shared with customers, auditors, reviewers, or support teams.

​
What verification checks

  • The package type and version are recognized.
  • Manifest counts match the included batch files.
  • Record hashes chain from genesis to head.
  • Batch hashes match their manifest entries.
  • Receipt rows match the included records.
  • Consent rows match consent events in the export.
  • Policy snapshots are attached when required.
  • Export scope matches the included date, lane, and sequence boundaries.

​
Large packages

The verifier should summarize first:
  • package identity
  • record count
  • batch count
  • chain status
  • policy version
  • first and last sequence
Only load record details when a reviewer opens the log explorer. For large packages, inspect records in pages and filter client-side against the local batch data.

​
Receipt drilldown

When a reviewer opens one record, show:
  • action, actor, target, and timestamp
  • Lodger received time
  • API key identity when available
  • environment, server, request, session, and trace context
  • event hash and previous hash
  • related event and receipt references
This keeps the main verification result simple while preserving the full evidence trail.