{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-byzantine-equivocation-in-multi-agent-task-commitment-a-boundary-case-quorum-certificates-that-validate-while-the-com",
  "title": "What structural signals indicate Byzantine equivocation in multi-agent task commitment (a boundary case: quorum certificates that validate while the committed state diverges)",
  "date_of_record": "2026 November 15",
  "scope": "Applies to BFT consensus protocols that commit multi-agent task assignments and reconcile shared state via threshold-signed quorum certificates (QC), where a QC is treated as sufficient proof of commitment. Does not apply to single-leader crash-fault-tolerant replication, nor to systems that require a full re-execution of the task log before honoring any committed assignment.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-byzantine-equivocation-in-multi-agent-task-commitment-a-boundary-case-quorum-certificates-that-validate-while-the-com.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-byzantine-equivocation-in-multi-agent-task-commitment-a-boundary-case-quorum-certificates-that-validate-while-the-com.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-byzantine-equivocation-in-multi-agent-task-commitment-a-boundary-case-quorum-certificates-that-validate-while-the-com.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1360,
    "python_slice_tokens": 193,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters operationally is between **certificate validity** and **commitment uniqueness**. A threshold signature over a block proves that a quorum of agents *signed* a view of state. It does not, by itself, prove that this is the *only* state a quorum will ever sign. When a Byzantine agent controls the message ordering seen by different ho...",
    "what_was_observed": "During a multi-agent task-commitment run, two agents were each assigned the same exclusive resource lock under two different view numbers. Both assignments carried valid QCs. Reconciliation logic, which trusted the QC as authoritative, applied them in arrival order, and the second application silently overwrote the first — leaving one agent executing a task whose commitment had been revoked without notification. The ...",
    "condition_of_validity": "This failure mode is reachable only when *all* of the following hold simultaneously: 1. The protocol accepts a single QC as sufficient proof of commitment without requiring a **commit certificate chain** back to a common ancestor. 2. The reconciliation path applies committed state in arrival order rather than verifying that the new commitment extends, rather...",
    "decision_boundary": "The operative question is not \"does the QC verify\" but **\"does the new commitment's ancestry contain the current commitment.\"** A correct reconciler must: - Reject any commitment whose parent hash does not match the current head, regardless of QC validity. - Require that view numbers be strictly monotonic per agent's local history; a lower view number is a f...",
    "operational_effect": "When the boundary is crossed, the system exhibits **silent double-commitment**: two agents believe they hold the same exclusive task, the shared state reflects only the later write, and the earlier agent continues executing against a commitment the network has effectively revoked. The failure is not a crash and produces no error — it produces divergence that..."
  },
  "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": "cdf6b7381e8ca7b44cd2a1342771e89a119cff378cf1e4ca492b13f58832e76d",
    "verified_classes": [
      "EquivocationBoundaryError"
    ],
    "verified_functions": [
      "reconcile_commitment"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "EquivocationBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
