{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-byzantine-quorum-intersection-fail-silently-when-the-fault-budget-is-reached-exactly-rather-than-exceeded",
  "title": "Why does an instance of Byzantine quorum intersection fail silently when the fault budget is reached exactly rather than exceeded?",
  "date_of_record": "2026 November 18",
  "scope": "Applies to BFT consensus protocols (PBFT-family, Tendermint-style, HotStuff-style) where quorum intersection is guaranteed by the inequality `3f + 1 ≤ n` and where agents cast signed votes over a decision value. Does not apply to crash-fault-tolerant quorums (`2f + 1 ≤ n`), to leaderless CRDT replication, or to protocols that enforce intersection via threshold signatures with a separately audited threshold.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-byzantine-quorum-intersection-fail-silently-when-the-fault-budget-is-reached-exactly-rather-than-exceeded.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-byzantine-quorum-intersection-fail-silently-when-the-fault-budget-is-reached-exactly-rather-than-exceeded.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-byzantine-quorum-intersection-fail-silently-when-the-fault-budget-is-reached-exactly-rather-than-exceeded.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2093,
    "python_slice_tokens": 348,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *fault-budget exhaustion* (`n = 3f + 1`, the tight case) and *fault-budget slack* (`n > 3f + 1`). Operators routinely treat these as the same regime because both satisfy the quorum-intersection theorem. They are not the same regime operationally. At `n = 3f + 1`, the intersection of any two quorums has size exactly `2f + 1...",
    "what_was_observed": "In a five-replica HotStuff-style deployment (`n = 5`, `f = 1`, `n = 3f + 2`), we observed a two-value split during a leader-change storm. Investigation showed the deployment had been configured with `f = 1` but a *membership view* that transiently contained six replicas during a rolling restart — the new replica joined before the old one was evicted. During that window the effective fault budget was `f' = floor((6 - ...",
    "condition_of_validity": "The quorum-intersection safety guarantee holds if and only if, for every pair of quorums `Q1, Q2` that can be formed, `|Q1 ∩ Q2| > f`. This is a statement about the *configuration actually in force at decision time*, not the configuration in the deployment manifest. The condition fails when: 1. **Membership view drift.** The set of replicas eligible to sign ...",
    "decision_boundary": "The operational rule is: **never run a BFT quorum at `n = 3f + 1` with a fault budget you have not independently verified, and never allow the eligible signer set to exceed the `n` used for quorum sizing for any interval, however brief.** Concretely: - If you cannot prove that the eligible signer set is frozen and equals the `n` in the quorum formula for eve...",
    "operational_effect": "When the boundary is crossed, the observable effect is not a crash, a timeout, or a divergence alarm. It is **two valid-looking decided values with disjoint or minimally-overlapping quorum certificates, each of which passes local verification**. Downstream systems that assume consensus linearizability will reconcile them arbitrarily — by timestamp, by replic..."
  },
  "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": "12c386f7d4a4f0226f3071c8a39480bde74fa5db7d3862fc0880f26427c27e9a",
    "verified_classes": [
      "QuorumIntersectionViolation",
      "QuorumCertificate"
    ],
    "verified_functions": [
      "check_intersection",
      "accept_certificate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "QuorumIntersectionViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
