{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-commit-the-quorum-intersection-blind-spot-in-bft-task-commitment-under-partial-synchrony",
  "title": "When must an instance refuse to commit: the Quorum-Intersection Blind Spot in BFT task commitment under partial synchrony",
  "date_of_record": "2026 November 17",
  "scope": "Applies to leader-based BFT consensus protocols (PBFT/Tendermint/HotStuff lineage) where a replica must decide whether a prepared value is safe to commit after a view change, given an `f`-tolerance assumption and a network that is merely partially synchronous. Does not apply to crash-fault-tolerant protocols, to protocols with trusted hardware attestation on every message, or to the case where the client itself is part of the quorum.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-commit-the-quorum-intersection-blind-spot-in-bft-task-commitment-under-partial-synchrony.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-commit-the-quorum-intersection-blind-spot-in-bft-task-commitment-under-partial-synchrony.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-commit-the-quorum-intersection-blind-spot-in-bft-task-commitment-under-partial-synchrony.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1591,
    "python_slice_tokens": 314,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters operationally is between **quorum intersection** (a set-theoretic property: any two quorums of size `2f+1` out of `3f+1` share at least one correct replica) and **quorum *observability*** (an epistemic property: the new leader can actually *learn* what the intersecting replica knew). These are routinely conflated. Intersection gu...",
    "what_was_observed": "In a five-replica deployment (`f = 1`, quorum `3`), a leader change was triggered by a slow primary. The new leader gathered three `VIEW-CHANGE` messages within 800 ms and — seeing no `prepared` certificate at sequence 412 — proposed a fresh block `B'`. Replicas `R2` and `R4` accepted and committed `B'`. Replica `R3` had, in the prior view, received `PREPARE` messages from `R1` and `R2` for block `B` at sequence 412 ...",
    "condition_of_validity": "The `2f+1` `VIEW-CHANGE` rule is valid only under the conjunction: 1. **Strong synchrony during view change.** Every correct replica's `VIEW-CHANGE` arrives within the leader's collection window `Δ_collect`. This is *not* implied by partial synchrony; partial synchrony only guarantees eventual delivery, not bounded delivery during a specific window. 2. **Or:...",
    "decision_boundary": "A replica (or the leader on its behalf) must **refuse to treat a `2f+1` `VIEW-CHANGE` quorum as sufficient** whenever any of the following hold: - The collection window `Δ_collect` was chosen by timeout rather than by an observed lower bound on delivery latency. - The set of `VIEW-CHANGE` senders is not known to intersect every quorum that could have prepare...",
    "operational_effect": "The practical consequence is that view-change timeouts must be treated as **safety parameters, not performance parameters**. Tuning `Δ_collect` downward to reduce failover latency directly shrinks the margin by which the `2f+1` shortcut is sound. In the observed deployment, reducing `Δ_collect` from 2 s to 800 ms to meet an SLO was the proximate cause of the..."
  },
  "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": "2022f2d9b54fa0afc5549a63e43e7e5430efb0201ccd16205c2fe114c830dc7b",
    "verified_classes": [
      "QuorumObservabilityError"
    ],
    "verified_functions": [
      "assert_commit_safe",
      "leader_commit"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "QuorumObservabilityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
