No-login integrity receipts
Prove an output matches a confidential source.
Publish a receipt. Anyone can verify the bytes later—without access to your internal systems.
Verified means the hashes match (black/white). It does not imply truth, compliance, or interpretation.
Constitutional for the subjects
Designed for the people affected by outputs, not only the architects.
“Subjects” are the people whose lives, rights, money, or safety can be affected by an output. “Architects” are the people who build systems. InfraFabric is built to be constitutional for the subjects: a non-expert should be able to verify integrity without accounts, vendor access, or special tools.
A receipt does one job: it lets you check whether the bytes you downloaded match the published hash (black/white). It does not prove the content is true, safe, compliant, or wise (interpretation).
Verify (fast)
No login. 60 seconds. Black/white.
-
Open a receipt on /static/trace/<shareId> and copy
output_sha256. - Download the output you are checking (pack or dossier) and hash it locally (sha256sum).
- Compare hashes. If they match, the bytes are verified.
If a single character changes in a bank statement, healthcare dossier, evidence folder, or AI output, the hash changes and verification fails. This is designed for adversarial reality: silent internal edits, external tampering, and handoff drift.
QUANTUM READY means a post-quantum signature receipt exists for the trace; it is not a claim of quantum security.
Use cases by vertical
Pick a vertical to see pressure points and proof needs.
AI trust pressure AI Products
Freeze outputs before they ship.
open
AI Products
Freeze outputs before they ship.
When an output is contested (“that’s not what we saw”), you need to prove which bytes were reviewed and released. if.trace supports integrity receipts for AI outputs without requiring third-party access to your internal systems.
- Customers demand provenance and reproducibility.
- Vendors and models change over time.
- Claims must be checkable outside your system.
- Integrity receipts: A stable proof surface for outputs (bytes, not truth).
- Audit-ready bundles: Offline verification options.
- Clear limits: Integrity verified; meaning debated separately.
- AI outputs: prove the exact bytes you reviewed are the bytes clients received.
- Eval reports: detect silent edits before release with a single hash check.
- Model/vendor changes: keep outputs provable even as internals evolve.
Financial pressure Financial Services
Chain-of-custody for high-stakes outputs.
expand
Financial Services
Chain-of-custody for high-stakes outputs.
Regulated environments need evidence that survives scrutiny. if.trace supports verifiable artifacts without fragile internal access dependencies.
- Model risk and decision audits require durable evidence.
- Regulators and auditors are external third parties.
- Evidence must remain checkable months later.
- Integrity receipts: Downloadable bytes that match published hashes.
- Stable proof surface: Predictable URLs for audit trails.
- Offline options: Bundles for constrained environments.
- Bank statement / risk report: if one digit changes, the hash changes and verification fails.
- Model risk pack: prove the exact report approved is what was distributed.
- Regulator review: share proof links without sharing internal dashboards.
Legal reality Legal
Chain-of-custody for drafts and evidence.
expand
Legal
Chain-of-custody for drafts and evidence.
Legal work depends on what can be proven. if.trace provides a simple, verifiable custody layer for documents and derived outputs.
- Draft histories matter when disputes arise.
- Evidence must be defensible in adversarial review.
- Third parties should verify without logins.
- Custody proof: Bind source and output with trace IDs and hashes.
- Black/white verification: Integrity verification with clear limits.
- Portable review: Offline bundles and HTML views.
- Evidence folder: prove exhibits weren’t modified between handoffs.
- Contract drafts: bind the signed version to a receipt so disputes stay grounded.
- Discovery packets: third parties verify bytes without logins.
Healthcare constraints Healthcare
Proof that respects boundaries.
expand
Healthcare
Proof that respects boundaries.
Healthcare environments require strict boundaries: privacy, consent, and auditability. if.trace supports integrity verification without broad data exposure.
- Privacy boundaries must be respected even during review.
- Audit trails must be clear and durable.
- Third-party verification must not depend on internal access.
- Verification without access: Receipts instead of credentials.
- De-risked sharing: Share proof of integrity, not sensitive sources.
- Operational clarity: Explicitly scoped claims for reviewers.
- Clinical-facing output: prove bytes weren’t modified after review (no patient data required).
- Evidence folder: if one character changes, verification fails — detect silent tampering.
- Third-party audit: provide proof without granting internal system access.
Security operations SecOps / SOC
Bind summaries to evidence.
expand
SecOps / SOC
Bind summaries to evidence.
Security teams summarize fast under pressure. if.trace keeps summaries tied to underlying evidence so post-incident review stays grounded.
- Incidents are reviewed later, often by external parties.
- Evidence chains can break during handoffs.
- Over-sharing internal access increases risk.
- Evidence binding: Link reports to underlying inputs via hashes.
- Shareable receipts: No-login verification for stakeholders.
- Offline verification: Portable bundles for review.
- Incident postmortem: bind narrative outputs to evidence hashes for later review.
- Red-team report: prove the delivered PDF matches what was generated at the time.
- Executive updates: avoid “message drift” across channels and rewrites.
Public sector reality Public Sector
Proof must survive procurement.
expand
Public Sector
Proof must survive procurement.
Public accountability is a third‑party problem: reviewers need proof without accounts or internal access. if.trace turns “trust us” into receipts that a stranger can verify.
- 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.
- Receipt surface: Stable, no‑login URLs for trace + output + source.
- Offline bundles: Triage bundles (light/standard/full) with expected hashes.
- Black/white: States what is verified (integrity) and what is not (interpretation).
- Procurement packet: prove the exact PDF a committee reviewed is what gets shared later.
- Oversight handoff: let third parties verify without creating accounts.
- Offline review: publish bundles for constrained or air‑gapped environments.
What you get (black/white)
Stable proof links
Share a URL that survives handoffs and time.
- https://infrafabric.io/static/trace/<shareId>
- https://infrafabric.io/static/pack/<shareId>
- https://infrafabric.io/static/pack/<shareId>.md
Offline bundles
For reviewers who can’t log in or need offline verification.
- https://infrafabric.io/static/hosted/review/trace-bundles/<id>/index.html
Offline verifier
Verify bundles offline (no InfraFabric install required).
- https://infrafabric.io/static/hosted/iftrace-offline.html
- https://infrafabric.io/static/hosted/iftrace.py
HTML fallbacks
Some reviewers can open HTML but refuse downloads—publish both.
Quantum-ready (optional)
A post-quantum receipt can exist for the trace (QUANTUM READY; not a claim of quantum security).