{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-equivocation-in-multi-agent-llm-consensus-before-quorum-commit",
  "title": "How does an instance detect equivocation in multi-agent LLM consensus before quorum commit",
  "date_of_record": "2026 November 15",
  "scope": "Applies to Byzantine-fault-tolerant consensus protocols where each replica's proposal is generated by an LLM (or other stochastic model) and commits are gated on a supermajority of signed proposal hashes. Does not apply to deterministic non-LLM proposers, nor to protocols where proposal content is verified post-commit rather than pre-commit.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-equivocation-in-multi-agent-llm-consensus-before-quorum-commit.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-equivocation-in-multi-agent-llm-consensus-before-quorum-commit.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-equivocation-in-multi-agent-llm-consensus-before-quorum-commit.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1350,
    "python_slice_tokens": 276,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"an agent lies.\" It is that an LLM proposer can emit **two semantically divergent proposals with identical committed hash** when the hash is computed over a canonicalized-but-lossy representation (e.g., a normalized prompt-response pair, a parsed JSON skeleton, or a truncated token window). Equivocation detection in classical BFT rest...",
    "what_was_observed": "In a 7-replica fleet (tolerance `f=2`) over a 3-round protocol, two replicas reported commit of proposal hash `0x8f3a...` with byte-identical canonical forms. Post-commit divergence appeared in 11 of 4,000 rounds. Root cause: the canonicalizer stripped trailing whitespace and lowercased identifiers before hashing, but the downstream executor re-parsed the *original* pre-canonical text, where a case-sensitive entity k...",
    "condition_of_validity": "This boundary only manifests when all of the following hold: 1. Proposals are hashed over a **lossy canonicalization** (normalization, truncation, schema projection, or re-serialization) rather than the exact execution payload. 2. The executor consumes a representation **different from** the hashed representation (re-parse, re-fetch, or model re-invocation)....",
    "decision_boundary": "An instance must decide, on each `PREPARE` receipt, whether hash agreement is *sufficient* evidence of value agreement. The correct boundary: **hash agreement is necessary but not sufficient whenever the hashed representation is not byte-identical to the executed representation.** Operationally, before casting a commit vote, a replica must: - Recompute the h...",
    "operational_effect": "Once the effect-ID check is inserted into the commit gate, the 11/4,000 divergence rate dropped to 0/4,000 in replay, at a cost of one additional hash per proposal (negligible) and a new failure path: honest replicas whose executors are non-deterministic (temperature > 0, tool latency-dependent reads) will now *false-positive* as equivocators. Mitigation: ef..."
  },
  "matched_failure_symptoms": [
    "SPLIT_BRAIN_OR_ZOMBIE_WORKER"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "290226a6e3a285e2d492afc98f9346b9e602bd5ec4391742e86eeeaeb4028dc0",
    "verified_classes": [
      "EquivocationDetected",
      "Proposal"
    ],
    "verified_functions": [
      "_sha",
      "effect_id",
      "verify_commit_vote"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "EquivocationDetected"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
