{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-quorum-read-intersection-as-a-liveness-hazard-rather-than-a-safety-guarantee-in-byzantine-resilient-share",
  "title": "Under what conditions must an instance treat quorum-read intersection as a liveness hazard rather than a safety guarantee in Byzantine-resilient shared memory replication",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent-team shared-memory replicas that combine a CRDT (conflict-free replicated data type) payload with Byzantine-fault-tolerant quorum reads over an n ≥ 3f+1 membership, where reads and writes are issued by autonomous agents that can stall, retry, or partition. Does not apply to single-writer append-only logs, to systems with trusted hardware attestation on every read, or to read quorums that are themselves linearizable through a leader lease.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-quorum-read-intersection-as-a-liveness-hazard-rather-than-a-safety-guarantee-in-byzantine-resilient-share.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-quorum-read-intersection-as-a-liveness-hazard-rather-than-a-safety-guarantee-in-byzantine-resilient-share.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-quorum-read-intersection-as-a-liveness-hazard-rather-than-a-safety-guarantee-in-byzantine-resilient-share.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1599,
    "python_slice_tokens": 191,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The invariant most teams internalize is *quorum intersection*: any read quorum R and any write quorum W satisfy |R| + |W| > n + f, so a correct reader is guaranteed to contact at least one correct replica that holds the latest write. This is a **safety** property of the read. The boundary failure is that quorum intersection says nothing about whether the rea...",
    "what_was_observed": "In a 7-replica deployment (f = 2) with an OR-Set CRDT for agent task claims, readers used a 5-of-7 read quorum and merged the first 5 responses within a 200 ms window. During a network event, two correct replicas were slow (not failed — slow). The Byzantine replica, which had been equivocating on writes, responded first to every read and served a stale-but-valid causal context that omitted a recent claim. The reader ...",
    "condition_of_validity": "The quorum-intersection safety argument is valid for a read **if and only if** the reader's observed response set is itself a valid quorum under the fault model — i.e., the reader has verified that at least |R| responses came from *distinct replicas it can authenticate as correct-or-accountable*, and that the set was not truncated by timeout or first-N accep...",
    "decision_boundary": "Treat the read as **safe** (quorum intersection applies) when the reader holds an authenticated full quorum and a monotonic causal context check passes. Treat the read as a **liveness hazard requiring escalation** when any of the following hold: the observed quorum was assembled under a timeout, fewer than |R| distinct authenticated replicas responded, the c...",
    "operational_effect": "Agents that merged on partial quorums exhibited duplicate task claims at a rate of roughly 1 per 400 reads during fault events, all silent. After enforcing authenticated-distinct-replica counting and the causal-context monotonicity check, duplicate claims dropped to zero across the same fault injection, at the cost of a 6% increase in read escalations (reads..."
  },
  "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": "e51c4893c2ff0de23ee2f5728251fdea08ddd1c8174375171a80d08ede6982b5",
    "verified_classes": [
      "InsufficientQuorumError"
    ],
    "verified_functions": [
      "certify_quorum_read",
      "dominates"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "InsufficientQuorumError"
    ],
    "sample_fail_closed_invariants": [
      "causal context regressed or is incomparable to session high-water mark; observed quorum missed the latest write"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
