{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-commits-a-plan-whose-quorum-certificate-is-valid-but-whose-view-change-proof-is-stale",
  "title": "What happens when an instance commits a plan whose quorum certificate is valid but whose view-change proof is stale",
  "date_of_record": "2026 November 18",
  "scope": "Applies to BFT consensus protocols used to commit multi-agent plans where commitment is certified by a quorum certificate (QC) and liveness is preserved across view changes via a view-change proof (VCP / new-view certificate). Does not apply to single-leader crash-fault-tolerant replication, nor to protocols where plan commitment is decided by an external coordinator rather than by quorum intersection.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-commits-a-plan-whose-quorum-certificate-is-valid-but-whose-view-change-proof-is-stale.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-commits-a-plan-whose-quorum-certificate-is-valid-but-whose-view-change-proof-is-stale.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-commits-a-plan-whose-quorum-certificate-is-valid-but-whose-view-change-proof-is-stale.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2018,
    "python_slice_tokens": 326,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct notions of \"the plan is committed\": 1. **Certificate-valid commitment** — a plan block carries a QC formed by a threshold of signatures from the current view's validator set. This is a statement about *who signed*, not about *what the signers knew*. 2. **Safety-preserving commitment** — a plan block is committed only if no conflicting ...",
    "what_was_observed": "In a 7-validator deployment (f = 2, quorum = 5) running a plan-commitment layer over a HotStuff-style pipeline, the following sequence was reproduced deterministically: - View `v`: leader `L_v` proposes plan `P1` (assign agents A, B to task T). Validators `{1,2,3,4,5}` sign; QC(P1) forms. The QC is gossiped but reaches only `{1,2,3,4}` before a network partition isolates `{5,6,7}`. - View `v+1`: leader `L_{v+1}` is v...",
    "condition_of_validity": "The safety argument for view-change commitment holds **only if** the VCP's `highQC` field is the true maximum over the QCs known to *every* validator in the VCP quorum, and the VCP quorum intersects every prior QC quorum. The first condition is the one that silently fails. It requires: - Validators must report their *locally highest* QC, not a QC they believ...",
    "decision_boundary": "An operator or agent must treat a plan as committed only when **both** of the following hold: - The plan block carries a QC from a quorum of the current view's validator set, **and** - The view that produced the QC was entered via a VCP whose `highQC` is at least as high as every QC observed by any validator in the VCP quorum, verified by requiring each VCP ...",
    "operational_effect": "The practical consequence is that multi-agent plan commitment cannot rely on QC validity alone. It must additionally enforce *VCP freshness* as a first-class invariant: every VCP signer discloses its highest known QC hash, the leader computes the maximum over the full quorum, and any signer whose disclosure arrives after the VCP is formed forces the VCP to b..."
  },
  "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": "4c41da4eea6c42f57e50cbbf4eb96449211447bd113a4f48a74e2c829f001b11",
    "verified_classes": [
      "StaleViewChangeProofError",
      "QC",
      "VCPDisclosure",
      "ViewChangeProof"
    ],
    "verified_functions": [
      "verify_vcp_freshness",
      "commit_plan"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "StaleViewChangeProofError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
