IF.Trace

No-login integrity receipts

Prove an output matches a confidential source.

Publish a receipt. Anyone can verify the bytes later—without access to your internal systems.

Verified means the hashes match (black/white). It does not imply truth, compliance, or interpretation.

See a live receipt Read the paper
What is verified
The output bytes match the receipt hash.
What is not verified
Whether the output is correct, true, or compliant.
Receipt preview
This is what a third party sees. No login. One question: do the bytes match the hash?
Open
shareId
6qRgcR01kw_qNo63Dbs_ob9n
verified
yes / no
proof links
/static/trace/<shareId>
/static/pack/<shareId>
/static/pack/<shareId>.md

How it works

Four steps. One outcome: verified or not.

  1. 1

    Keep the source private

    source_sha256

    You do not publish the confidential source.

  2. 2

    Hash what you will share

    output_sha256

    You hash the output you can show to others.

  3. 3

    Publish a receipt

    receipt_url

    A receipt binds source → output so the debate stays grounded.

  4. 4

    Third parties verify

    verified: true/false

    They verify hashes match—no logins.

What you get (black/white)

Stable proof links

Share a URL that survives handoffs and time.

  • https://infrafabric.io/static/trace/<shareId>
  • https://infrafabric.io/static/pack/<shareId>
  • https://infrafabric.io/static/pack/<shareId>.md

Offline bundles

For reviewers who can’t download or can’t log in.

  • https://infrafabric.io/static/hosted/review/trace-bundles/<id>/index.html

HTML fallbacks

Some reviewers can open HTML but refuse downloads—publish both.

Quantum-ready (optional)

A post-quantum receipt can exist for the trace (QUANTUM READY, not “quantum-secure”).

Browse by sector

Same mechanism, different pressure.

Public sector reality

Public Sector

Public accountability is a third‑party problem: reviewers need proof without getting access to your internal systems. IF.Trace turns “trust us” into receipts that a stranger can verify.

Open →

Enterprise pressure

Enterprise

In enterprise environments, audit friction becomes a tax on delivery. IF.Trace provides proof that third parties can verify without joining your internal world.

Open →

External review reality

Research

Research reviewers need proof, not your whole environment. IF.Trace makes it practical to share verifiable outputs while keeping raw data controlled.

Open →

Client handoff reality

Professional Services

When advice, drafts, and deliverables become contested, you need custody that holds up. IF.Trace makes your outputs verifiable without exposing your internal process.

Open →

Common failure modes

Real buyers don’t want more dashboards. They want a third party to stop arguing.

External reviewers cannot log in
They refuse account creation or downloads.
IF.Trace response
HTML view + offline bundles + stable URLs.
Vendor handoff breaks the proof chain
Links, access, or context disappears after the handoff.
IF.Trace response
No-login proof links that survive time.
Disputes months later
People argue about what existed at the time.
IF.Trace response
Receipts bind source → output; integrity is checkable later.
contact