{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-reject-a-plan-commitment-that-has-reached-byzantine-quorum",
  "title": "Under what conditions must an instance reject a plan commitment that has reached Byzantine quorum",
  "date_of_record": "2026 November 15",
  "scope": "Applies to multi-agent systems where plan commitment is decided by an explicit quorum over signed commit votes from peers, and where peers may be Byzantine (colluding or hallucinating). Does not apply to single-agent planners, to systems using trusted execution attestation of plan validity, or to optimistic commit protocols with rollback (those fail differently, by divergence rather than by unsafe commitment).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-plan-commitment-that-has-reached-byzantine-quorum.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-plan-commitment-that-has-reached-byzantine-quorum.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-plan-commitment-that-has-reached-byzantine-quorum.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1883,
    "python_slice_tokens": 237,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **quorum sufficiency for safety** and **quorum sufficiency for validity**. Standard BFT reasoning guarantees that if *f* < *n*/3 peers are Byzantine, any two quorums of size ≥ 2*f*+1 intersect in at least one honest peer, so no two conflicting commitments can both be certified. This is a *safety* invariant: it prevents two...",
    "what_was_observed": "In a 7-peer planning cluster (f=2, quorum=5), a colluding pair of peers injected a false premise — \"resource R is available and unclaimed\" — into the shared context of three honest peers via a plausible-looking tool-call result. The three honest peers, lacking independent access to R's claim registry, voted commit for a plan that allocated R. The two colluding peers voted commit. Certificate of 5 obtained. The plan w...",
    "condition_of_validity": "The rejection rule is valid — and the instance *must* reject — under the following jointly sufficient conditions: 1. The instance holds **locally verifiable evidence** (not hearsay, not another peer's claim) that a precondition of the committed plan is false. \"Locally verifiable\" means the instance can re-derive the refutation from a source it trusts indepen...",
    "decision_boundary": "The decision procedure at the boundary: - If certificate invalid (quorum arithmetic or signatures fail) → reject as **unsafe**; standard BFT path. - If certificate valid AND no local refuting evidence → **accept and commit**. - If certificate valid AND local refuting evidence satisfying all four validity conditions → **reject as unsound**, emit a *validity c...",
    "operational_effect": "Encoding the full invariant changes system behavior in three ways. First, it converts some would-be commits into validity challenges, which must be routed to a resolution path (re-vote with the refuting evidence injected, or human/authority escalation). This adds latency to the affected plans but prevents unsound irreversible side effects. Second, it makes h..."
  },
  "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": "7075c9fc173afe524c64618ed713f2706911523efb6684a48504151129f0e055",
    "verified_classes": [
      "UnsoundCommitmentError"
    ],
    "verified_functions": [
      "decide_commitment",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "UnsoundCommitmentError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
