# IF.TTT — Public Sector
IF.TTT for the public sector: public receipts, offline verification bundles, and unambiguous chain-of-custody for external reviewers.

Public sector reality

# Proof must survive procurement.

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

### Third‑party pressure

- Assessors need chain‑of‑custody that survives vendor handoffs.
- Procurement and oversight bodies require documentation that outlives staff turnover.
- Some environments must support offline verification by design.

### What IF.TTT provides

Receipt surface
Stable, no‑login URLs for trace + output + source.
Offline bundles
Triage bundles (lightweight/standard/full) with expected hashes.
Black/white
States what is verified (integrity) and what is not (interpretation).
OFFLINE
RECEIPTS
Triage selector (HTML) https://infrafabric.io/static/hosted/review/trace-bundles/b6547c03/index.html Verifier (HTML) https://infrafabric.io/static/hosted/iftrace.html

## What you can hand to a reviewer

No accounts required. No internal consoles required.

    Trace receipt: https://infrafabric.io/static/trace/<shareId>
    Pack (HTML): https://infrafabric.io/static/pack/<shareId>
    Bundle selector: https://infrafabric.io/static/hosted/review/trace-bundles/<id>/index.html

## Live example

Example trace receipt https://infrafabric.io/static/trace/6qRgcR01kw_qNo63Dbs_ob9n
Sectors Public Sector Enterprise Research Professional · Industries Healthcare Financial Legal
Developers | API