Legal

Citations as chain-of-custody

Legal trust is not persuasion. It’s provenance. IF.TTT treats citations as load‑bearing structure: every claim links to a source you can independently verify.

Pain points (today)

“Where did this number come from?” becomes a week of inbox archaeology.
Evidence exists, but can’t be produced fast enough to matter.
AI summaries create risk when the underlying record isn’t bound to the output.

What IF.TTT makes easier

Attach a trace record to an output: source hash → output hash → receipt.
Publish a no‑login receipt surface for third‑party review.
Export offline bundles when the reviewer can’t (or won’t) log in.

Debate extracts (roles)

General counsel

“Show me the provenance. If it can’t be produced, assume it will be disputed.”

Litigator

“A confident summary without receipts is discoverable pain.”

Compliance

“We don’t need another dashboard. We need a defensible record.”

Open verification

Receipts are built for external reviewers: stable URLs + HTML fallbacks.
Offline verification exists for adversarial or air‑gapped review.
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`