How verification works

Black/white: what the receipt proves vs what it doesn’t.

1. 1
   Bind source ↔ output

   Hash the exact source bytes and the exact output bytes.
2. 2
   Publish a trace receipt

   A public page that links the hashes, time, and versioning.
3. 3
   No‑login share surface

   Stable URLs keyed by a single shareId (trace, dossier, pack, source).
4. 4
   Optional: offline triage bundles

   Lightweight/standard/full bundles for constrained environments.

If it’s not verifiable, label it as a gap. Don’t endorse it. This is how you keep governance legible to outsiders.