hosted/ifttt/verticals/index.html

172 lines
7.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.TTT — Verticals</title>
<meta name="description" content="Vertical fit overview for IF.TTT: third-party trust pressure mapped to receipts, bundles, and verification." />
<link rel="stylesheet" href="../style.css" />
</head>
<body>
<header class="top">
<div class="wrap top__inner">
<a class="brand" href="../" aria-label="IF.TTT home">
<img class="brand__logo" src="../assets/if-logo-simple.svg" alt="" aria-hidden="true" />
<span class="brand__text">
<span class="brand__title">IF.TTT</span>
<span class="brand__sub">Vertical fit</span>
</span>
</a>
<nav class="nav" aria-label="Primary">
<a href="../#how">How</a>
<a href="../#trust">Trust</a>
<a href="../#verify">Verify</a>
<a href="../governance/">Governance</a>
<a href="../whitepaper/">Whitepaper</a>
<a href="../about/">About</a>
<a href="../api/">Developers</a>
<a class="lang" href="../fr/" aria-label="French">FR</a>
</nav>
</div>
</header>
<main id="top">
<section class="hero">
<div class="wrap hero__grid">
<div class="hero__copy">
<p class="kicker">Same mechanism, different pressure</p>
<h1>Verticals are just different auditors.</h1>
<p class="lede">
IF.TTT doesnt “solve compliance.” It solves the universal problem underneath compliance: third parties demanding proof without joining
your internal world.
</p>
<div class="cta">
<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="Receipt-first sequence">
<div class="card">
<div class="card__media">
<img src="../assets/red-team-doc-1024-559.jpg" alt="Red Team dossier cover" loading="lazy" />
</div>
<div class="card__hdr">
<div class="badge badge--ok">RECEIPTFIRST</div>
<div class="badge">NOLOGIN</div>
</div>
<div class="card__body">
<ol class="steps">
<li class="step">
<div class="step__n">1</div>
<div class="step__b">
<div class="step__t">Hash the source</div>
<div class="step__d">Compute <code>source_sha256</code>.</div>
</div>
</li>
<li class="step">
<div class="step__n">2</div>
<div class="step__b">
<div class="step__t">Hash the output</div>
<div class="step__d">Compute <code>output_sha256</code>.</div>
</div>
</li>
<li class="step">
<div class="step__n">3</div>
<div class="step__b">
<div class="step__t">Publish the trace</div>
<div class="step__d">A receipt page binds source ↔ output.</div>
</div>
</li>
</ol>
</div>
</div>
</aside>
</div>
</section>
<section class="section section--alt">
<div class="wrap">
<h2>Choose a vertical</h2>
<p class="sub">Each page explains what third parties demand and what receipts make those demands tractable.</p>
<div class="cards">
<article class="vcard">
<h3>Fintech / Regulated Finance</h3>
<p class="vcard__v">Model risk, nonrepudiation, dispute workflows.</p>
<a class="vcard__more" href="./finance/">Finance →</a>
</article>
<article class="vcard">
<h3>Legal</h3>
<p class="vcard__v">Chainofcustody for drafts, evidence, and decisions.</p>
<a class="vcard__more" href="./legal/">Legal →</a>
</article>
<article class="vcard">
<h3>Sciences / Research</h3>
<p class="vcard__v">Provenance, reproducibility, and external reviewers.</p>
<a class="vcard__more" href="./sciences/">Sciences →</a>
</article>
<article class="vcard">
<h3>Government / Defense</h3>
<p class="vcard__v">Offline verification and unambiguous custody.</p>
<a class="vcard__more" href="./government/">Government →</a>
</article>
<article class="vcard">
<h3>B2B SaaS (SOC 2 / ISO)</h3>
<p class="vcard__v">Auditors, procurement, “prove it existed at the time.”</p>
<a class="vcard__more" href="./saas/">B2B SaaS →</a>
</article>
<article class="vcard">
<h3>SecOps / SOC</h3>
<p class="vcard__v">Bind summaries to evidence; keep custody intact.</p>
<a class="vcard__more" href="./secops/">SecOps →</a>
</article>
<article class="vcard">
<h3>Healthcare</h3>
<p class="vcard__v">Clear boundaries, audit trails, and disputeready receipts.</p>
<a class="vcard__more" href="./healthcare/">Healthcare →</a>
</article>
<article class="vcard">
<h3>AI Product Companies</h3>
<p class="vcard__v">Provable provenance for outputs: “why did it say that?”</p>
<a class="vcard__more" href="./ai/">AI products →</a>
</article>
<article class="vcard">
<h3>Industrial / Supply Chain</h3>
<p class="vcard__v">Traceability that survives vendor and contractor handoffs.</p>
<a class="vcard__more" href="./supply-chain/">Supply chain →</a>
</article>
</div>
</div>
</section>
</main>
<footer class="footer">
<div class="wrap footer__inner">
<div class="muted">InfraFabric • IF.TTT receipts are designed to be legible to the governed.</div>
<div class="muted">
<a href="../">IF.TTT</a> · <a href="../governance/">Governance</a> · <a href="../api/">Developers</a> ·
<a href="mailto:ds@infrafabric.io">ds@infrafabric.io</a> <span class="bottombar__sep">·</span> Danny Stocker
</div>
</div>
</footer>
<div class="bottombar" aria-label="Quick links">
<div class="wrap bottombar__inner">
<div class="bottombar__left">
<a href="./finance/">Finance</a>
<a href="./legal/">Legal</a>
<a href="./sciences/">Sciences</a>
<a href="./government/">Government</a>
</div>
<div class="bottombar__right">
<a href="../api/">Developers</a>
<span class="bottombar__sep">|</span>
<a href="../api/">API</a>
</div>
</div>
</div>
</body>
</html>