@sanning/proof 0.19.0 → 0.20.0

package/vectors/jcs-reader.json

@@ -1,10 +1,10 @@
 {
   "rule": "jcs-reader",
   "ruleVersion": 3,
-  "statement": "How a kernel reads bytes that claim to be JCS(value) (RFC 8785). Five checks, none of them left to a built-in decoder's defaults: strict UTF-8, no LEADING byte-order mark, no non-finite literal, no object that names one member twice (I-JSON, RFC 7493; ruleVersion 3, proof#144), and no UNPAIRED surrogate in the parsed value. The fourth is not the first one twice: a surrogate written as the ASCII escape `\\ud800` survives every byte-level check, because the bytes are ASCII, and the parser produces the malformed code unit afterwards. Everything else a JSON parser rejects is rejected. A reader that accepts any of the rejected cases here is reading a set of bytes some other reader will read differently, and a producer chooses those bytes: that is a split verdict on one pack, not a spelling preference. The accepted cases matter as much as the rejected ones -- an honest body carrying astral characters, noncharacters, a U+FEFF inside a string value or combining marks is conformant and must keep verifying.",
+  "statement": "How a kernel reads bytes that claim to be JCS(value) (RFC 8785). Five checks, none of them left to a built-in decoder's defaults: strict UTF-8, no LEADING byte-order mark, no non-finite literal, no object that names one member twice (I-JSON, RFC 7493; ruleVersion 3), and no UNPAIRED surrogate in the parsed value. The fourth is not the first one twice: a surrogate written as the ASCII escape `\\ud800` survives every byte-level check, because the bytes are ASCII, and the parser produces the malformed code unit afterwards. Everything else a JSON parser rejects is rejected. A reader that accepts any of the rejected cases here is reading a set of bytes some other reader will read differently, and a producer chooses those bytes: that is a split verdict on one pack, not a spelling preference. The accepted cases matter as much as the rejected ones -- an honest body carrying astral characters, noncharacters, a U+FEFF inside a string value or combining marks is conformant and must keep verifying.",
   "home": "@sanning/proof -- ts/vectors/jcs-reader.json. This file is the RULE, not a test fixture of one implementation. TypeScript implements it in ts/src/verifier.ts as jcsParse and Python in src/sanning_proof/canonicalize.py as jcs_loads; ts/test/host-wording.test.ts and tests/test_host_wording.py hold BOTH kernels to this file, so neither can pass by agreeing with the other.",
   "howToUse": "Base64-decode `bytesB64`, hand the bytes to your kernel's JCS reader, and assert that it returns a value where `accept` is true and throws or raises where it is false. Never decode to a string first: half of these cases are ABOUT the decode, and a reader tested through a string has not been tested. Where a case carries `error`, the refusal's message is that exact string in both kernels: a duplicate's message is kernel wording, and a finding carries it.",
-  "whyItExists": "Round four of proof#140 put a strict decoder on the TypeScript side of three sites and left json.loads(<bytes>) on the Python side of two. CPython hands bytes to detect_encoding and decodes with errors='surrogatepass', so Python became the LENIENT kernel: a sanning.anchor.trace/v3 pack whose checkpoint record bytes were BOM + JCS(record), re-sealed so the pack verifies, read `verified` with zero exceptions in Python and `mixed` in TypeScript. The full ladder, the case leg and CI were green over it. Both guards were source assertions over different module sets, and the TypeScript one stated the false premise in its own comment. One table both kernels read is the fix for that.",
+  "whyItExists": "A strict decoder at the TypeScript sites beside json.loads(<bytes>) on the Python side would split the kernels. CPython hands bytes to detect_encoding and decodes with errors='surrogatepass', so Python became the LENIENT kernel: a sanning.anchor.trace/v3 pack whose checkpoint record bytes were BOM + JCS(record), re-sealed so the pack verifies, read `verified` with zero exceptions in Python and `mixed` in TypeScript. One table both kernels read keeps them from splitting.",
   "cases": [
     {
       "id": "plain",
@@ -52,7 +52,7 @@
       "id": "escaped-lone-surrogate-high",
       "bytesB64": "eyJrIjoiY1x1ZDgwMHgifQ==",
       "accept": false,
-      "why": "a high surrogate written as the ASCII escape `\\ud800`, with no low surrogate after it. PURE ASCII ON THE WIRE, which is the whole point: the strict UTF-8 decode above cannot see it, and both kernels accepted it while their own text said they refuse a lone surrogate. I-JSON (RFC 7493 2.1) forbids an unpaired surrogate and RFC 8785 cannot emit one, since it serializes to UTF-8 and UTF-8 has no encoding for a surrogate code point. Accepted, it is not a lenience anyone can live with: the Python kernel could not then encode the value for a sort key, `read_chains` raised, and the CLI reported `no event chain was found to follow in this bundle` for a bundle whose chains TypeScript read and named a finding on (proof#154)"
+      "why": "a high surrogate written as the ASCII escape `\\ud800`, with no low surrogate after it. PURE ASCII ON THE WIRE, which is the whole point: the strict UTF-8 decode above cannot see it, and a reader that accepts it contradicts its own refusal of a lone surrogate. I-JSON (RFC 7493 2.1) forbids an unpaired surrogate and RFC 8785 cannot emit one, since it serializes to UTF-8 and UTF-8 has no encoding for a surrogate code point. Accepted, it is not a lenience anyone can live with: the Python kernel could not then encode the value for a sort key, `read_chains` raised, and the CLI reported `no event chain was found to follow in this bundle` for a bundle whose chains TypeScript read and named a finding on"
     },
     {
       "id": "escaped-lone-surrogate-low",
@@ -82,7 +82,7 @@
       "id": "raw-0x80",
       "bytesB64": "eyJhIjoieIB5In0=",
       "accept": false,
-      "why": "a continuation byte with no lead byte: not UTF-8 at all. The case gate 4 found, where `new TextDecoder()` substituted U+FFFD and read `verified`"
+      "why": "a continuation byte with no lead byte: not UTF-8 at all. `new TextDecoder()` would substitute U+FFFD and read `verified`"
     },
     {
       "id": "overlong-solidus",
@@ -167,7 +167,7 @@
       "bytesB64": "eyJzcGVjX3ZlcnNpb24iOiJqdW5rIiwic3BlY192ZXJzaW9uIjoic2FubmluZy5ldmVudHMvdjIifQ==",
       "accept": false,
       "error": "duplicate key \"spec_version\"",
-      "why": "an object that names one member twice (proof#144). I-JSON (RFC 7493 section 2.3), which RFC 8785 is defined over, forbids it, and RFC 8785 cannot emit it. `json.loads` and `JSON.parse` both keep the LAST value and say nothing, so a reader that looks at the first sees junk while the kernel verifies the second"
+      "why": "an object that names one member twice. I-JSON (RFC 7493 section 2.3), which RFC 8785 is defined over, forbids it, and RFC 8785 cannot emit it. `json.loads` and `JSON.parse` both keep the LAST value and say nothing, so a reader that looks at the first sees junk while the kernel verifies the second"
     },
     {
       "id": "duplicate-nested",
@@ -239,7 +239,7 @@
       "id": "case-variant-names",
       "bytesB64": "eyJzcGVjX3ZlcnNpb24iOiJzYW5uaW5nLmV2ZW50cy92MiIsIlNwZWNfVmVyc2lvbiI6Imp1bmsiLCJcdTAxN2ZwZWNfdmVyc2lvbiI6Imp1bmsifQ==",
       "accept": true,
-      "why": "names that differ only in case, or by a look-alike such as the long s U+017F, are DIFFERENT names to I-JSON and to both parsers, and this rule does not refuse them. No spec in this repository pins how a reader treats a key that folds to a defined one; to every reader here it is an unknown member, and unknown members are ignored. The Go bundle reader in sanning-io/agent refuses these at the top level of a bundle, which is a recorded Go divergence (proof#144)"
+      "why": "names that differ only in case, or by a look-alike such as the long s U+017F, are DIFFERENT names to I-JSON and to both parsers, and this rule does not refuse them. No spec in this repository pins how a reader treats a key that folds to a defined one; to every reader here it is an unknown member, and unknown members are ignored. The Go bundle reader in sanning-io/agent refuses these at the top level of a bundle, which is a recorded Go divergence"
     }
   ]
 }

package/vectors/pack-grading.json

@@ -1,17 +1,21 @@
 {
   "rule": "pack-grading",
-  "ruleVersion": 6,
-  "statement": "What a verification surface may CLAIM about a pack it was handed. verified is reachable ONLY when every record's own bytes bound to its own commitment and nothing is missing, unreadable, surplus or omitted. Absent or unreadable evidence is incomplete (UNKNOWN), never failed and never verified. A hard kernel verdict wins: malformed > failed > incomplete > the kernel's own headline. A pack that DEVIATES from its own signed declaration (evidence-bundle.md \u00a75.4) is failed, and every deviation is a cause: a declared record that is absent, a present record nobody declared, or a record the pack declared withheld whose bytes its own SIGNED BODY supplies. A reading that rests instead on the UNSIGNED content handed in beside a pack is not a deviation and never reaches failed (proof#147): each content-dependent finding is its own cause and carries the pack to incomplete, because whoever assembles a case fills that map in, so an accuser holding an intact pack could otherwise reach failed with no key at all. A deviation and a content-dependent finding together are still failed, because the deviation reads off the signed body and a failing check wins. A declaration check that came back partial therefore splits in THREE, and only two of the three turn on the declaration's readability: no declaration member in the body at all moves nothing, because every pack built before \u00a75.4 is that case; a declaration the reader CANNOT READ makes the pack incomplete, because declaration_version is chosen by the party that assembles the pack and has no accept-set, so an unreadable claim must never reach a clean verdict; and a declaration the reader read perfectly well whose disclosure only unsigned bytes could settle makes the pack incomplete as well, named as what the reader could not establish rather than as what the holder did. The grade carries the declaration check verdict in its own output field, so a consumer that keeps only the grade can still tell a declared pack from an undeclared one. Rule version 6 (evidence-bundle.md \u00a75.4.5 v1.20, A22): a record is WITHHELD BY ITS DECLARATION when a readable declaration lists it in declared_withheld, its ok is true, its contentOk is null and its payloadBindingOk is true; it counts in recordsWithheld and never in recordsVerified, it is taken out of expected and missing before the disclosure causes are computed, and it holds the pack at nothing, so a pack whose every record its declaration withholds grades verified with recordsVerified zero. A record that fails any of the four, a pack with no readable declaration, and an input that does not carry eventId and payloadBindingOk keep rule version 5's reading.",
+  "ruleVersion": 9,
+  "statement": "What a verification surface may claim about a pack it was handed. Rule version 8 (evidence-bundle.md section 5.4.5): every problem the bundle verifier found, every cause and the declaration check each map to one of six claims (signed, unchanged, witnessed, complete, agreed, follows_rules) and one state (proven, disproven, not_proven), and the pack verdict is read off the claims: failed where a claim is disproven, else incomplete where a claim is not proven, else verified. verified is reachable only when every record's own bytes bound to its own commitment and nothing is missing, unreadable, surplus or omitted. Absent or unreadable evidence is not proven, so incomplete, never failed and never verified. A bundle status this rule cannot interpret is not proven too. A pack that deviates from its own signed declaration (evidence-bundle.md section 5.4) is failed, and every deviation is a cause: a declared record that is absent, a present record nobody declared, or a record the pack declared withheld whose bytes its own signed body supplies. A reading that rests instead on the unsigned content handed in beside a pack is not a deviation and never reaches failed: each content-dependent finding is its own cause and carries the pack to incomplete, because whoever assembles a case fills that map in, so an accuser holding an intact pack could otherwise reach failed with no key at all. A deviation and a content-dependent finding together are still failed, because the deviation reads off the signed body and a disproof wins. A declaration check that came back incomplete therefore splits in three, and only two of the three turn on the declaration's readability: no declaration member in the body at all moves nothing, because the complete claim is then out of scope; a declaration the reader cannot read makes the pack incomplete, because declaration_version is chosen by the party that assembles the pack and has no accept-set, so an unreadable claim must never reach a clean verdict; and a declaration the reader read perfectly well whose disclosure only unsigned bytes could settle makes the pack incomplete as well, named as what the reader could not establish rather than as what the holder did. The grade carries the declaration check verdict in its own output field, so a consumer that keeps only the grade can still tell a declared pack from an undeclared one. Rule version 6: a record is withheld by its declaration when a readable declaration lists it in declared_withheld, its ok is true, its contentOk is null and its payloadBindingOk is true; it counts in recordsWithheld and never in recordsVerified, it is taken out of expected and missing before the disclosure causes are computed, and it holds the pack at nothing, so a pack whose every record its declaration withholds grades verified with recordsVerified zero. A record that fails any of the four, a pack with no readable declaration, and an input that does not carry eventId and payloadBindingOk keep rule version 5's reading. Rule version 7 (agent-events.md section 10): each record's agent reading is an input. Rule version 9: every reason of an agent reading that is not verified is a cause, after the declaration's causes, in bundle order and then in the reading's own order. A reason that reads incomplete (event_schema_unknown, a vocabulary version this reader does not know, or listed_record_absent, a record a closing record lists and the pack does not hold) is agent_record_incomplete and is not proven, so incomplete. Every other reason is agent_record_nonconforming: the record is signed and intact and does not follow its vocabulary, so it disproves follows_rules and the pack is failed with the reason kind nonconforming, and a disproof of any other claim beside it makes the reason kind changed. A closing record that lists two records the pack does not hold is two causes. A finding on an agent record is never a cause and moves nothing.",
   "home": "@sanning/proof — ts/vectors/pack-grading.json. This file is the RULE, not a test fixture of one implementation. The kernel implements it in ts/src/grading.ts and is held to it by ts/test/grading.test.ts.",
   "consumers": "A surface that grades packs SHOULD call the kernel's gradePack rather than derive the rule again. A surface that cannot yet (an older pinned kernel, another language) vendors this file byte-for-byte, asserts its own derivation against it, and runs a drift check that compares its copy against the copy shipped in the @sanning/proof tarball at vectors/pack-grading.json. A vendored copy that is not byte-identical to this one is a defect, not a variant.",
-  "howToUse": "Adapt a kernel verification result and a disclosure account into the shapes below, call gradePack, and assert the expectations. `kernel` gives the per-event outcome classes the kernel returns; `logs` gives the account of which records disclosed bytes; `omissions` gives the signed-leaf_count completeness notes. Nothing here depends on how the bytes were transported: a directory read and a browser drop produce the same account and must produce the same verdict. `declaration`, where a case carries one, gives the declaration check's verdict, whether the body carried a declaration member at all, and how many deviations it found; pass a check of that shape as gradePack's optional fourth argument. A case with no `declaration` key calls gradePack with three arguments, which is the pre-§5.4 behavior and must not move, and its `expect.declaration` is absent. Rule version 6: `kernel.withheldBound` and `kernel.withheldUnbound` events carry eventId withheld-0, withheld-1 and so on, in that order, and payloadBindingOk true and null respectively, unless `kernel.v5Adapter` is true, in which case they carry neither field; `logs.withheld` adds that many of those ids to the account's expected AND missing lists, after the counted ones; `declaration.declaredWithheld` is how many of them, from withheld-0, the check lists in declared_withheld (0 where absent); and `expect.recordsWithheld`, where present, is the grade's count of records withheld by their declaration.",
+  "howToUse": "Adapt a kernel verification result and a disclosure account into the shapes below, call gradePack, and assert the expectations. `kernel` gives the per-event outcome classes the kernel returns; `logs` gives the account of which records disclosed bytes; `omissions` gives the signed-leaf_count completeness notes. Nothing here depends on how the bytes were transported: a directory read and a browser drop produce the same account and must produce the same verdict. `declaration`, where a case carries one, gives the declaration check's verdict, whether the body carried a declaration member at all, and how many deviations it found; pass a check of that shape as gradePack's optional fourth argument. A case with no `declaration` key calls gradePack with three arguments, which is the pre-§5.4 behavior and must not move, and its `expect.declaration` is absent. Rule version 6: `kernel.withheldBound` and `kernel.withheldUnbound` events carry eventId withheld-0, withheld-1 and so on, in that order, and payloadBindingOk true and null respectively, unless `kernel.v5Adapter` is true, in which case they carry neither field; `logs.withheld` adds that many of those ids to the account's expected AND missing lists, after the counted ones; `declaration.declaredWithheld` is how many of them, from withheld-0, the check lists in declared_withheld (0 where absent); and `expect.recordsWithheld`, where present, is the grade's count of records withheld by their declaration. Rule version 9: `kernel.agentFailed`, `kernel.agentIncomplete`, `kernel.agentTwoAbsent` and `kernel.agentFindings` are events with eventId agent-0, agent-1 and so on, in that order after every other class, each with ok true and contentOk true and an `agent` reading of verdict failed (reason bad_value at /metadata/run/seq), incomplete (reason event_schema_unknown at /extras/event_schema), incomplete with two reasons (listed_record_absent at /metadata/closing/record_ids/0 and at /metadata/closing/record_ids/2) and verified with the finding unended, respectively; each reading that is not verified carries `reasons`, every reason in order; every other event carries no agent reading. Their bytes count in `logs` like any record whose content bound.",
   "kernelEventClasses": {
     "okBound": "{ ok: true, contentOk: true } — the record's own bytes hashed to its own commitment",
     "okUnknown": "{ ok: true, contentOk: null } — structurally fine, but no bytes were disclosed",
     "mismatched": "{ ok: false, contentOk: false } — the bytes disagree with the commitment",
     "brokenNoContent": "{ ok: false, contentOk: null } — the record itself does not verify",
     "withheldBound": "{ eventId: withheld-<i>, ok: true, contentOk: null, payloadBindingOk: true } — no content bound, the record bytes bound to the envelope (rule version 6)",
-    "withheldUnbound": "{ eventId: withheld-<i>, ok: true, contentOk: null, payloadBindingOk: null } — no content bound, and the record bytes did not travel either (rule version 6)"
+    "withheldUnbound": "{ eventId: withheld-<i>, ok: true, contentOk: null, payloadBindingOk: null } — no content bound, and the record bytes did not travel either (rule version 6)",
+    "agentFailed": "{ eventId: agent-<i>, ok: true, contentOk: true, agent: { verdict: failed, reason: bad_value, at: /metadata/run/seq, reasons: [{ reason: bad_value, at: /metadata/run/seq }], findings: [] } }: an agent record that does not follow its vocabulary (rule version 9)",
+    "agentIncomplete": "{ eventId: agent-<i>, ok: true, contentOk: true, agent: { verdict: incomplete, reason: event_schema_unknown, at: /extras/event_schema, reasons: [{ reason: event_schema_unknown, at: /extras/event_schema }], findings: [] } }: an agent record this reader could not read to the end (rule version 9)",
+    "agentTwoAbsent": "{ eventId: agent-<i>, ok: true, contentOk: true, agent: { verdict: incomplete, reason: listed_record_absent, at: /metadata/closing/record_ids/0, reasons: [{ reason: listed_record_absent, at: /metadata/closing/record_ids/0 }, { reason: listed_record_absent, at: /metadata/closing/record_ids/2 }], findings: [] } }: a closing record whose first and third listed records the pack does not hold (rule version 9)",
+    "agentFindings": "{ eventId: agent-<i>, ok: true, contentOk: true, agent: { verdict: verified, findings: [unended] } }: a verified agent record with a finding (rule version 7)"
   },
   "cases": [
     {
@@ -40,7 +44,7 @@
     },
     {
       "id": "one-log-deleted",
-      "why": "absent bytes are UNKNOWN — never verified, never failed (P-10)",
+      "why": "absent bytes are unknown — never verified, never failed (P-10)",
       "kernel": { "status": "verified", "okBound": 25, "okUnknown": 1, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 26, "present": 25, "missing": 1, "unreadable": 0, "extra": 0 },
       "omissions": [],
@@ -48,7 +52,7 @@
     },
     {
       "id": "every-log-deleted",
-      "why": "the silent-catch regression: zero bytes hashed must never read as a verified pack",
+      "why": "the silent-catch case: zero bytes hashed must never read as a verified pack",
       "kernel": { "status": "verified", "okBound": 0, "okUnknown": 26, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 26, "present": 0, "missing": 26, "unreadable": 0, "extra": 0 },
       "omissions": [],
@@ -56,7 +60,7 @@
     },
     {
       "id": "withheld-record-clean-account",
-      "why": "the case the terminal got wrong (proof#110). A bundle the kernel grades `verified` under evidence-bundle.md §3, holding one record the producer WITHHELD. The disclosure account is clean, and correctly so: no bytes were ever expected for a record that was never offered, so nothing is missing, unreadable, surplus or omitted and there is no cause to report. The record is still unhashed. The PACK is `incomplete` while the BUNDLE is `verified`: the two enums are distinct, and an undetermined record ON ITS OWN is enough to downgrade, with no cause beside it. Every other incomplete case here carries a cause, so a surface could satisfy all of them by keying off `causes` alone and still print a green verdict over a record nobody checked, which is exactly what `proof verify` did.",
+      "why": "the case the terminal got wrong. A bundle the kernel grades `verified` under evidence-bundle.md §3, holding one record the producer WITHHELD. The disclosure account is clean, and correctly so: no bytes were ever expected for a record that was never offered, so nothing is missing, unreadable, surplus or omitted and there is no cause to report. The record is still unhashed. The PACK is `incomplete` while the BUNDLE is `verified`: the two enums are distinct, and an undetermined record ON ITS OWN is enough to downgrade, with no cause beside it. Every other incomplete case here carries a cause, so a surface could satisfy all of them by keying off `causes` alone and still print a green verdict over a record nobody checked, which is exactly what `proof verify` did.",
       "kernel": { "status": "verified", "okBound": 2, "okUnknown": 1, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 2, "present": 2, "missing": 0, "unreadable": 0, "extra": 0 },
       "omissions": [],
@@ -64,7 +68,7 @@
     },
     {
       "id": "one-log-unreadable",
-      "why": "a file we could not read is our fault, not the record's — UNKNOWN",
+      "why": "a file we could not read is our fault, not the record's — unknown",
       "kernel": { "status": "verified", "okBound": 25, "okUnknown": 1, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 26, "present": 25, "missing": 0, "unreadable": 1, "extra": 0 },
       "omissions": [],
@@ -96,7 +100,7 @@
     },
     {
       "id": "leaf-count-unreadable",
-      "why": "a completeness check we could not run is UNKNOWN, not a pass",
+      "why": "a completeness check we could not run is unknown, not a pass",
       "kernel": { "status": "verified", "okBound": 26, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 26, "present": 26, "missing": 0, "unreadable": 0, "extra": 0 },
       "omissions": [{ "kind": "unreadable", "checkpointRef": "TX", "signed": null, "presented": null }],
@@ -105,10 +109,10 @@
     {
       "id": "malformed-wins",
       "why": "an unreadable bundle is named for what it is, whatever else is true",
-      "kernel": { "status": "malformed", "okBound": 0, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0 },
+      "kernel": { "status": "incomplete", "okBound": 0, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 0, "present": 0, "missing": 0, "unreadable": 0, "extra": 0 },
       "omissions": [],
-      "expect": { "verdict": "malformed", "recordsVerified": 0, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0 }
+      "expect": { "verdict": "incomplete", "recordsVerified": 0, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0 }
     },
     {
       "id": "tamper-beats-absence",
@@ -129,14 +133,14 @@
     {
       "id": "kernel-headline-passes-through",
       "why": "this rule downgrades a verdict; it never invents one",
-      "kernel": { "status": "partial", "okBound": 26, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0 },
+      "kernel": { "status": "incomplete", "okBound": 26, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 26, "present": 26, "missing": 0, "unreadable": 0, "extra": 0 },
       "omissions": [],
-      "expect": { "verdict": "partial", "recordsVerified": 26, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0 }
+      "expect": { "verdict": "incomplete", "recordsVerified": 26, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0 }
     },
     {
       "id": "unknown-headline-is-not-repeated",
-      "why": "a headline this rule cannot interpret is a check it could not run — UNKNOWN, never repeated verbatim. The status a surface prints must not be attacker-chosen: passing an uninterpreted string through is how a pack could be headlined with the one word the trust model forbids",
+      "why": "a headline this rule cannot interpret is a check it could not run — unknown, never repeated verbatim. The status a surface prints must not be attacker-chosen: passing an uninterpreted string through is how a pack could be headlined with the one word the trust model forbids",
       "kernel": { "status": "SAFE", "okBound": 26, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 26, "present": 26, "missing": 0, "unreadable": 0, "extra": 0 },
       "omissions": [],
@@ -162,7 +166,7 @@
     },
     {
       "id": "declaration-content-dependent",
-      "why": "the pack agrees with its own claim everywhere its signature reaches, and does not line up with the UNSIGNED content handed in beside it. A NAMED cause and incomplete, never failed: an accuser holding an intact pack reaches this by dropping one file or adding one, with no key at all (proof#147)",
+      "why": "the pack agrees with its own claim everywhere its signature reaches, and does not line up with the UNSIGNED content handed in beside it. A NAMED cause and incomplete, never failed: an accuser holding an intact pack reaches this by dropping one file or adding one, with no key at all",
       "kernel": {
         "status": "verified",
         "okBound": 26,
@@ -179,7 +183,7 @@
       },
       "omissions": [],
       "declaration": {
-        "verdict": "partial",
+        "verdict": "incomplete",
         "present": true,
         "deviations": 0,
         "contentFindings": 1
@@ -190,7 +194,7 @@
         "recordsFailed": 0,
         "recordsUndetermined": 0,
         "causeCount": 1,
-        "declaration": "partial"
+        "declaration": "incomplete"
       }
     },
     {
@@ -250,8 +254,8 @@
       "kernel": { "status": "verified", "okBound": 26, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 26, "present": 26, "missing": 0, "unreadable": 0, "extra": 0 },
       "omissions": [],
-      "declaration": { "verdict": "partial", "present": false, "deviations": 0 },
-      "expect": { "verdict": "verified", "recordsVerified": 26, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0, "declaration": "partial" }
+      "declaration": { "verdict": "incomplete", "present": false, "deviations": 0 },
+      "expect": { "verdict": "verified", "recordsVerified": 26, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0, "declaration": "incomplete" }
     },
     {
       "id": "declaration-unreadable-is-incomplete",
@@ -259,8 +263,8 @@
       "kernel": { "status": "verified", "okBound": 26, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0 },
       "logs": { "expected": 26, "present": 26, "missing": 0, "unreadable": 0, "extra": 0 },
       "omissions": [],
-      "declaration": { "verdict": "partial", "present": true, "deviations": 0 },
-      "expect": { "verdict": "incomplete", "recordsVerified": 26, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0, "declaration": "partial" }
+      "declaration": { "verdict": "incomplete", "present": true, "deviations": 0 },
+      "expect": { "verdict": "incomplete", "recordsVerified": 26, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0, "declaration": "incomplete" }
     },
     {
       "id": "withheld-by-declaration",
@@ -303,8 +307,8 @@
       "kernel": { "status": "verified", "okBound": 2, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "withheldBound": 1, "withheldUnbound": 0 },
       "logs": { "expected": 3, "present": 2, "missing": 0, "unreadable": 0, "extra": 0, "withheld": 1 },
       "omissions": [],
-      "declaration": { "verdict": "partial", "present": true, "deviations": 0, "declaredWithheld": 0 },
-      "expect": { "verdict": "incomplete", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 1, "recordsWithheld": 0, "causeCount": 1, "declaration": "partial" }
+      "declaration": { "verdict": "incomplete", "present": true, "deviations": 0, "declaredWithheld": 0 },
+      "expect": { "verdict": "incomplete", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 1, "recordsWithheld": 0, "causeCount": 1, "declaration": "incomplete" }
     },
     {
       "id": "withheld-and-side-bytes",
@@ -312,8 +316,8 @@
       "kernel": { "status": "verified", "okBound": 2, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "withheldBound": 1, "withheldUnbound": 0 },
       "logs": { "expected": 3, "present": 2, "missing": 0, "unreadable": 0, "extra": 0, "withheld": 1 },
       "omissions": [],
-      "declaration": { "verdict": "partial", "present": true, "deviations": 0, "contentFindings": 1, "declaredWithheld": 1 },
-      "expect": { "verdict": "incomplete", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 0, "recordsWithheld": 1, "causeCount": 1, "declaration": "partial" }
+      "declaration": { "verdict": "incomplete", "present": true, "deviations": 0, "contentFindings": 1, "declaredWithheld": 1 },
+      "expect": { "verdict": "incomplete", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 0, "recordsWithheld": 1, "causeCount": 1, "declaration": "incomplete" }
     },
     {
       "id": "withheld-v5-adapter",
@@ -323,6 +327,79 @@
       "omissions": [],
       "declaration": { "verdict": "verified", "present": true, "deviations": 0, "declaredWithheld": 1 },
       "expect": { "verdict": "incomplete", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 1, "recordsWithheld": 0, "causeCount": 1, "declaration": "verified" }
+    },
+    {
+      "id": "agent-record-failed",
+      "why": "an agent record whose envelope verified and whose content bound, and which breaks its vocabulary: signed and intact, so the pack is failed with the reason kind nonconforming (rule version 9)",
+      "kernel": { "status": "verified", "okBound": 1, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "agentFailed": 1 },
+      "logs": { "expected": 2, "present": 2, "missing": 0, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "expect": { "verdict": "failed", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 1 }
+    },
+    {
+      "id": "agent-failed-beside-a-mismatch",
+      "why": "a proven content mismatch beside an agent record that fails: failed with the reason kind changed, with the agent record still a cause",
+      "kernel": { "status": "verified", "okBound": 1, "okUnknown": 0, "mismatched": 1, "brokenNoContent": 0, "agentFailed": 1 },
+      "logs": { "expected": 3, "present": 3, "missing": 0, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "expect": { "verdict": "failed", "recordsVerified": 2, "recordsFailed": 1, "recordsUndetermined": 0, "causeCount": 1 }
+    },
+    {
+      "id": "agent-failed-beside-a-deviation",
+      "why": "a pack that deviates from its own declaration fails, and the agent record that fails is named beside the deviation",
+      "kernel": { "status": "verified", "okBound": 1, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "agentFailed": 1 },
+      "logs": { "expected": 2, "present": 2, "missing": 0, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "declaration": { "verdict": "failed", "present": true, "deviations": 1 },
+      "expect": { "verdict": "failed", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 2, "declaration": "failed" }
+    },
+    {
+      "id": "agent-failed-in-an-incomplete-bundle",
+      "why": "a bundle status this rule cannot read is not proven, and an agent record beside it that does not follow its vocabulary disproves follows_rules: a disproof outranks anything not proven, so the pack is failed (reason kind nonconforming)",
+      "kernel": { "status": "incomplete", "okBound": 1, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "agentFailed": 1 },
+      "logs": { "expected": 2, "present": 2, "missing": 0, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "expect": { "verdict": "failed", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 1 }
+    },
+    {
+      "id": "agent-failed-beside-missing-bytes",
+      "why": "a disproof outranks anything not proven: a pack holding an agent record that fails and a record whose bytes did not travel is failed with the reason kind nonconforming, with both causes",
+      "kernel": { "status": "verified", "okBound": 1, "okUnknown": 1, "mismatched": 0, "brokenNoContent": 0, "agentFailed": 1 },
+      "logs": { "expected": 3, "present": 2, "missing": 1, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "expect": { "verdict": "failed", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 1, "causeCount": 2 }
+    },
+    {
+      "id": "agent-record-incomplete",
+      "why": "an agent record naming a vocabulary version this reader does not know reads incomplete, which holds the pack at incomplete, never verified and never failed",
+      "kernel": { "status": "verified", "okBound": 1, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "agentIncomplete": 1 },
+      "logs": { "expected": 2, "present": 2, "missing": 0, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "expect": { "verdict": "incomplete", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 1 }
+    },
+    {
+      "id": "agent-closing-two-records-absent",
+      "why": "a closing record that lists two records the pack does not hold reads incomplete with two reasons, and each is a cause: incomplete, never failed, with two causes",
+      "kernel": { "status": "verified", "okBound": 1, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "agentTwoAbsent": 1 },
+      "logs": { "expected": 2, "present": 2, "missing": 0, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "expect": { "verdict": "incomplete", "recordsVerified": 2, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 2 }
+    },
+    {
+      "id": "agent-failed-and-incomplete",
+      "why": "an agent record that fails and one that reads incomplete: failed with the reason kind nonconforming, with one cause each in bundle order",
+      "kernel": { "status": "verified", "okBound": 1, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "agentFailed": 1, "agentIncomplete": 1 },
+      "logs": { "expected": 3, "present": 3, "missing": 0, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "expect": { "verdict": "failed", "recordsVerified": 3, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 2 }
+    },
+    {
+      "id": "agent-findings-only",
+      "why": "a finding is reported beside its record and moves nothing: two verified agent records each with the finding unended leave the pack verified with no cause",
+      "kernel": { "status": "verified", "okBound": 1, "okUnknown": 0, "mismatched": 0, "brokenNoContent": 0, "agentFindings": 2 },
+      "logs": { "expected": 3, "present": 3, "missing": 0, "unreadable": 0, "extra": 0 },
+      "omissions": [],
+      "expect": { "verdict": "verified", "recordsVerified": 3, "recordsFailed": 0, "recordsUndetermined": 0, "causeCount": 0 }
     }
   ]
 }