Government

Legible to the governed

Public-sector trust fails when verification requires insider access. IF.TTT publishes no‑login receipts so reviewers can verify provenance without joining your systems.

Pain points (today)

Oversight asks “prove it” and the evidence is locked behind accounts and approvals.
Procurement demands controls; operations ship exceptions.
Audits become calendar events instead of continuous verification.

What IF.TTT makes easier

No‑login receipt surfaces for third‑party review.
Offline bundles for air‑gapped or constrained environments.
Clear “verified vs not verified” semantics (black/white, not vibes).

Debate extracts (roles)

Procurement

“If the proof requires a login, it won’t survive procurement.”

Security

“A policy that can’t be verified becomes a waiver workflow.”

Oversight

“Give me receipts, not reassurance.”

Open verification

Receipts are stable, no‑login, and designed for external review.
HTML fallbacks exist for restricted “web fetcher” environments.
Start with the public IF.TTT explainer: infrafabric.io/static/hosted/ifttt/

if.ttt

what third parties can verify

1

Ingest a source

PDF • policy • dataset • report
2

Mirror + claim register

keep the evidence payload intact
3

Bind with a trace

hashes • signatures • provenance ID
4

Publish public receipts

no login • stable URLs • HTML fallbacks
5

Optional triage bundles

lightweight • standard • full
6

Offline verify

verify with `iftrace.py`