hosted/ifttt/about/index.html
2025-12-30 05:54:49 +00:00

134 lines
6.2 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>IF.Trace — About</title>
<meta
name="description"
content="IF.Trace is a receipt-first governance protocol: traceable, transparent, trustworthy. This page explains the who/why/what/where/when/how and the traps that break open verification."
/>
<link rel="stylesheet" href="../style.css" />
</head>
<body class="home home--sig">
<header class="sigNav" aria-label="Top navigation">
<div class="wrap sigNav__inner">
<a class="sigBrand" href="../" aria-label="IF.Trace home">IF.Trace</a>
<nav class="sigLinks" aria-label="Site">
<a href="../verticals/">Sector</a>
<span class="sigLinks__sep" aria-hidden="true">|</span>
<a href="../pricing/">Pricing</a>
<span class="sigLinks__sep" aria-hidden="true">|</span>
<a href="../api/">API</a>
</nav>
</div>
</header>
<main id="top">
<section class="hero">
<div class="wrap hero__grid">
<div class="hero__copy">
<p class="kicker">Why this exists</p>
<h1>We built the skeleton first.</h1>
<p class="lede">
Most systems produce answers and call that “governance”. IF.Trace starts earlier: it produces receipts that a third party can verify without
joining your internal world.
</p>
<div class="panel">
<h3>Who / Why / What / Where / When / How</h3>
<div class="bw">
<div class="bw__row">
<div class="bw__k">Who</div>
<div class="bw__v">InfraFabric operators shipping public, nologin verification artifacts.</div>
</div>
<div class="bw__row">
<div class="bw__k">Why</div>
<div class="bw__v">Because “trust us” fails the moment a reviewer asks for proof.</div>
</div>
<div class="bw__row">
<div class="bw__k">What</div>
<div class="bw__v">A receiptfirst protocol: bind <code>source_sha256</code><code>output_sha256</code> under a trace receipt.</div>
</div>
<div class="bw__row">
<div class="bw__k">Where</div>
<div class="bw__v">On a stable public share surface (no login): trace, dossier, packs, and source.</div>
</div>
<div class="bw__row">
<div class="bw__k">When</div>
<div class="bw__v">At publication time: the receipt is generated and can be verified later during disputes.</div>
</div>
<div class="bw__row">
<div class="bw__k">How</div>
<div class="bw__v">Hashes + receipts + optional offline bundles; nothing magical, just opposable proof.</div>
</div>
</div>
</div>
<div class="cta" style="margin-top: 12px">
<a class="btn btn--primary" href="../#verify">Try a live trace</a>
<a class="btn" href="../api/">Developer surface</a>
</div>
</div>
<aside class="hero__card" aria-label="Traps to avoid">
<div class="card">
<div class="card__hdr">
<div class="badge badge--ok">TRAPS</div>
<div class="badge">HOW RECEIPTS BREAK</div>
</div>
<div class="card__body">
<ul class="list" style="margin: 0; padding-left: 18px">
<li><strong>Broken share surface:</strong> moving URLs or forcing login turns receipts into theater.</li>
<li><strong>Mixing identifiers:</strong> <code>shareId</code> is public; <code>trace_id</code> is chainofcustody. Dont swap them.</li>
<li><strong>“Compliance” claims:</strong> receipts support audits; they do not guarantee program scope or behavior.</li>
<li><strong>Unverifiable artifacts:</strong> screenshots and PDFs are not gates unless bound to machinecheckable signals.</li>
<li><strong>WAF surprises:</strong> some clients can fetch HTML but reject binary downloads—publish HTML views.</li>
</ul>
</div>
</div>
</aside>
</div>
</section>
<section class="section section--alt">
<div class="wrap">
<h2>What a receipt proves (and what it doesnt)</h2>
<div class="grid2">
<div class="panel">
<h3>Proves</h3>
<ul class="list">
<li>Integrity binding: the published bytes match the hashes on the receipt.</li>
<li>Traceability: a reviewer can point to a stable, nologin receipt.</li>
<li>Replay: verification still works during disputes (offline bundles when needed).</li>
</ul>
</div>
<div class="panel">
<h3>Does not prove</h3>
<ul class="list">
<li>Intent, interpretation, or “correctness” of a narrative.</li>
<li>That a control is effective—only that the evidence exists and is bound to the record.</li>
<li>Compliance scope (people, policy, contracts); receipts are inputs to governance.</li>
</ul>
</div>
</div>
</div>
</section>
<section class="section">
<div class="wrap">
<h2>Read the paper (and verify the examples)</h2>
<div class="links">
<a class="linkrow" href="https://infrafabric.io/static/hosted/review/ifttt-paper-update/2025-12-28/review-pack.html" target="_blank" rel="noreferrer">
<span class="linkrow__t">IF.Trace: The Skeleton of Everything (review pack)</span>
<span class="linkrow__u">https://infrafabric.io/static/hosted/review/ifttt-paper-update/2025-12-28/review-pack.html</span>
</a>
</div>
</div>
</section>
</main>
<a class="sigContact" href="mailto:ds@infrafabric.io?subject=IF.Trace%20contact">contact</a>
</body>
</html>