Spaces:

SZLHOLDINGS
/

a11oy

Running

App Files Files Community

betterwithage commited on Jun 14

Commit

e2d1708

verified ·

1 Parent(s): fe61b0a

chore(sync): mirror static/3d kit + Dockerfile-COPY'd web/*.html to Space (hf-sync)

Browse files

Automated 3D/web-page asset sync from szl-holdings/a11oy main via hf-sync.
web/*.html set parsed live from the Dockerfile COPY directives.
Added/updated: 48 file(s)
Deleted (gone from GitHub main): (none)

Keeps static/3d/** and every Dockerfile-COPY'd web/<page>.html identical
to GitHub main so an HF factory rebuild never drops a GitHub edit (closes
the chronic hf-module-drift red for the 3D kit + baked web pages).

Files changed (2) hide show

web/defense-readiness.html +255 -0
web/signature-is-not-proof.html +350 -0

web/defense-readiness.html ADDED Viewed

	@@ -0,0 +1,255 @@

+<!DOCTYPE html>
+<!--
+  a11oy · DEFENSE READINESS — public showcase summary (showcase lane).
+  © 2026 Lutar, Stephen P. — SZL Holdings. SPDX-License-Identifier: Apache-2.0
+  0 runtime CDN: system fonts only, no external scripts. This is a PUBLIC fit +
+  honest-maturity summary. It deliberately exposes NO private application content
+  (DARPA / JIATF / NATO / AFWERX submissions are private). It shows the FIT, the
+  honest maturity (MODELED bounds + live signed software APIs, NOT flown hardware),
+  and links each pathway to the relevant LIVE a11oy surface. Live surfaces are
+  probed via fetch with an HONEST NO-LIVE-DATA fallback (doctrine v11).
+-->
+<html lang="en">
+<head>
+<meta charset="utf-8"/>
+<meta name="viewport" content="width=device-width, initial-scale=1"/>
+<title>a11oy · Defense Readiness</title>
+<style>
+  :root{
+    --bg:#0a0e14; --panel:#121823; --panel2:#0f141d; --line:#1f2a3a;
+    --ink:#e6edf3; --mut:#8b98a9; --acc:#5ad1c9; --acc2:#7aa2f7;
+    --ok:#3fb950; --warn:#d29922; --err:#f85149; --road:#a371f7;
+  }
+  *{box-sizing:border-box}
+  body{margin:0;background:var(--bg);color:var(--ink);
+       font:14px/1.6 ui-monospace,SFMono-Regular,Menlo,Consolas,monospace}
+  header{padding:18px 22px;border-bottom:1px solid var(--line);
+         background:linear-gradient(180deg,#0d1320,#0a0e14)}
+  h1{margin:0;font-size:19px;letter-spacing:.3px}
+  .sub{color:var(--mut);font-size:12px;margin-top:4px;max-width:980px}
+  .nav{margin-top:10px;display:flex;gap:14px;flex-wrap:wrap;font-size:12px}
+  .nav a{color:var(--acc2);text-decoration:none}
+  .nav a:hover{text-decoration:underline}
+  .wrap{max-width:1080px;margin:0 auto;padding:22px}
+  section{margin:0 0 26px}
+  .eyebrow{color:var(--acc);font-size:11px;letter-spacing:.16em;text-transform:uppercase;margin-bottom:6px}
+  h2{font-size:16px;letter-spacing:.3px;margin:0 0 10px}
+  h3{font-size:14px;letter-spacing:.2px;margin:0 0 6px;color:var(--acc)}
+  p{margin:0 0 12px}
+  .lede{font-size:15px;color:#cdd8e6}
+  .card{background:var(--panel);border:1px solid var(--line);border-radius:10px;padding:16px 18px;margin:0 0 14px}
+  .quote{border-left:3px solid var(--acc);background:var(--panel2);padding:12px 16px;border-radius:0 8px 8px 0;color:#cdd8e6;margin:0 0 14px}
+  .pill{display:inline-block;padding:2px 9px;border-radius:999px;font-size:11px;border:1px solid var(--line);white-space:nowrap}
+  .pill.ok,.pill.live{color:var(--ok);border-color:#163a1f;background:#0e2113}
+  .pill.err{color:var(--err);border-color:#4a1c1c;background:#240f0f}
+  .pill.warn{color:var(--warn);border-color:#3a3015;background:#1f1a0a}
+  .pill.road{color:var(--road);border-color:#2e2147;background:#160f24}
+  .pill.acc{color:var(--acc);border-color:#13403c;background:#0a201e}
+  .pill.modeled{color:var(--warn);border-color:#3a3015;background:#1f1a0a}
+  .grid{display:grid;gap:14px;grid-template-columns:repeat(auto-fit,minmax(330px,1fr))}
+  .path{background:var(--panel);border:1px solid var(--line);border-radius:10px;padding:16px 18px;display:flex;flex-direction:column}
+  .path .head{display:flex;align-items:flex-start;justify-content:space-between;gap:10px;margin-bottom:6px}
+  .path h3{margin:2px 0 2px}
+  .path .org{color:var(--mut);font-size:11px;letter-spacing:.05em}
+  .path .body{color:#c4d0de;flex:1;margin-top:8px}
+  .path .fit{margin-top:10px;font-size:12.5px}
+  .path .fit b{color:var(--ink)}
+  .path .surface{margin-top:10px;padding-top:10px;border-top:1px dotted #1a2435;font-size:12px}
+  .live-line{display:flex;align-items:center;gap:8px;margin-top:6px;font-size:12px}
+  .live-line .v{color:var(--ink);word-break:break-word}
+  .live-line .v a{color:var(--acc2)}
+  table{width:100%;border-collapse:collapse;font-size:12.5px;margin:6px 0}
+  th,td{text-align:left;padding:8px 10px;border-bottom:1px solid #1a2435;vertical-align:top}
+  th{color:var(--mut);font-weight:600}
+  a{color:var(--acc2)}
+  code{color:var(--acc2);font-size:12px}
+  .cite{color:var(--mut);font-size:11.5px;margin-top:8px;line-height:1.6}
+  .cite a{color:var(--acc2)}
+  footer{color:var(--mut);font-size:11px;padding:18px 22px;border-top:1px solid var(--line);line-height:1.7}
+  @media(max-width:640px){.wrap{padding:16px}}
+</style>
+</head>
+<body>
+<header>
+  <h1>a11oy · Defense Readiness</h1>
+  <div class="sub">SZL Holdings is aligned to multiple federal and allied innovation pathways. This page
+  shows the <b>fit</b> and the <b>honest maturity</b> — MODELED physics bounds + live signed software APIs,
+  <b>not flown hardware</b> — and links each pathway to the live a11oy surface that backs it. It exposes
+  no private submission content. Every maturity claim labelled <span class="pill modeled">MODELED</span>
+  <span class="pill live">LIVE</span> <span class="pill road">ROADMAP</span>.</div>
+  <nav class="nav">
+    <a href="/console/">← Console</a>
+    <a href="/signature-is-not-proof">Signature ≠ Proof case study</a>
+    <a href="/compliance">Compliance crosswalk</a>
+    <a href="/governance">Governance</a>
+  </nav>
+</header>
+<div class="wrap">
+  <section>
+    <div class="eyebrow">Posture</div>
+    <p class="lede">SZL builds on an explicit doctrine of <b>honest maturity</b>: we publish what is
+    MEASURED, label what is MODELED, and claim only what has a checkable artifact. The differentiator is
+    not a flown prototype — it is <b>verifiable provenance + assurance, sovereign on-metal compute</b>,
+    and a refusal to overclaim. Below: where a11oy and its surfaces fit federal pathways, and exactly how
+    mature each claim is.</p>
+    <div class="quote"><b>What we are.</b> A governed-AI command platform (deny-by-default 8-gate policy
+    engine, DSSE-signed verdicts/receipts, supply-chain assurance mesh, hash-chained governance ledger,
+    hybrid post-quantum signing) plus MODELED hard-physics PNT bounds and a sense-and-evidence counter-UAS
+    surface. <b>What we are not.</b> We do not claim flown hardware, a fielded prototype, or “proven trust.”
+    Λ is Conjecture 1 — advisory, &lt; 1.0, never a theorem.</div>
+  </section>
+  <section>
+    <div class="eyebrow">Federal &amp; allied pathways · fit + honest maturity</div>
+    <h2>Where we align</h2>
+    <div class="grid">
+      <!-- DARPA PINPOINT -->
+      <div class="path">
+        <div class="head">
+          <div><h3>DARPA PINPOINT</h3><div class="org">DSO · DARPA-SN-26-88 · PNT</div></div>
+          <span class="pill modeled">MODELED</span>
+        </div>
+        <div class="body">Precision Inertial Navigation &amp; Positioning — highly accurate nav/positioning
+        where GPS is unavailable or unreliable. Our PNT engine is a clean-room, closed-form quantum-sensing
+        and GNSS-resilience stack.</div>
+        <div class="fit"><b>Fit:</b> closed-form cold-atom interferometer sensitivity certificate
+        (at/above the Standard Quantum Limit), RAIM/AGC/SQM deny-by-default spoof fusion, GPS-denied
+        coasting figure-of-merit, and fundamental compute/energy bounds — all served as live signed
+        software APIs.</div>
+        <div class="surface">
+          <b>Honest maturity:</b> MODELED closed-form physics (stdlib, deterministic), <b>not flown
+          hardware</b>. The sensor certificate is labelled MODELED · STRUCTURAL-ONLY.
+          <div class="live-line" id="pnt-live"><span class="pill warn">checking…</span><span class="v">PNT mesh</span></div>
+        </div>
+        <div class="cite">Special Notice (advance notice of a future program); responses due Jul 13, 2026.
+        <a href="https://www.highergov.com/contract-opportunity/future-program-announcement-precision-inertial-na-darpa-sn-26-88-s-4a1f7/">DARPA-SN-26-88</a></div>
+      </div>
+      <!-- JIATF 401 -->
+      <div class="path">
+        <div class="head">
+          <div><h3>JIATF 401</h3><div class="org">NDAA FY26 §912 · counter-sUAS T&amp;E</div></div>
+          <span class="pill live">LIVE</span>
+        </div>
+        <div class="body">Joint Interagency Task Force 401 approves counter-sUAS systems for Department use
+        and published standardized C-UAS test &amp; evaluation criteria (Apr 28, 2026). Our counter-UAS
+        surface <b>senses and evidences</b> — it does not jam, spoof, take over, or kinetically defeat.</div>
+        <div class="fit"><b>Fit:</b> forensic-evidence and rules-of-engagement alignment — a live Λ decision
+        plus an ECDSA-P256 DSSE-signed forensic verdict, verified drone fingerprints, and a Remote-ID
+        validator. The value is <b>admissible, replayable evidence</b>, not effects.</div>
+        <div class="surface">
+          <b>Honest maturity:</b> live sense-and-evidence surface with signed verdicts; each T&amp;E
+          criterion is crosswalked honestly as Demonstrated / Modeled / Not-yet / Out-of-scope — never
+          assumed.
+          <div class="live-line" id="elite-live"><span class="pill warn">checking…</span><span class="v">Counter-UAS surface</span></div>
+        </div>
+        <div class="cite">Criteria published Apr 28, 2026.
+        <a href="https://www.war.gov/News/Releases/External/Article/4473626/jiatf-401-publishes-testing-and-evaluation-criteria-to-inform-future-demonstrat/">war.gov</a></div>
+      </div>
+      <!-- NATO DIANA -->
+      <div class="path">
+        <div class="head">
+          <div><h3>NATO DIANA</h3><div class="org">Defence Innovation Accelerator · dual-use</div></div>
+          <span class="pill acc">FIT</span>
+        </div>
+        <div class="body">DIANA accelerates dual-use deep tech across the alliance. a11oy’s governed-AI
+        assurance and sovereign-compute provenance are dual-use by construction — civilian supply-chain
+        integrity and defense AI governance share the same substrate.</div>
+        <div class="fit"><b>Fit:</b> verifiable provenance + assurance mesh (3-axis attestation, C2PA
+        content credentials, hash-chained ledger), aligned to EU AI Act Article 50 (effective Aug 2, 2026)
+        and NIST AI RMF / ISO 42001 via a live compliance crosswalk.</div>
+        <div class="surface">
+          <b>Honest maturity:</b> live signed software APIs + compliance crosswalk; trans-Atlantic
+          deployment is a roadmap engagement, labelled as such.
+          <div class="live-line" id="comp-live"><span class="pill warn">checking…</span><span class="v">Compliance crosswalk</span></div>
+        </div>
+      </div>
+      <!-- AFWERX SBIR -->
+      <div class="path">
+        <div class="head">
+          <div><h3>AFWERX SBIR</h3><div class="org">Dept. of the Air Force · small-business R&amp;D</div></div>
+          <span class="pill acc">FIT</span>
+        </div>
+        <div class="body">AFWERX SBIR funds small-business innovation with a defense transition path. As a
+        US-based small business (NAICS 541715, &lt;500 employees) with live, signed, sovereign-compute
+        software, SZL fits the R&amp;D-to-transition model.</div>
+        <div class="fit"><b>Fit:</b> governed counter-UAS sense-and-evidence + AI-governance assurance — a
+        software-first capability with a clear dual-use transition and a verifiable-provenance moat.</div>
+        <div class="surface">
+          <b>Honest maturity:</b> live software APIs + MODELED physics bounds; hardware integration and a
+          fielded prototype are roadmap, labelled honestly. SAM/UEI/CAGE founder-supplied.
+          <div class="live-line" id="elite2-live"><span class="pill warn">checking…</span><span class="v">Elite console</span></div>
+        </div>
+      </div>
+    </div>
+  </section>
+  <section>
+    <div class="eyebrow">The honesty is the feature</div>
+    <h2>Doctrine v11 as a defense-acquisition advantage</h2>
+    <p>In a market where “signed: yes” has already certified a supply-chain worm
+    (<a href="/signature-is-not-proof">see the Mini Shai-Hulud case study</a>), an evaluator’s hardest
+    problem is telling a real capability from a confident slide. Our doctrine is built to make that easy:</p>
+    <div class="card">
+      <table>
+        <tr><th>Principle</th><th>What it means for an evaluator</th></tr>
+        <tr><td><b>Prove-or-downgrade</b></td><td>Every DONE claim has a checkable artifact: a pushed commit SHA, an HTTP 200 from a named endpoint, or a verifying signature. No artifact → it is labelled RECOMMENDED or ROADMAP, not claimed.</td></tr>
+        <tr><td><b>Label every value</b></td><td>MEASURED / MODELED / SAMPLE / STRUCTURAL-ONLY. A modeled physics bound is never dressed up as flown telemetry.</td></tr>
+        <tr><td><b>Never overclaim</b></td><td>No fabricated numbers, TRL, signatures, partnerships, or flown-hardware claims. Λ is Conjecture 1 (advisory), never “proven trust.”</td></tr>
+        <tr><td><b>Behaviour over attestation</b></td><td>We trust the behaviour we can observe and the receipts we can replay — not the attestation we were handed.</td></tr>
+      </table>
+    </div>
+    <p>The result is a capability statement an evaluator can verify in a browser, line by line, against
+    live endpoints — the opposite of a black box.</p>
+  </section>
+  <section>
+    <div class="card">
+      <h3>Engagement</h3>
+      <p>Founder is handling SAM.gov registration (via an APEX Accelerator) and federal submission
+      mechanics; the engineering artifacts behind each pathway are live and verifiable now at
+      <a href="https://a11oy.net">a11oy.net</a>. Private submission content is not published here by design.</p>
+    </div>
+  </section>
+</div>
+<footer>
+  a11oy showcase · doctrine v11 · honest maturity: MODELED bounds + live signed software APIs, NOT flown
+  hardware · prove-or-downgrade · Λ = Conjecture 1 (advisory, &lt; 1.0) · 0 runtime CDN.<br>
+  Live surfaces probed from <span style="color:var(--acc2)">/api/a11oy/v1/{pnt, compliance}</span> · <span style="color:var(--acc2)">/elite</span> · <span style="color:var(--acc2)">/elite-console</span> — honest NO-LIVE-DATA fallback, never fabricated.
+  SZL Holdings · sovereign-compute, AI-governance &amp; defense-tech, NYC · UEI [PLACEHOLDER: UEI] · CAGE [PLACEHOLDER: CAGE] · NAICS 541715.
+</footer>
+<script>
+// 0-CDN inline. Probe live a11oy surfaces; render an HONEST NO-LIVE-DATA chip on
+// any failure — never a fabricated value.
+(function(){
+  function setLive(id, ok, label, href){
+    var el = document.getElementById(id);
+    if(!el) return;
+    var pill = ok ? '<span class="pill live">LIVE ✓</span>'
+                  : '<span class="pill warn">NO-LIVE-DATA</span>';
+    var v = href ? '<span class="v"><a href="'+href+'">'+label+'</a></span>'
+                 : '<span class="v">'+label+'</span>';
+    el.innerHTML = pill + v;
+  }
+  function probe(url, id, label, href){
+    fetch(url, {headers:{'accept':'application/json'}})
+      .then(function(r){ setLive(id, r.ok, label, href); })
+      .catch(function(){ setLive(id, false, label, href); });
+  }
+  probe('/api/a11oy/v1/pnt/limits', 'pnt-live', 'PNT mesh · /api/a11oy/v1/pnt/limits', '/api/a11oy/v1/pnt/limits');
+  probe('/elite',                   'elite-live', 'Counter-UAS · /elite', '/elite');
+  probe('/api/a11oy/v1/compliance', 'comp-live', 'Compliance crosswalk', '/compliance');
+  probe('/elite-console',           'elite2-live', 'Elite console · /elite-console', '/elite-console');
+})();
+</script>
+</body>
+</html>

web/signature-is-not-proof.html ADDED Viewed

	@@ -0,0 +1,350 @@

+<!DOCTYPE html>
+<!--
+  a11oy · A SIGNATURE IS NOT PROOF OF SAFETY — public case study (showcase lane).
+  © 2026 Lutar, Stephen P. — SZL Holdings. SPDX-License-Identifier: Apache-2.0
+  0 runtime CDN: system fonts only, no external scripts. Where a claim can be
+  proven LIVE it is wired to a real a11oy production endpoint
+  (/api/a11oy/v1/{compliance,pinn/certificate,...}) via fetch with an HONEST
+  NO-LIVE-DATA fallback — never a fabricated value. Maturity is labelled
+  LIVE-today vs ROADMAP throughout (doctrine v11). Content mirrors the
+  SZL thought-leadership case study of the same name.
+-->
+<html lang="en">
+<head>
+<meta charset="utf-8"/>
+<meta name="viewport" content="width=device-width, initial-scale=1"/>
+<title>a11oy · A Signature Is Not Proof of Safety</title>
+<style>
+  :root{
+    --bg:#0a0e14; --panel:#121823; --panel2:#0f141d; --line:#1f2a3a;
+    --ink:#e6edf3; --mut:#8b98a9; --acc:#5ad1c9; --acc2:#7aa2f7;
+    --ok:#3fb950; --warn:#d29922; --err:#f85149; --road:#a371f7;
+  }
+  *{box-sizing:border-box}
+  body{margin:0;background:var(--bg);color:var(--ink);
+       font:14px/1.6 ui-monospace,SFMono-Regular,Menlo,Consolas,monospace}
+  header{padding:18px 22px;border-bottom:1px solid var(--line);
+         background:linear-gradient(180deg,#0d1320,#0a0e14)}
+  h1{margin:0;font-size:19px;letter-spacing:.3px}
+  .sub{color:var(--mut);font-size:12px;margin-top:4px;max-width:980px}
+  .nav{margin-top:10px;display:flex;gap:14px;flex-wrap:wrap;font-size:12px}
+  .nav a{color:var(--acc2);text-decoration:none}
+  .nav a:hover{text-decoration:underline}
+  .wrap{max-width:1080px;margin:0 auto;padding:22px}
+  section{margin:0 0 26px}
+  .eyebrow{color:var(--acc);font-size:11px;letter-spacing:.16em;text-transform:uppercase;margin-bottom:6px}
+  h2{font-size:16px;letter-spacing:.3px;margin:0 0 10px;color:var(--ink)}
+  h3{font-size:14px;letter-spacing:.2px;margin:0 0 6px;color:var(--acc)}
+  p{margin:0 0 12px}
+  .hook{font-size:26px;line-height:1.35;font-weight:700;letter-spacing:.3px;margin:6px 0 14px}
+  .hook .em{color:var(--acc)}
+  .lede{font-size:15px;color:#cdd8e6}
+  .card{background:var(--panel);border:1px solid var(--line);border-radius:10px;padding:16px 18px;margin:0 0 14px}
+  .quote{border-left:3px solid var(--acc);background:var(--panel2);padding:12px 16px;
+         border-radius:0 8px 8px 0;color:#cdd8e6;margin:0 0 14px;font-style:normal}
+  .quote.big{font-size:16px;color:var(--ink)}
+  .pill{display:inline-block;padding:2px 9px;border-radius:999px;font-size:11px;
+        border:1px solid var(--line);white-space:nowrap}
+  .pill.ok{color:var(--ok);border-color:#163a1f;background:#0e2113}
+  .pill.err{color:var(--err);border-color:#4a1c1c;background:#240f0f}
+  .pill.warn{color:var(--warn);border-color:#3a3015;background:#1f1a0a}
+  .pill.road{color:var(--road);border-color:#2e2147;background:#160f24}
+  .pill.acc{color:var(--acc);border-color:#13403c;background:#0a201e}
+  .pill.live{color:var(--ok);border-color:#163a1f;background:#0e2113}
+  table{width:100%;border-collapse:collapse;font-size:12.5px;margin:6px 0}
+  th,td{text-align:left;padding:8px 10px;border-bottom:1px solid #1a2435;vertical-align:top}
+  th{color:var(--mut);font-weight:600;letter-spacing:.04em}
+  td.no{color:var(--err)} td.yes{color:var(--ok)}
+  .grid{display:grid;gap:14px;grid-template-columns:repeat(auto-fit,minmax(300px,1fr))}
+  .mech{background:var(--panel);border:1px solid var(--line);border-radius:10px;padding:15px 17px;display:flex;flex-direction:column}
+  .mech .head{display:flex;align-items:center;justify-content:space-between;gap:10px;margin-bottom:8px}
+  .mech .num{color:var(--mut);font-size:11px}
+  .mech h3{margin:2px 0 8px}
+  .mech .body{color:#c4d0de;flex:1}
+  .mech .status{margin-top:10px;padding-top:10px;border-top:1px dotted #1a2435;font-size:12px;color:var(--mut)}
+  .mech .status b{color:var(--ink);font-weight:600}
+  .live-line{display:flex;align-items:center;gap:8px;margin-top:8px;font-size:12px}
+  .live-line .v{color:var(--ink);word-break:break-word}
+  .cite{color:var(--mut);font-size:11.5px;margin-top:10px;line-height:1.6}
+  .cite a{color:var(--acc2)}
+  a{color:var(--acc2)}
+  code{color:var(--acc2);font-size:12px}
+  .loading{color:var(--mut)}
+  .nolive{color:var(--warn)}
+  footer{color:var(--mut);font-size:11px;padding:18px 22px;border-top:1px solid var(--line);line-height:1.7}
+  .reflist{font-size:11.5px;color:var(--mut);line-height:1.7}
+  .reflist li{margin-bottom:5px}
+  .reflist a{color:var(--acc2);word-break:break-all}
+  @media(max-width:640px){.hook{font-size:21px}.wrap{padding:16px}}
+</style>
+</head>
+<body>
+<header>
+  <h1>a11oy · A Signature Is Not Proof of Safety</h1>
+  <div class="sub">SZL Holdings thought leadership · What the May 2026 “Mini Shai-Hulud” npm worm taught us — and why a11oy is built for a world where the cryptography is genuine but the code is not. Every maturity claim labelled <span class="pill live">LIVE</span> / <span class="pill road">ROADMAP</span>; live claims wired to real a11oy endpoints (honest <span class="nolive">NO-LIVE-DATA</span> fallback).</div>
+  <nav class="nav">
+    <a href="/console/">← Console</a>
+    <a href="/governance">Governance</a>
+    <a href="/compliance">Compliance crosswalk</a>
+    <a href="/defense-readiness">Defense readiness →</a>
+  </nav>
+</header>
+<div class="wrap">
+  <!-- HOOK -->
+  <section>
+    <div class="eyebrow">SZL Holdings · Thought Leadership · June 2026</div>
+    <div class="hook">A signature is not proof of safety.<br><span class="em">The cryptography was genuine. The package was malicious anyway.</span></div>
+    <p class="lede">On May 11, 2026, a piece of malware did something the software industry had quietly
+    assumed was impossible: it shipped with a valid, cryptographically signed SLSA Build Level 3
+    provenance attestation. The signature checked out. The provenance was genuine. The package was
+    malicious anyway.</p>
+    <p class="cite">Stephen P. Lutar Jr., Founder &amp; CEO, SZL Holdings · <a href="https://a11oy.net">a11oy.net</a></p>
+  </section>
+  <!-- 1. WHAT HAPPENED -->
+  <section>
+    <div class="eyebrow">1 · What happened</div>
+    <h2>Mini Shai-Hulud — a signed supply-chain worm</h2>
+    <div class="card">
+      <p>Between May 10 and 12, 2026 — with the main publishing burst compressed into roughly five
+      hours on May 11 — the threat group TeamPCP compromised <b>more than 170 packages</b> across the
+      npm and PyPI ecosystems, publishing over 400 malicious versions spanning 19 namespaces.
+      Affected projects had accumulated more than <b>half a billion cumulative downloads</b>. It is the
+      first documented npm worm to propagate while carrying <b>legitimately attested</b> malicious
+      packages.</p>
+      <p>The entry point was an orphaned CI/CD trust configuration in TanStack’s GitHub Actions
+      workflows — a <code>pull_request_target</code> workflow that retained OIDC federation despite no
+      longer being actively maintained. The attacker read short-lived OIDC tokens directly out of the
+      GitHub Actions runner’s process memory (<code>/proc/&lt;pid&gt;/mem</code>), then exchanged those
+      tokens with the Sigstore Fulcio certificate authority to mint legitimate signing certificates.
+      From there: stolen OIDC token → short-lived npm publish token → malicious versions released under
+      the real maintainer identity, with valid provenance describing the exact GitHub Actions job that
+      produced them.</p>
+      <div class="quote">Nothing in the cryptographic chain failed. Sigstore did exactly what it is
+      designed to do: it verified the identity of the token presenter. What it cannot do — what no
+      signature can do — is verify that the build environment had not been compromised, or that the
+      code executing inside that legitimate, identity-verified job was safe.</div>
+      <p>The provenance was accurate. It correctly described a build that produced malware. Phase 2 of
+      the campaign reportedly reached infrastructure at OpenAI, Grafana, and GitHub itself.</p>
+    </div>
+    <div class="quote big">The attack did not break the signature. It exploited the gap between
+    identity verification and behavioural integrity. The signature told you <i>who</i> built it. It
+    told you nothing about <i>what it does</i>.</div>
+  </section>
+  <!-- 2. WHY IT MATTERS -->
+  <section>
+    <div class="eyebrow">2 · Why it matters</div>
+    <h2>The signature-trust fallacy</h2>
+    <p>A cryptographic signature answers two questions with mathematical confidence: <b>who</b> signed
+    this, and <b>what exact bytes</b> were signed. It answers a third question — <i>is the signed thing
+    safe?</i> — not at all. The industry has spent a decade conflating the first two with the third.</p>
+    <div class="card">
+      <table>
+        <tr><th>What a signature proves</th><th>What it does NOT prove</th><th>Mini Shai-Hulud reality</th></tr>
+        <tr>
+          <td>Identity of the signer (the OIDC subject)</td>
+          <td class="no">That the signer’s environment was uncompromised</td>
+          <td>OIDC tokens stolen from runner memory; identity genuine</td>
+        </tr>
+        <tr>
+          <td>The exact bytes that were signed</td>
+          <td class="no">That those bytes are safe to execute</td>
+          <td>Provenance accurately described a malicious build</td>
+        </tr>
+        <tr>
+          <td>That a recognized pipeline produced the artifact</td>
+          <td class="no">That the pipeline behaved as intended</td>
+          <td>Legitimate GitHub Actions job produced malware</td>
+        </tr>
+      </table>
+    </div>
+    <p>SLSA and Sigstore are good. They are <b>necessary but not sufficient</b>. When a control becomes
+    a checkbox — “signed: yes” — it stops being a security boundary and becomes a false sense of one.</p>
+  </section>
+  <!-- 3. THE LESSON -->
+  <section>
+    <div class="eyebrow">3 · The lesson</div>
+    <h2>Doctrine v11 — Signature ≠ Safety</h2>
+    <div class="quote big">“A signature is not proof of safety.” Trust the behaviour you can observe
+    and the receipts you can replay — not the attestation you were handed.</div>
+    <p>The corollary is a posture we call <b>behaviour-over-attestation</b>. An attestation is a claim
+    made at build time about the past. Behaviour is evidence gathered at runtime about the present. When
+    the two disagree, behaviour wins. The rest of our doctrine follows from this: <b>prove-or-downgrade</b>
+    (claim only what has a checkable artifact), label every value <span class="pill acc">MEASURED</span>
+    <span class="pill warn">MODELED</span> <span class="pill">SAMPLE</span>, and never present an
+    attestation as a guarantee. We do not claim a11oy is unbreakable. We claim it <b>stops trusting the
+    signature alone</b>.</p>
+  </section>
+  <!-- 4. HOW a11oy IS ARCHITECTED -->
+  <section>
+    <div class="eyebrow">4 · How a11oy is architected for exactly this</div>
+    <h2>Five mechanisms — each labelled LIVE-today vs ROADMAP</h2>
+    <p>Below are the five mechanisms that make a11oy a structural answer to a Mini Shai-Hulud-class
+    attack. We are explicit throughout about what is live today versus what is roadmap. The credibility
+    comes from the honesty. Where a mechanism can be proven right now, the card binds to a real a11oy
+    production endpoint below.</p>
+    <div class="grid">
+      <!-- 4.1 -->
+      <div class="mech">
+        <div class="head"><span class="num">4.1</span><span class="pill live">LIVE — GAP1</span></div>
+        <h3>Artifact-behaviour monitor</h3>
+        <div class="body">Observe what an artifact actually <i>does</i> at runtime and compare it against an
+        expected behavioural envelope. A signature would have passed Mini Shai-Hulud straight through; a
+        behaviour monitor asks the question the signature cannot — does this thing act the way a safe
+        version of it should? Deny-by-default applied to behaviour, not identity.</div>
+        <div class="status"><b>Today:</b> live as the GAP1 capability, backed by a certified live PINN
+        (physics-informed) certificate from production APIs. <b>Roadmap:</b> broader behavioural-envelope
+        catalogue per artifact class / ecosystem (npm, PyPI, container, model).</div>
+        <div class="live-line" id="pinn-live"><span class="pill warn">checking…</span><span class="v">PINN certificate</span></div>
+      </div>
+      <!-- 4.2 -->
+      <div class="mech">
+        <div class="head"><span class="num">4.2</span><span class="pill live">LIVE</span></div>
+        <h3>3-axis attestation</h3>
+        <div class="body">Single-axis attestation is the exact weakness Mini Shai-Hulud exploited: a valid
+        build attestation, and nothing binding it to runtime behaviour. a11oy’s assurance mesh binds three
+        axes — <b>build provenance · model lineage · runtime behaviour</b> — so compromise of any one axis
+        does not silently pass the others. A genuine build signature riding on a malicious runtime fails
+        the cross-axis check.</div>
+        <div class="status"><b>Today:</b> 3-axis model + DSSE-signed verdicts/receipts in the live mesh.
+        <b>Roadmap:</b> deeper third-party STIX/TAXII threat-intel correlation into the model + runtime axes.</div>
+        <div class="live-line" id="comp-live"><span class="pill warn">checking…</span><span class="v">Compliance crosswalk</span></div>
+      </div>
+      <!-- 4.3 -->
+      <div class="mech">
+        <div class="head"><span class="num">4.3</span><span class="pill live">LIVE</span></div>
+        <h3>Hash-chained Forge ledger + kill switch</h3>
+        <div class="body">Every verdict is written to a hash-chained, offline-verifiable governance ledger
+        (the Forge ledger), so any action is replayable after the fact and any decision is revocable through
+        the kill switch. In a Mini Shai-Hulud scenario this is the difference between “we think we contained
+        it” and “we can prove, line by line, what was admitted, when, and on what evidence — and revoke it now.”</div>
+        <div class="status"><b>Today:</b> hash-chained ledger + kill switch live, with signed receipts
+        (including MEASURED energy receipts via a real NVML exporter, kept distinct from any modeled figure).
+        <b>Roadmap:</b> publishing ledger inclusion proofs to an external transparency service (§5).</div>
+      </div>
+      <!-- 4.4 -->
+      <div class="mech">
+        <div class="head"><span class="num">4.4</span><span class="pill live">LIVE</span></div>
+        <h3>Hybrid Ed25519 + ML-DSA &amp; C2PA</h3>
+        <div class="body">We do not deprecate signing — we harden it and stop over-trusting it. a11oy signs
+        with a hybrid <b>Ed25519 + ML-DSA</b> scheme so verdicts remain verifiable in a post-quantum world,
+        and attaches <b>C2PA content credentials</b> so the provenance of generated content is transparent.
+        This anticipates EU AI Act Article 50 transparency obligations.</div>
+        <div class="status"><b>Today:</b> hybrid signing + C2PA implemented, alongside a NIST AI RMF / ISO
+        42001 / EU AI Act compliance crosswalk. <b>Roadmap:</b> third-party attestation of the crosswalk
+        mapping ahead of enforcement.</div>
+      </div>
+      <!-- 4.5 -->
+      <div class="mech">
+        <div class="head"><span class="num">4.5</span><span class="pill road">ROADMAP</span></div>
+        <h3>SCITT-style independent transparency</h3>
+        <div class="body">The deepest lesson of Mini Shai-Hulud is that <b>self-attestation is not enough</b>:
+        the build attested honestly to its own malicious output. Independent, append-only transparency
+        ledgers — as standardized by IETF SCITT — let third parties verify receipts without trusting the
+        producer.</div>
+        <div class="status"><b>Today:</b> internal hash-chained ledger (4.3) is live and offline-verifiable.
+        <b>Roadmap:</b> external SCITT-style transparency service with third-party inclusion proofs — we label
+        this honestly as not-yet-live.</div>
+      </div>
+    </div>
+  </section>
+  <!-- 5. THE BROADER SHIFT -->
+  <section>
+    <div class="eyebrow">5 · The broader shift</div>
+    <h2>From self-attestation to independent, behavioural assurance</h2>
+    <div class="grid">
+      <div class="card">
+        <h3>EU AI Act · Article 50</h3>
+        <p>Transparency obligations for AI-generated content take effect <b>August 2, 2026</b>. a11oy’s
+        C2PA content credentials and hybrid signing (4.4) are built toward exactly this — provenance of
+        generated content, transparent and verifiable.</p>
+      </div>
+      <div class="card">
+        <h3>IETF SCITT</h3>
+        <p>Supply Chain Integrity, Transparency and Trust — independent, append-only ledgers that let
+        third parties verify receipts without trusting the producer. The direct standards answer to the
+        self-attestation gap (4.5, roadmap).</p>
+      </div>
+      <div class="card">
+        <h3>OMB · risk-based shift</h3>
+        <p>The 2026 OMB action rescinding the prior secure-software-development self-attestation mandate
+        in favor of a risk-based approach reflects the same realization: an attestation checkbox is not a
+        risk control. Behaviour and replayable evidence are.</p>
+      </div>
+    </div>
+  </section>
+  <!-- TALK TO US -->
+  <section>
+    <div class="card">
+      <h3>Tabletop it against a live instance</h3>
+      <p>We are happy to walk through a Mini Shai-Hulud tabletop against a live a11oy instance — what the
+      artifact-behaviour monitor would have flagged, what the 3-axis check would have rejected, and what
+      the governance ledger would let you prove and revoke after the fact. Live signed APIs and the GAP1
+      behavioural monitor are available now at <a href="https://a11oy.net">a11oy.net</a>.</p>
+    </div>
+  </section>
+  <!-- REFERENCES -->
+  <section>
+    <div class="eyebrow">References</div>
+    <ol class="reflist">
+      <li>Cloud Security Alliance, “Mini Shai-Hulud: When Signed Provenance Certified a Supply Chain Worm,” May 15, 2026. <a href="https://labs.cloudsecurityalliance.org/research/csa-research-note-mini-shai-hulud-supply-chain-sigstore-2026/">labs.cloudsecurityalliance.org</a></li>
+      <li>Open Source For U, “Hackers Abuse GitHub Actions and SLSA Signing to Spread Malware Across Open Source Ecosystems,” May 14, 2026. <a href="https://www.opensourceforu.com/2026/05/hackers-abuse-github-actions-and-slsa-signing-to-spread-malware-across-open-source-ecosystems/">opensourceforu.com</a></li>
+      <li>EU AI Act Service Desk FAQ. <a href="https://ai-act-service-desk.ec.europa.eu/en/faq">ai-act-service-desk.ec.europa.eu</a>; Latham &amp; Watkins, “AI Act Update,” May 13, 2026. <a href="https://www.lw.com/en/insights/ai-act-update-eu-resolves-to-change-rules-and-extend-deadlines">lw.com</a></li>
+      <li>IETF SCITT Working Group, Datatracker (draft-ietf-scitt-architecture; draft-dawkins-scitt-ai-article50-00, filed May 25, 2026). <a href="https://datatracker.ietf.org/wg/scitt/">datatracker.ietf.org/wg/scitt</a></li>
+      <li>Wiley Law, “OMB Rescinds Secure Software Development Mandate in Favor of a Risk-Based Approach,” Jan 29, 2026. <a href="https://www.wiley.law/alert-OMB-Rescinds-Secure-Software-Development-Mandate-in-Favor-of-a-Risk-Based-Approach">wiley.law</a></li>
+    </ol>
+  </section>
+</div>
+<footer>
+  a11oy showcase · doctrine v11 · A signature is not proof of safety · behaviour-over-attestation ·
+  prove-or-downgrade · Λ = Conjecture 1 (advisory, &lt; 1.0) · trust &lt; 100% · 0 runtime CDN ·
+  every maturity claim labelled LIVE / ROADMAP.<br>
+  Live proofs fetched from <span style="color:var(--acc2)">/api/a11oy/v1/{pinn/certificate, compliance}</span> — honest NO-LIVE-DATA fallback, never fabricated.
+  About SZL Holdings · sovereign-compute, AI-governance &amp; defense-tech, NYC · UEI [PLACEHOLDER: UEI] · CAGE [PLACEHOLDER: CAGE] · NAICS 541715.
+</footer>
+<script>
+// 0-CDN inline. Prove what we can, LIVE, against real a11oy endpoints; otherwise
+// render an HONEST NO-LIVE-DATA chip — never a fabricated value.
+(function(){
+  function setLive(id, ok, label, href){
+    var el = document.getElementById(id);
+    if(!el) return;
+    var pill = ok ? '<span class="pill live">LIVE ✓</span>'
+                  : '<span class="pill warn">NO-LIVE-DATA</span>';
+    var v = href && ok
+        ? '<span class="v"><a href="'+href+'">'+label+'</a></span>'
+        : '<span class="v">'+label+'</span>';
+    el.innerHTML = pill + v;
+  }
+  function probe(url, id, label, href){
+    fetch(url, {headers:{'accept':'application/json'}})
+      .then(function(r){ return r.ok ? r.json().catch(function(){return {};}) : null; })
+      .then(function(j){ setLive(id, j!==null, label, href); })
+      .catch(function(){ setLive(id, false, label, href); });
+  }
+  // 4.1 — certified live PINN (physics-informed) certificate.
+  probe('/api/a11oy/v1/pinn/certificate', 'pinn-live',
+        'PINN certificate (GAP1 behaviour monitor)', '/api/a11oy/v1/pinn/certificate');
+  // 4.2/4.4 — NIST AI RMF / ISO 42001 / EU AI Act compliance crosswalk.
+  probe('/api/a11oy/v1/compliance', 'comp-live',
+        'NIST AI RMF / ISO 42001 / EU AI Act crosswalk', '/compliance');
+})();
+</script>
+</body>
+</html>