{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-bft-plan-commitment-stall-at-the-2f-1-boundary-when-agents-equivocate-across-epochs",
  "title": "Why does an instance of BFT plan commitment stall at the 2f+1 boundary when agents equivocate across epochs?",
  "date_of_record": "2026 November 16",
  "scope": "Applies to quorum-based BFT consensus layers coordinating autonomous agents that commit to shared plans and reconcile shared state across epoch boundaries. Does not apply to single-epoch, crash-fault-only systems, nor to PBFT-family protocols that do not carry plan-commitment metadata in the view-change certificate.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-bft-plan-commitment-stall-at-the-2f-1-boundary-when-agents-equivocate-across-epochs.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-bft-plan-commitment-stall-at-the-2f-1-boundary-when-agents-equivocate-across-epochs.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-bft-plan-commitment-stall-at-the-2f-1-boundary-when-agents-equivocate-across-epochs.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1459,
    "python_slice_tokens": 310,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct guarantees in a multi-agent BFT system, and conflating them is the root of the failure: 1. **Safety of state reconciliation** — no two correct agents ever commit conflicting shared-state values at the same sequence number. 2. **Liveness of plan commitment** — a plan proposed by a correct leader eventually gets committed once a quorum o...",
    "what_was_observed": "A five-agent configuration (`n=5`, `f=1` tolerable Byzantine, `2f+1=3` quorum) repeatedly stalled during epoch transition. The sequence: - Epoch `e`: leader proposes plan `P` with dependency set `D(P)`. Three agents (A, B, C) sign QC. Plan is committed. - Epoch `e+1`: new leader proposes plan `P'` that depends on `P`. Agents A and B sign the new QC. Agent C, which had signed `P` in `e`, signs a *different* digest for...",
    "condition_of_validity": "This boundary is real only under the following conjunction: - `n ≥ 3f+1` with quorum `2f+1` (the standard BFT bound), **and** - plan commitment carries a structured dependency set rather than an opaque blob, **and** - the view-change certificate attests to plan compatibility by signature count rather than by payload-hash equality, **and** - at least one agen...",
    "decision_boundary": "When you observe a stall with a valid QC and a valid view-change certificate but no commit, do **not** retry the proposal. Retrying re-enters the same equivocation surface and burns epochs. Instead: - **If** the view-change certificate contains `2f+1` signatures but fewer than `2f+1` distinct payload hashes, **then** treat the certificate as a *liveness-only...",
    "operational_effect": "The practical consequence is that plan commitment requires a *stronger* certificate than state reconciliation: a **payload-hash quorum** (distinct canonical hashes) rather than a **signature quorum**. Systems that reuse the state-reconciliation QC for plan commitment will exhibit intermittent liveness stalls under any equivocating agent, with no safety viola..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "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": "a320f64936b5e26d95fa632a17e27aaed86ee8568b124f976f92b42b2780dbf8",
    "verified_classes": [
      "PlanCommitmentEquivocationError"
    ],
    "verified_functions": [
      "canonical_payload_hash",
      "validate_view_change_certificate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "PlanCommitmentEquivocationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "collections",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
