Why this exists
We built the skeleton first.
Most systems produce answers and call that “governance”. IF.Trace starts earlier: it produces receipts that a third party can verify without joining your internal world.
Who / Why / What / Where / When / How
Who
InfraFabric operators shipping public, no‑login verification artifacts.
Why
Because “trust us” fails the moment a reviewer asks for proof.
What
A receipt‑first protocol: bind
source_sha256 ↔ output_sha256 under a trace receipt.Where
On a stable public share surface (no login): trace, dossier, packs, and source.
When
At publication time: the receipt is generated and can be verified later during disputes.
How
Hashes + receipts + optional offline bundles; nothing magical, just opposable proof.
What a receipt proves (and what it doesn’t)
Proves
- Integrity binding: the published bytes match the hashes on the receipt.
- Traceability: a reviewer can point to a stable, no‑login receipt.
- Replay: verification still works during disputes (offline bundles when needed).
Does not prove
- Intent, interpretation, or “correctness” of a narrative.
- That a control is effective—only that the evidence exists and is bound to the record.
- Compliance scope (people, policy, contracts); receipts are inputs to governance.