{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-quorum-intersection-collapse-under-equivocating-proposers-in-bft-multi-agent-decision-quorums",
  "title": "Which invariants prevent quorum intersection collapse under equivocating proposers in BFT multi-agent decision quorums",
  "date_of_record": "2026 November 18",
  "scope": "Applies to leader-based BFT protocols (PBFT, HotStuff, Tendermint-style) where a decision quorum is any set of `2f+1` distinct voting agents out of `3f+1`, and where agents may equivocate (send conflicting proposals/votes to disjoint subsets). Does not apply to crash-fault consensus, to protocols that require `n >= 5f+1` for asynchronous safety, or to weighted-voting schemes without per-agent vote ceilings.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-quorum-intersection-collapse-under-equivocating-proposers-in-bft-multi-agent-decision-quorums.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-quorum-intersection-collapse-under-equivocating-proposers-in-bft-multi-agent-decision-quorums.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-quorum-intersection-collapse-under-equivocating-proposers-in-bft-multi-agent-decision-quorums.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1582,
    "python_slice_tokens": 286,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two properties that are routinely conflated when reasoning about multi-agent decision quorums: 1. **Quorum intersection** — any two quorums of size `2f+1` share at least one honest agent. This is a *set-theoretic* property of the quorum system, provable by counting alone: `|Q1| + |Q2| - n = (2f+1) + (2f+1) - (3f+1) = f+1 > f`. 2. **Quorum intersect...",
    "what_was_observed": "In a 4-agent (`f=1`, `n=4`) decision quorum deployment, a proposer `P` was observed to send proposal `A` to agents `{1,2}` and proposal `A'` to agents `{3}`. Quorum size is `2f+1 = 3`. Agents `1,2` collected a quorum `{1,2,P}` for `A`; agent `3` collected `{3,P,?}` — insufficient alone, but `P` then sent `A'` to agent `2`, who had already voted `A`. Agent `2` was honest but *stateless with respect to prior votes* (a ...",
    "condition_of_validity": "The standard safety argument holds only under the conjunction of: - **(I1) Vote uniqueness:** for each agent and each view `v`, the agent signs at most one value. Equivocation by an agent across views is permitted only if the view number strictly increases *and* the agent's prior vote is included in its new justification (the \"lock\" certificate). - **(I2) Lo...",
    "decision_boundary": "Operationally, treat the following as the go/no-go line: - **Safe to accept a decision** if and only if the quorum certificate's signer set intersects every previously observed conflicting certificate in at least one agent whose vote-once invariant is *externally verifiable* (e.g., via a monotonic view counter in the signed payload, not a local flag). - **Re...",
    "operational_effect": "The practical consequence is that quorum-intersection checkers and formal-verification harnesses that model only set cardinalities will pass while the system is unsafe. This produces a specific, dangerous failure profile: safety violations occur *without* any detectable cardinality anomaly, so monitoring based on \"did we see two quorums that don't overlap\" n..."
  },
  "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": "68cada1f3fbbd2a2abb2a19ea004c3db1ff81334281b1f247b155f8697a32d76",
    "verified_classes": [
      "QuorumIntersectionCollapseError"
    ],
    "verified_functions": [
      "validate_decision_quorum"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "QuorumIntersectionCollapseError"
    ],
    "sample_fail_closed_invariants": [
      "intersection is non-empty but every shared agent equivocated across views; quorum intersection is vacuous",
      "no shared agent advanced view; lock certificate not propagated"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
