@sanning/proof 0.8.0 → 0.8.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sanning/proof",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "TypeScript kernel of the Sanning verification stack: RFC 8785 (JCS) canonicalization, SHA-256, and Ed25519 verification for Verifiable Event Envelopes. Full-family verifier (inline + external commitment); accepts sanning.agent/v1, sanning.mlflow/v1, sanning.events/v1. Conformance-gated byte-for-byte against the test-vectors corpus.",
   "license": "MIT",
   "type": "module",
@@ -38,11 +38,6 @@
     "typescript": "^5.4.0",
     "vitest": "^2.0.0"
   },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/sanning-io/proof.git",
-    "directory": "ts"
-  },
   "publishConfig": {
     "access": "public"
   },
@@ -56,5 +51,6 @@
     "ed25519",
     "merkle",
     "rfc9162"
-  ]
+  ],
+  "homepage": "https://docs.sanning.io"
 }

package/src/cli.ts

@@ -697,6 +697,35 @@ function reportEvidence(
     }
   }
 
+  // Stamps (evidence-bundle.md §5.2 / §5.3). Printed rather than summarised,
+  // because for a stamp body the WITNESS is the entire independent part
+  // (§5.2.4) — and until now this reporter showed nothing about it at all, so a
+  // §5.3 pack printed a rollup line claiming an on-chain scope with no visible
+  // on-chain result anywhere above it.
+  //
+  // The on-chain column distinguishes all four states in the same three
+  // characters the checkpoint block uses, plus its absence: `✓` confirmed,
+  // `✗` mismatched, `~` asked and unreachable, and NO COLUMN AT ALL when
+  // nothing was checked. A reader must never have to infer "not checked" from
+  // a symbol that also means "could not be reached".
+  if (result.stamps && result.stamps.length > 0) {
+    io.out("");
+    io.out(paint("  Stamps", DIM));
+    for (const st of result.stamps) {
+      const witness =
+        st.anchorRef === null
+          ? paint("~ no witness", Y)
+          : `witness ${st.anchorRef.kind}:${shortTx(st.anchorRef.id)}`;
+      const onChain =
+        st.onChain === null ? "" : `  on-chain ${mark(st.onChainOk)} (${st.onChain.rollup})`;
+      io.out(
+        `    ${mark(st.ok)} ${shortTx(st.stampRef)}  bytes ${mark(st.stampRefOk && st.bodyOk)}` +
+          `  ranges ${mark(st.subtreesOk)}  ${witness}${onChain}`,
+      );
+      for (const e of st.errors) io.out(paint(`        - ${e}`, R));
+    }
+  }
+
   if (result.events.length > 0) {
     io.out("");
     io.out(paint("  Events", DIM));

package/src/evidence.ts

@@ -428,6 +428,35 @@ export interface StampResult {
    * carries it.
    */
   anchorRef: AnchorRef | null;
+  /**
+   * Per-gateway on-chain outcomes for this stamp's `anchor_ref` (§4.2's shape,
+   * `checkpoints[]`'s vocabulary), or `null` when NOTHING WAS CHECKED.
+   *
+   * ── The four states, and why none of them collapses ──
+   *
+   * `null` means not checked — no gateways were supplied, or this stamp names
+   * no witness to check. It is a statement about the RUN, never about the
+   * stamp. The other three are statements about the stamp and live in
+   * `onChain.rollup`: `confirm` (a gateway returned the witnessed bytes),
+   * `mismatch` (a gateway returned DIFFERENT bytes — a finding, and the only
+   * one of the four that fails anything), `unreachable` (we asked and nobody
+   * answered — an availability gap, never an accusation).
+   *
+   * Keeping "not checked" distinct from "unreachable" is the whole point. A
+   * surface handed a collapsed boolean cannot tell "no gateway could be
+   * reached" from "no gateway was tried", and reported the first when the
+   * second was true — a false accusation manufactured by a missing state.
+   */
+  onChain: OnChainResult | null;
+  /**
+   * Derived collapse of `onChain`, mirroring `CheckpointResult.onChainOk` so a
+   * consumer reads one field the same way on both: `false` on mismatch, `true`
+   * on confirm, `null` on unreachable AND on not-checked.
+   *
+   * It is deliberately the LOSSY view — `null` is three-quarters of the state
+   * space here. Anything that needs to tell those apart reads `onChain`.
+   */
+  onChainOk: boolean | null;
   ok: boolean;
   errors: string[];
 }
@@ -749,7 +778,7 @@ export async function verifyEvidenceBundle(
   // wrapper is authentic — and for this body that IS "Sanning signed it", since
   // a stamp carries no second signature of its own inside the bundle.
   if (bodyType === STAMP_TRACE_BODY_TYPE) {
-    return verifyStampTrace(b, specVersionOk, assertedStatus, errors);
+    return verifyStampTrace(b, specVersionOk, assertedStatus, errors, options);
   }
 
   // The DL-52 hand-over body (§5.3): stamps AND the customer's events, joined.
@@ -1365,10 +1394,29 @@ async function verifyDisclosedContent(
   return { contentOk, errors: evErrors };
 }
 
+/**
+ * One `stamps[]` entry's result, plus the witnessed bytes it was graded on.
+ *
+ * `witnessedHex` is internal and never surfaces on `StampResult`: it is the
+ * whole stamp body again, and putting it back on the result would double every
+ * serialized verdict to carry a copy of what the bundle already holds. It
+ * exists so the optional on-chain re-fetch compares the chain against THE SAME
+ * BYTES this function hashed to derive `stamp_ref`, rather than re-reading
+ * `stamp_bytes` out of the body a second time — one value, so the graded bytes
+ * and the compared bytes cannot come apart.
+ *
+ * Undefined exactly when `stamp_bytes` was unusable, in which case the entry
+ * has already failed and there is nothing a gateway could confirm.
+ */
+interface StampEntryOutcome {
+  result: StampResult;
+  witnessedHex?: string;
+}
+
 async function verifyStampEntry(
   raw: unknown,
   seen: Set<string>,
-): Promise<StampResult> {
+): Promise<StampEntryOutcome> {
   const errors: string[] = [];
   const base: StampResult = {
     stampRef: "",
@@ -1382,28 +1430,33 @@ async function verifyStampEntry(
     subtreesOk: false,
     subtrees: [],
     anchorRef: null,
+    onChain: null,
+    onChainOk: null,
     ok: false,
     errors,
   };
 
   if (raw === null || typeof raw !== "object" || Array.isArray(raw)) {
     errors.push("stamp entry is not an object");
-    return base;
+    return { result: base };
   }
   const e = raw as Partial<StampEntry> & Record<string, unknown>;
 
   // --- the witnessed bytes, which are the only authority in this body -------
   if (!isLowerHex(e.stamp_bytes)) {
     errors.push("stamp_bytes is missing or not lowercase hex");
-    return base;
+    return { result: base };
   }
   let bytes: Uint8Array;
   try {
     bytes = hexToBytes(e.stamp_bytes);
   } catch (err) {
     errors.push(`stamp_bytes is not hex: ${stringifyErr(err)}`);
-    return base;
+    return { result: base };
   }
+  // Gated by `isLowerHex` above, so this is already the exact lowercase hex of
+  // the exact witnessed bytes — §5.2.2's "one authority in this body".
+  const witnessedHex: string = e.stamp_bytes;
 
   // --- the derived identity -------------------------------------------------
   const derived = await sha256Hex(bytes);
@@ -1434,7 +1487,7 @@ async function verifyStampEntry(
     const parsed: unknown = JSON.parse(new TextDecoder().decode(bytes));
     if (parsed === null || typeof parsed !== "object" || Array.isArray(parsed)) {
       errors.push("stamp body is not a JSON object");
-      return base;
+      return { result: base, witnessedHex };
     }
     body = parsed as StampBody;
     // Re-canonicalize and compare. The plane replays these bytes verbatim on
@@ -1443,11 +1496,11 @@ async function verifyStampEntry(
     // of the stamp disagree with the one that was witnessed.
     if (jcs(body as unknown as Record<string, unknown>) !== new TextDecoder().decode(bytes)) {
       errors.push("stamp_bytes are not JCS-canonical (RFC 8785)");
-      return base;
+      return { result: base, witnessedHex };
     }
   } catch (err) {
     errors.push(`stamp body is not JSON: ${stringifyErr(err)}`);
-    return base;
+    return { result: base, witnessedHex };
   }
 
   if (body.stamp_version !== STAMP_BODY_VERSION) {
@@ -1459,7 +1512,7 @@ async function verifyStampEntry(
       `unsupported stamp_version ${JSON.stringify(body.stamp_version)} in a ` +
         `${STAMP_TRACE_BODY_TYPE} body (expected ${STAMP_BODY_VERSION})`,
     );
-    return base;
+    return { result: base, witnessedHex };
   }
   base.stampVersion = body.stamp_version;
   base.bodyOk = true;
@@ -1493,7 +1546,7 @@ async function verifyStampEntry(
 
   base.ok =
     base.stampRefOk && base.bodyOk && base.subtreesOk && errors.length === 0;
-  return base;
+  return { result: base, witnessedHex };
 }
 
 /**
@@ -1581,6 +1634,7 @@ async function verifyStampTrace(
   specVersionOk: boolean,
   assertedStatus: string | null,
   errors: string[],
+  options: VerifyEvidenceOptions,
 ): Promise<EvidenceBundleResult> {
   const body = b.body as StampTraceBody;
   if (!Array.isArray(body?.stamps)) {
@@ -1589,10 +1643,27 @@ async function verifyStampTrace(
 
   const seen = new Set<string>();
   const stamps: StampResult[] = [];
+  const witnessed: (string | undefined)[] = [];
   for (const entry of body.stamps) {
-    stamps.push(await verifyStampEntry(entry, seen));
+    const outcome = await verifyStampEntry(entry, seen);
+    stamps.push(outcome.result);
+    witnessed.push(outcome.witnessedHex);
   }
 
+  // --- The optional on-chain re-fetch (§5.2.4's "online act") ---------------
+  //
+  // The SAME stamps[] array §5.3 carries, so it gets the same capability. The
+  // alternative — a stamp that can be re-fetched inside one body and not the
+  // other — asks every consumer to remember which wrapper it is holding before
+  // it can trust `onChain: null`, and that is exactly the kind of per-body
+  // exception a reader eventually gets wrong.
+  const { onChainChecked, gatewayUnavailable } = await refetchStamps(
+    stamps,
+    witnessed,
+    options,
+    errors,
+  );
+
   // --- Rollup ----------------------------------------------------------------
   const anyHardFailure = stamps.some((s) => !s.ok);
   const anyUnwitnessed = stamps.some((s) => s.anchorRef === null);
@@ -1606,17 +1677,25 @@ async function verifyStampTrace(
     // does not have.
     status = "partial";
     errors.push(`${STAMP_TRACE_BODY_TYPE} body carries no stamps`);
-  } else if (anyUnwitnessed) {
-    // The honest half of P-10, one layer up. A stamp with no `anchor_ref` is
-    // sealed and unwitnessed: `retained-by-sanning`, which is a statement about
-    // our coverage and never an accusation about their evidence. It is also not
-    // `verified`, because for a stamp the witness is the entire independent
-    // part — unlike an anchor-trace checkpoint, which still carries a producer
-    // signature and an inclusion proof that stand on their own offline.
+  } else if (gatewayUnavailable || anyUnwitnessed) {
+    // Both hold the bundle at `partial`, and both get said — see §5.3's rollup
+    // for why one note is not enough when there are two different gaps.
     status = "partial";
-    errors.push(
-      "one or more stamps carries no anchor_ref — sealed by Sanning, witnessed by nobody",
-    );
+    if (gatewayUnavailable) {
+      errors.push("one or more stamps could not be re-fetched from the supplied gateways");
+    }
+    if (anyUnwitnessed) {
+      // The honest half of P-10, one layer up. A stamp with no `anchor_ref` is
+      // sealed and unwitnessed: `retained-by-sanning`, which is a statement
+      // about our coverage and never an accusation about their evidence. It is
+      // also not `verified`, because for a stamp the witness is the entire
+      // independent part — unlike an anchor-trace checkpoint, which still
+      // carries a producer signature and an inclusion proof that stand on
+      // their own offline.
+      errors.push(
+        "one or more stamps carries no anchor_ref — sealed by Sanning, witnessed by nobody",
+      );
+    }
   } else {
     status = "verified";
   }
@@ -1627,7 +1706,7 @@ async function verifyStampTrace(
     bodyHashOk: true,
     signatureOk: true,
     bodyType: STAMP_TRACE_BODY_TYPE,
-    onChainChecked: false,
+    onChainChecked,
     checkpoints: [],
     events: [],
     assertedStatus,
@@ -1666,7 +1745,12 @@ async function verifyStampEvidence(
   // --- The stamp half: §5.2's rules, §5.2's code ----------------------------
   const seen = new Set<string>();
   const stamps: StampResult[] = [];
-  for (const entry of body.stamps) stamps.push(await verifyStampEntry(entry, seen));
+  const witnessed: (string | undefined)[] = [];
+  for (const entry of body.stamps) {
+    const outcome = await verifyStampEntry(entry, seen);
+    stamps.push(outcome.result);
+    witnessed.push(outcome.witnessedHex);
+  }
 
   // The join table. ONLY a stamp whose derived ref and witnessed bytes both
   // checked out is joinable: a root read out of bytes that failed their own
@@ -1811,6 +1895,14 @@ async function verifyStampEvidence(
     });
   }
 
+  // --- The optional on-chain re-fetch (§5.2.4's "online act") ---------------
+  const { onChainChecked, gatewayUnavailable } = await refetchStamps(
+    stamps,
+    witnessed,
+    options,
+    errors,
+  );
+
   // --- Rollup ---------------------------------------------------------------
   // Rule 4: a declared event MUST be checked. `events[]` present and unverified
   // is the false green this body exists to prevent, so an event that did not
@@ -1824,13 +1916,23 @@ async function verifyStampEvidence(
   } else if (stamps.length === 0 && eventResults.length === 0) {
     status = "partial";
     errors.push(`${STAMP_EVIDENCE_BODY_TYPE} body carries no stamps and no events`);
-  } else if (anyUnwitnessed) {
-    // §5.3.3 rule 6, inherited whole from §5.2.4: for a stamp the witness IS
-    // the independent part, so the events resting on it inherit `partial`.
+  } else if (gatewayUnavailable || anyUnwitnessed) {
+    // Both hold the bundle at `partial`, and BOTH get said. A stamp nobody
+    // witnessed and a witness we could not reach are different gaps with
+    // different fixes — one waits for the interval, the other for the network —
+    // and an auditor told only about the second would read the first as fine.
+    // The order is fixed so the two kernels emit the same list.
     status = "partial";
-    errors.push(
-      "one or more stamps carries no anchor_ref — sealed by Sanning, witnessed by nobody",
-    );
+    if (gatewayUnavailable) {
+      errors.push("one or more stamps could not be re-fetched from the supplied gateways");
+    }
+    if (anyUnwitnessed) {
+      // §5.3.3 rule 6, inherited whole from §5.2.4: for a stamp the witness IS
+      // the independent part, so the events resting on it inherit `partial`.
+      errors.push(
+        "one or more stamps carries no anchor_ref — sealed by Sanning, witnessed by nobody",
+      );
+    }
   } else {
     status = "verified";
   }
@@ -1841,7 +1943,7 @@ async function verifyStampEvidence(
     bodyHashOk: true,
     signatureOk: true,
     bodyType: STAMP_EVIDENCE_BODY_TYPE,
-    onChainChecked: false,
+    onChainChecked,
     checkpoints: [],
     events: eventResults,
     assertedStatus,
@@ -1850,6 +1952,83 @@ async function verifyStampEvidence(
   };
 }
 
+/**
+ * The optional on-chain re-fetch over `stamps[]`, shared by §5.2 and §5.3.
+ *
+ * ── Why the results land on `stamps[]` and `checkpoints` stays empty ──
+ *
+ * A stamp body carries no checkpoints. Synthesising `CheckpointResult`s to
+ * carry these outcomes would make a stamp indistinguishable from a checkpoint
+ * in every consumer that reads `checkpoints[]` — the exact conflation §5.2.1
+ * and §5.3.1 refused twice, most sharply in "a Sanning attestation
+ * indistinguishable on the wire from a producer's". They are different
+ * artifacts with different signers and different meanings when absent, and a
+ * reader must never have to guess which one it is holding. So the stamp
+ * results go on the stamps, and `checkpoints: []` keeps saying the true thing:
+ * this body has none.
+ *
+ * ── Why an unwitnessed stamp gets `onChain: null` and NOT all-unreachable ──
+ *
+ * The anchor-trace path synthesises an all-`unreachable` result for a
+ * checkpoint with no `anchor_ref`. That is not copied here, for two reasons.
+ *
+ * It would be untrue: nothing was asked of any gateway, so reporting that
+ * every gateway failed to answer invents a network event. "Not checked" and
+ * "we asked and nobody answered" are different facts, and collapsing them is
+ * precisely the defect that had a surface reporting an unreachable gateway
+ * when it had contacted none.
+ *
+ * And it would be load-bearing in the wrong direction. Over there the
+ * synthesis exists to drive `gatewayUnavailable`, which is what downgrades that
+ * run to `partial`. Here §5.2.4 already downgrades an unwitnessed stamp to
+ * `partial` on its own, with a better error. Copying the synthesis would add
+ * nothing to the status and would silently move the CLI exit code from 0 to 3
+ * for an unwitnessed stamp — changing what an auditor's script does, based on
+ * nothing but whether the caller happened to pass a gateway list.
+ */
+async function refetchStamps(
+  stamps: StampResult[],
+  witnessed: (string | undefined)[],
+  options: VerifyEvidenceOptions,
+  errors: string[],
+): Promise<{ onChainChecked: boolean; gatewayUnavailable: boolean }> {
+  const gateways = options.gateways ?? [];
+  const onChainChecked = gateways.length > 0;
+  if (!onChainChecked) return { onChainChecked, gatewayUnavailable: false };
+
+  const fetchImpl = options.fetchImpl ?? (globalThis.fetch as typeof fetch | undefined);
+  if (typeof fetchImpl !== "function") {
+    errors.push("on-chain re-fetch requested but no fetch implementation is available");
+    return { onChainChecked, gatewayUnavailable: true };
+  }
+
+  let gatewayUnavailable = false;
+  for (let i = 0; i < stamps.length; i++) {
+    const st = stamps[i]!;
+    const witnessedHex = witnessed[i];
+    // No witness named, or bytes we could not read: nothing to re-fetch, and
+    // nothing a gateway could confirm or deny. Left as `onChain: null`.
+    if (st.anchorRef === null || witnessedHex === undefined) continue;
+
+    const outcome = await refetchStamp(witnessedHex, st.anchorRef, gateways, fetchImpl);
+    st.onChain = outcome.onChain;
+    st.onChainOk = outcome.onChain.onChainOk;
+    if (outcome.unavailable) gatewayUnavailable = true;
+    if (outcome.error) st.errors.push(outcome.error);
+    // Fold the on-chain dimension in exactly as a checkpoint does: a MISMATCH
+    // (false) fails the stamp — the chain does not hold what the bundle says
+    // was witnessed. UNREACHABLE (null) leaves an offline-sound stamp ok and
+    // downgrades the run to `partial` via gatewayUnavailable. A confirm (true)
+    // changes nothing that was not already true offline.
+    //
+    // `st.ok` is kept and narrowed rather than recomputed: its offline form
+    // includes `errors.length === 0`, and re-evaluating that AFTER pushing an
+    // unreachable note would fail a stamp for a gateway being down.
+    st.ok = st.ok && st.onChainOk !== false;
+  }
+  return { onChainChecked, gatewayUnavailable };
+}
+
 // ===========================================================================
 // Ingest: materializing the disclosed raw bytes (evidence-bundle.md §5.1).
 //
@@ -2621,6 +2800,10 @@ async function refetchCheckpoint(
 ): Promise<{ onChain: OnChainResult; unavailable: boolean; error?: string }> {
   let expectedHex: string | undefined;
   try {
+    // A checkpoint's witnessed bytes are its envelope RE-CANONICALIZED. The
+    // bundle carries the envelope as a JSON object, not as bytes, so what was
+    // uploaded has to be recomputed from it. See `refetchStamp` for the case
+    // where this step is not merely unnecessary but WRONG.
     expectedHex = toHex(utf8(jcs(cp.envelope)));
   } catch {
     // Cannot canonicalize the checkpoint envelope — every gateway is a mismatch
@@ -2628,6 +2811,54 @@ async function refetchCheckpoint(
     expectedHex = undefined;
   }
 
+  return refetchAnchored("checkpoint", expectedHex, anchorRef, gateways, fetchImpl);
+}
+
+// Re-fetch a STAMP's witnessed bytes (evidence-bundle.md §5.2.2 / §5.3.2).
+//
+// ── The one step this path must NOT copy from the checkpoint path ──
+//
+// `refetchCheckpoint` recomputes `JCS(envelope)` because a checkpoint's
+// witnessed bytes are not in the bundle — only the object they were derived
+// from is. A stamp is the opposite case: §5.2.2 defines `stamp_bytes` as
+// "lowercase hex of the exact JCS bytes that were handed to the witness", and
+// §5.3.2 repeats it — *"the EXACT bytes that were witnessed, verbatim"*. They
+// are already the bytes, already hex, already lowercase (`isLowerHex` gated
+// them), and `stamp_ref` is their SHA-256.
+//
+// So the expected hex IS `stamp_bytes`, and re-canonicalizing would be a
+// defect, not a redundancy: it would compare the chain against bytes NOBODY
+// SIGNED. On a canonical body the two agree and the bug hides; on a body that
+// is not canonical — the exact case §5.2.2 makes the kernel check for, because
+// the plane replays these bytes as text precisely so a normalizing serializer
+// cannot alter them — a re-canonicalizing verifier reports `mismatch` against
+// a chain that faithfully holds what it was given. A false accusation, from
+// the verifier, about untampered evidence.
+//
+// The bytes handed here are the SAME value `verifyStampEntry` hashed to derive
+// `stamp_ref`, threaded through rather than re-read from the body, so the bytes
+// graded and the bytes compared cannot drift apart.
+async function refetchStamp(
+  witnessedHex: string,
+  anchorRef: AnchorRef,
+  gateways: string[],
+  fetchImpl: typeof fetch,
+): Promise<{ onChain: OnChainResult; unavailable: boolean; error?: string }> {
+  return refetchAnchored("stamp", witnessedHex, anchorRef, gateways, fetchImpl);
+}
+
+// The part both paths share: probe every gateway, roll the outcomes up under
+// the ONE rule (`rollupOnChain`), and phrase the finding. Extracted rather than
+// copied — a second rollup rule is a second place for "mismatch beats confirm
+// beats unreachable" to drift, and the drifted copy is the one nobody reads.
+// The subject only ever selects wording; it never changes a verdict.
+async function refetchAnchored(
+  subject: "checkpoint" | "stamp",
+  expectedHex: string | undefined,
+  anchorRef: AnchorRef,
+  gateways: string[],
+  fetchImpl: typeof fetch,
+): Promise<{ onChain: OnChainResult; unavailable: boolean; error?: string }> {
   const perGateway: PerGatewayOutcome[] = [];
   for (const gw of gateways) {
     perGateway.push({
@@ -2639,9 +2870,12 @@ async function refetchCheckpoint(
   const onChain = rollupOnChain(perGateway);
   let error: string | undefined;
   if (onChain.rollup === "mismatch") {
-    error = `on-chain bytes at ${anchorRef.id} do not match the bundle's checkpoint envelope`;
+    error =
+      subject === "checkpoint"
+        ? `on-chain bytes at ${anchorRef.id} do not match the bundle's checkpoint envelope`
+        : `on-chain bytes at ${anchorRef.id} do not match the stamp's witnessed bytes`;
   } else if (onChain.rollup === "unreachable") {
-    error = `checkpoint ${anchorRef.id} unreachable on all gateways`;
+    error = `${subject} ${anchorRef.id} unreachable on all gateways`;
   }
   return { onChain, unavailable: onChain.rollup === "unreachable", error };
 }

package/vectors/README.md

@@ -8,6 +8,24 @@ That distinction is the whole point. A rule that consumers must agree with needs
 a statement they can *fetch*, not one they have to be trusted to have copied
 correctly.
 
+## `stamp-on-chain.json`
+
+The rule that decides what re-fetching a **stamp's witness** from a gateway does
+and does not settle — the optional, online half of `sanning.stamp.trace/v1` and
+`sanning.stamp.evidence/v1` (`evidence-bundle.md` §5.2.4 / §5.3.4). Implemented
+by [`../src/evidence.ts`](../src/evidence.ts) and asserted against this table by
+[`../test/stamp-on-chain-vectors.test.ts`](../test/stamp-on-chain-vectors.test.ts)
+— **and by the Python kernel against the same bytes**, in
+`tests/test_stamp_on_chain_vectors.py`, so neither kernel can pass by agreeing
+with the other.
+
+**The one thing a consumer must not do with it: collapse the four states into a
+boolean.** `not checked` · `confirm` · `mismatch` · `unreachable`. A reader that
+cannot tell the first from the last will report that no gateway could be reached
+on a run that contacted none — a false accusation manufactured by a missing
+state, and the defect this table was written after. Vendoring rules are the same
+three steps as below, against `vectors/stamp-on-chain.json`.
+
 ## `pack-grading.json`
 
 The rule that decides whether a **pack** — a signed bundle plus whatever