Open governance, readable by outsiders

# Receipts, not vibes.

IF.TTT is a receipt‑first governance layer. It binds a source artifact to an output with a trace page, stable no‑login links, and optional offline bundles anyone can verify.

No‑login Public proof surface
Offline Triage bundles
Black/white What’s verified vs what isn’t
Try a live trace See vertical fit

We don’t claim “compliance”. We support audits by producing verifiable receipts that third parties can check without your credentials.

VERIFIED
QUANTUM READY (optional)
Source
`sha256:…`
Output
`sha256:…`
Trace
`trace_id: …`
Share
`shareId: …`
What’s the promise?
“Download the output. Hash it. Compare. Optionally verify offline.”

## How It Works (receipt‑first)

This is the sequence third‑party reviewers actually care about. Every step either produces a receipt, or it doesn’t ship.

1. 1
   Capture the source bytes
   We hash the exact artifact (PDF/MD/etc) to produce `source_sha256`.
2. 2
   Produce the output bytes
   We hash the final output to produce `output_sha256` (what the reader sees).
3. 3
   Bind source ↔ output in a trace
   We create `trace_id` and publish a trace receipt that links hashes, time, and versioning.
4. 4
   Publish a no‑login proof surface
   Stable URLs keyed by an unguessable `shareId` (trace, dossier, pack, source).
5. 5
   Optional: publish offline bundles
   For constrained environments, export triage bundles (lightweight/standard/full) verifiable without network access.

## Third‑Party Trust Requirements (what outsiders demand)

This is the “procurement/audit” checklist, stated plainly.

### Typical third‑party questions

- “Can I verify the output came from this source?”
- “Can I verify without your login, VPN, or internal tools?”
- “Can I verify later, offline, after a dispute?”
- “What does the receipt prove, and what does it not prove?”
- “If the evidence is missing, is that visible?”

### IF.TTT answers (black/white)

Proves
Integrity binding (hashes), publication receipts, optional signatures, offline verification artifacts.
Does not prove
Intent, interpretation, or “compliance”. It gives evidence; your process decides what that evidence means.
Default stance
If it’s not verifiable, label it as a gap (do not endorse it).

## Open Verification (try it yourself)

Use the same path your auditors and external reviewers will use.

### Live example (trace + bundles)

Example trace page https://infrafabric.io/static/trace/6qRgcR01kw_qNo63Dbs_ob9n Triage bundle selector (lightweight/standard/full) https://infrafabric.io/static/hosted/review/trace-bundles/d70ed99a/index.html Offline verifier (HTML view) https://infrafabric.io/static/hosted/iftrace.html Offline verifier (download) https://infrafabric.io/static/hosted/iftrace.py
Public receipt URLs (no-login)

Every published output gets a stable share surface keyed by a single `shareId`.

    https://infrafabric.io/static/trace/<shareId>
    https://infrafabric.io/static/dossier/<shareId>
    https://infrafabric.io/static/dossier/<shareId>/download
    https://infrafabric.io/static/pack/<shareId>.md
    https://infrafabric.io/static/review/<shareId>.md
    https://infrafabric.io/static/marketing/<shareId>.md
    https://infrafabric.io/static/source/<source_sha256>.pdf

HTML views exist for sandboxes that load `text/html` but reject downloads: `/static/pack/<shareId>`, `/static/review/<shareId>`, `/static/marketing/<shareId>`.

Note: some constrained “web fetchers” reject downloadable binaries (e.g., `.tar.gz`) while still loading HTML. That’s why HTML views exist for packs and indexes.

### CLI verification (2 minutes)

Download a bundle from the selector, then:

    curl -fsSL -o iftrace.py 'https://infrafabric.io/static/hosted/iftrace.py'
    python3 iftrace.py verify trace_bundle_<id>_standard.tar.gz --expected-sha256 <sha256>

VERIFIED means the hashes match what the receipt declares. QUANTUM READY may be shown when a post‑quantum signature receipt exists (PQ verification is additive; hash verification still stands).

## Vertical Fit (what each buyer is actually looking for)

Same mechanism, different third‑party pressure.

### B2B SaaS (SOC 2 / ISO)

Third party

Auditors + enterprise procurement

They want

Evidence that controls existed at the right time, in the right scope, with receipts.

IF.TTT helps by

Publishing no‑login receipts and offline bundles for disputes and audits.

### Fintech / Regulated Finance

Third party

Regulators + model risk + internal audit

They want

Non‑repudiation, dispute workflows, and “show your work” provenance.

IF.TTT helps by

Binding outputs to sources and creating a defensible, replayable receipt trail.

### Healthcare

Third party

Compliance + vendors + incident reviewers

They want

Clear boundaries: what’s verified, what’s inferred, and what must be reviewed by humans.

IF.TTT helps by

Making evidence legible to outsiders while preserving strict, machine‑verifiable receipts.

### Gov / Defense Contractors

Third party

Assessors + customers + supply‑chain review

They want

Offline‑verifiable bundles and unambiguous chain‑of‑custody.

IF.TTT helps by

Providing triage bundles that can be verified without trusted network access.

### AI Product Companies

Third party

Enterprise buyers + incident responders

They want

Provable provenance for outputs (“why did it say that?”) without internal access.

IF.TTT helps by

Making trace receipts shareable, replayable, and dispute‑friendly.

### SecOps / SOC

Third party

Executives + auditors after an incident

They want

To verify AI summaries against raw evidence and keep chain‑of‑custody intact.

IF.TTT helps by

Binding “what the system said” to “what the system saw” via receipts and bundles.

### Industrial / Supply Chain

Third party

Customers + auditors + insurers

They want

Proof of change control and traceability that survives contractor handoffs.

IF.TTT helps by

Standardizing receipts so handoffs remain verifiable across organizational boundaries.

## FAQ

What is “VERIFIED”?

“VERIFIED” means the hashes on the trace page match the output/source that can be downloaded and hashed independently. It is an integrity receipt: the bytes match what the trace declares.

What is “QUANTUM READY”?

“QUANTUM READY” is shown when a post‑quantum signature receipt exists for the trace. It means PQ receipts are present now (for future audit requirements). PQ verification is additive; the hash receipt remains valid either way.

Do you guarantee compliance?

No. IF.TTT produces verifiable artifacts that can support audits and disputes. Compliance is a broader program: scope, policy, human review, and governance decisions are still required.

What’s the difference between shareId and trace_id?

`shareId` is the public handle used in URLs. `trace_id` is the chain‑of‑custody UUID recorded in receipts and bundles.

Docs
IF.TTT paper update (review pack)
Contact
trace@infrafabric.io