{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-equivocating-commitment-receipts-as-a-liveness-hazard-rather-than-a-safety-violation-in-byzantine-consensus",
  "title": "In what scenarios must an instance treat equivocating commitment receipts as a liveness hazard rather than a safety violation in Byzantine consensus",
  "date_of_record": "2026 November 18",
  "scope": "Applies to multi-agent task-commitment protocols where agents broadcast signed commitment receipts for shared-state reconciliation under an f < n/3 Byzantine quorum assumption. Does not apply to single-writer replicated logs, to protocols with trusted hardware attestation of broadcast atomicity, or to CRDT-based state where receipts are idempotent and non-authoritative.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-equivocating-commitment-receipts-as-a-liveness-hazard-rather-than-a-safety-violation-in-byzantine-consensus.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-equivocating-commitment-receipts-as-a-liveness-hazard-rather-than-a-safety-violation-in-byzantine-consensus.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-equivocating-commitment-receipts-as-a-liveness-hazard-rather-than-a-safety-violation-in-byzantine-consensus.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1385,
    "python_slice_tokens": 276,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The conventional BFT intuition treats an equivocating replica — one that signs two conflicting receipts for the same task epoch — as a *safety* violation: it proves Byzantine behavior and must be slashed and excluded. This is correct for the *safety* layer (no two honest agents should ever finalize conflicting task assignments). It is dangerously wrong when ...",
    "what_was_observed": "In a 7-agent reconciliation cluster (f=2 tolerated), agent `A3` signed receipt `R1` for task `T` at epoch `e` and receipt `R2` for the same `T` at epoch `e+1` during a view change triggered by leader `L1`'s timeout. `R1` and `R2` carried different assignee fields (`A5` vs `A6`) but identical task payloads and monotonic epoch counters. Three honest agents (`A1`, `A2`, `A4`) held `R1`; three honest agents (`A5`, `A6`, ...",
    "condition_of_validity": "The safety-first treatment of equivocation receipts is valid **only** when the two receipts share an epoch. Formally, define the *equivocation span* as the signed epoch difference Δ = |epoch(R1) − epoch(R2)|. The hard-safety policy is sound iff Δ = 0. When Δ ≥ 1, the receipts are *sequentially* valid — the later supersedes the earlier — and the correct primi...",
    "decision_boundary": "Before excluding a signer, the reconciler must compute: 1. `Δ = epoch(R_late) − epoch(R_early)`. If `Δ == 0`, escalate to safety fault (slash, exclude, freeze task). 2. If `Δ >= 1`, verify that `R_late` is causally descended from `R_early` via the epoch watermark chain (each epoch's commit certificate references the prior epoch's quorum hash). If the chain i...",
    "operational_effect": "After the incident, the reconciler was changed to gate exclusion on `Δ == 0` and to run watermark-chain validation for `Δ >= 1` before any quorum mutation. Replay of the incident trace showed the deadlock would have resolved in 2 reconciliation rounds (~400ms) instead of 41 minutes, with zero safety violations. The operational lesson: in multi-agent commitme..."
  },
  "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": "cbb52c110141ca28ea33b30dc2c4b4b3212f30bfad77c57af897eedc1a13fc72",
    "verified_classes": [
      "EquivocationSpanError"
    ],
    "verified_functions": [
      "classify_receipt_pair",
      "reconcile"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "EquivocationSpanError"
    ],
    "sample_fail_closed_invariants": [
      "receipts reference different tasks"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
