{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a-speculative-agent-plan-whose-byzantine-quorum-check-passes-on-the-plan-hash-but-fails-on-the-pre-state-bin",
  "title": "In what scenarios must an instance reject a speculative agent plan whose Byzantine quorum check passes on the plan hash but fails on the pre-state binding",
  "date_of_record": "2026 November 15",
  "scope": "Applies to multi-agent orchestration layers where a planner agent emits a speculative plan, a set of verifier agents attest to it via lightweight Byzantine quorum (typically 2f+1 of 3f+1), and a committer executes side effects only after quorum. Does not apply to single-writer systems, to plans with no external side effects, or to quorums that already carry full state witnesses rather than hash attestations.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-speculative-agent-plan-whose-byzantine-quorum-check-passes-on-the-plan-hash-but-fails-on-the-pre-state-bin.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-speculative-agent-plan-whose-byzantine-quorum-check-passes-on-the-plan-hash-but-fails-on-the-pre-state-bin.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-speculative-agent-plan-whose-byzantine-quorum-check-passes-on-the-plan-hash-but-fails-on-the-pre-state-bin.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1644,
    "python_slice_tokens": 268,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A Byzantine quorum check answers exactly one question: *did at least 2f+1 verifiers sign the same 32-byte digest?* It does **not** answer whether the digest was computed over the object the committer is about to mutate. Speculative plans are constructed against a *read snapshot* of world state; by the time quorum completes, that snapshot may be stale. The fa...",
    "what_was_observed": "During a rolling deployment of a plan-verification tier, a planner emitted a plan to transfer a shard lease from node `A` to node `B`. The plan body included `expected_lease_epoch: 4417` and `source_resource_version: 99213`. Three of four verifiers signed the plan hash within 40 ms. Quorum was reached. The committer began execution 610 ms later. In that 610 ms window, an unrelated rebalancer on node `A` renewed the l...",
    "condition_of_validity": "The quorum result is valid evidence for commit **only if** all of the following hold: 1. The plan hash covers every field the committer will use as a write precondition (epochs, versions, tokens), not merely the intended effect. 2. The committer's write is a compare-and-swap against those exact fields, evaluated atomically at commit time — not a read-then-wr...",
    "decision_boundary": "Reject the plan at commit time (do not execute, re-plan) when **any** of: - The CAS against the plan's embedded preconditions returns a mismatch, even though quorum passed. Quorum passing is not a reason to force the write; it is a reason to *attempt* the CAS. - The plan's preconditions reference a field that the commit path does not actually guard on. This ...",
    "operational_effect": "The correction is to move the binding from the verifier tier to the commit tier. Verifiers keep doing what they are cheap at — quorum over plan structure, catching malformed or maliciously divergent plans. The committer independently enforces the pre-state binding via CAS, and treats a CAS failure as a *normal, expected* outcome that triggers silent re-plann..."
  },
  "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": "efa839f0059edc9fdd2bb025fd12d6bf9afed20a98b1c581862a6380f493ec93",
    "verified_classes": [
      "StalePreconditionError",
      "Plan",
      "WorldState"
    ],
    "verified_functions": [
      "verify_and_commit"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "StalePreconditionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
