{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-quorum-collapse-when-heterogeneous-llm-agents-disagree-about-the-meaning-of-a-vote",
  "title": "Which invariants prevent quorum collapse when heterogeneous LLM agents disagree about the meaning of a vote",
  "date_of_record": "2026 November 16",
  "scope": "Applies to BFT consensus protocols (PBFT, Tendermint-style, HotStuff) where voting members are LLM agents with differing model families, tokenizers, and system prompts, and where the vote payload is natural-language or structured JSON emitted by a generative model. Does not apply to homogeneous, deterministic, or single-model deployments where vote serialization is byte-identical across replicas.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-quorum-collapse-when-heterogeneous-llm-agents-disagree-about-the-meaning-of-a-vote.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-quorum-collapse-when-heterogeneous-llm-agents-disagree-about-the-meaning-of-a-vote.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-quorum-collapse-when-heterogeneous-llm-agents-disagree-about-the-meaning-of-a-vote.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1621,
    "python_slice_tokens": 264,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Classical BFT safety proofs assume that a *vote* is an atomic, hashable, semantically unambiguous object: a replica signs `(view, seq, digest)` and the digest binds the replica to exactly one interpretation. The proof of quorum intersection depends only on the *set* of signers and the *uniqueness* of what each signature attests to. Heterogeneous LLM agents b...",
    "what_was_observed": "In a 7-replica deployment (f=2, tolerance 2 Byzantine) spanning three model families, a view-change was triggered after a leader emitted a proposal whose `value` field was a JSON object. Six honest replicas prepared on it. During the prepare phase, three distinct byte-level digests were recorded for what all six agents reported as \"the same proposal\": - Two agents (family A) emitted compact JSON with keys in insertio...",
    "condition_of_validity": "The quorum-collapse failure requires all of the following to hold simultaneously: 1. Vote payloads are produced by generative models rather than by a deterministic serializer owned by the protocol. 2. The digest is computed over model-emitted bytes rather than over a canonical form the protocol itself constructs. 3. At least one agent's emission path is loss...",
    "decision_boundary": "The boundary is not \"use deterministic models\" (impossible with heterogeneous LLM agents) nor \"add more replicas\" (does not help; the failure is per-digest, not per-count). The operative decision is: - **If** the protocol can own canonicalization — i.e., agents submit *structured intent* (a proposal identifier plus field values) and the protocol serializes, ...",
    "operational_effect": "After adopting protocol-owned canonicalization plus an explicit equivalence gate, the cluster's view-change rate dropped and, critically, the commit rule gained a *fail-closed* property: any payload that could not be normalized was rejected before signature collection, converting a silent safety hazard into a loud, attributable liveness event. The trade-off ..."
  },
  "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": "df76597ede12237fcf82c25aee2750fe28c17c7fb2d93ed9b15c930f543c0f5f",
    "verified_classes": [
      "QuorumCollapseError",
      "SemanticDriftError"
    ],
    "verified_functions": [
      "canonicalize",
      "digest",
      "verify_certificate",
      "commit_round"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "QuorumCollapseError",
      "SemanticDriftError"
    ],
    "sample_fail_closed_invariants": [
      "empty proposal cannot anchor a certificate"
    ],
    "stdlib_dependencies": [
      "hashlib",
      "json",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
