No-login verification

IF.Trace

Confidential work → open verification.

Anyone can check the proof links. Nobody needs access to your internal systems.

Verified means
Hashes match (black/white).
Not implied
Truth, compliance, or interpretation.

How it works

A receipt-first sequence. Fast to understand. Hard to fake.

Step 1
source_sha256

Keep the source private

You do not publish the confidential source.

Step 2
output_sha256

Hash what you will share

You hash the output you can show to others.

Step 3
receipt_url

Publish a receipt

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

Step 4
verified: true/false

Third parties verify

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.

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