# IF.TTT — Finance
IF.TTT for fintech and regulated finance: prove provenance, non-repudiation, and dispute-ready receipts for auditors and regulators.

Finance reality

# Regulators don’t buy narratives. They buy receipts.

In regulated finance, the first question after an incident is not “what did the model mean?” It’s “show me the evidence chain: inputs, outputs, timestamps, and who approved what.”

### Third‑party pressure

- Model risk / validation teams need reproducibility.
- Internal audit needs non‑repudiation and time‑scoped proof.
- Regulators need chain‑of‑custody that survives disputes.

### What IF.TTT provides

Receipt
A public trace page binding `source_sha256` ↔ `output_sha256`.
Dispute
Offline bundles for later verification without relying on internal access.
Clarity
Black/white separation of what’s verified vs what is interpretation.
PROCESS
RECEIPT‑FIRST

1. 1
   Hash the source
   Compute `source_sha256` of the exact bytes.
2. 2
   Hash the output
   Compute `output_sha256` of what is published.
3. 3
   Publish the trace
   Receipt links hashes + trace id + version.
4. 4
   Share without login
   Stable URLs keyed by `shareId`.

## Artifacts you can hand to third parties

This is the point: reviewers shouldn’t need your VPN.

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