# IF.TTT — Legal
IF.TTT for legal workflows: chain-of-custody for drafts, evidence, and decisions. Receipts, not recollections.

Legal reality

# Courts don’t accept “trust me.” They accept provenance.

Legal and compliance teams live in the difference between “we believe this happened” and “we can prove this happened.” IF.TTT is built to make that proof portable.

### Third‑party pressure

- Disputes demand reproducibility: the exact input and the exact output.
- Evidence must be time‑scoped: “what did we know, when did we know it?”
- Chain‑of‑custody must survive handoffs (vendor → customer → counsel → auditor).

### What IF.TTT provides

Integrity
Hash receipts bind the published bytes to what was reviewed.
Portability
No‑login links and offline bundles for external review.
Clarity
Explicit “proves / does not prove” framing reduces ambiguity.
EVIDENCE
CHAIN‑OF‑CUSTODY

1. 1
   Define the artifact
   Identify the exact bytes to be relied upon.
2. 2
   Hash it
   Publish `sha256` as the integrity baseline.
3. 3
   Issue the receipt
   Trace page binds source ↔ output with a trace id.

## Artifacts that make disputes less expensive

You can hand these to an external reviewer without shipping your internal systems.

    Trace receipt: https://infrafabric.io/static/trace/<shareId>
    Output (raw): https://infrafabric.io/static/dossier/<shareId>/download
    Review pack: https://infrafabric.io/static/review/<shareId>
    Offline bundles: 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