{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-byzantine-equivocation-boundary-in-multi-agent-task-commitment-before-shared-state-divergence",
  "title": "What structural signals indicate a Byzantine equivocation boundary in multi-agent task commitment before shared-state divergence",
  "date_of_record": "2026 November 15",
  "scope": "Applies to quorum-based BFT consensus layers (PBFT-style, Tendermint-style, or HotStuff-style) coordinating ≥4 agents over a shared task-commitment ledger where agents may be adversarial or crash-faulty. Does not apply to single-leader crash-only replication (Raft/Paxos), nor to systems with a trusted coordinator or hardware-attested enclaves that eliminate equivocation at the transport layer.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-byzantine-equivocation-boundary-in-multi-agent-task-commitment-before-shared-state-divergence.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-byzantine-equivocation-boundary-in-multi-agent-task-commitment-before-shared-state-divergence.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-byzantine-equivocation-boundary-in-multi-agent-task-commitment-before-shared-state-divergence.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1252,
    "python_slice_tokens": 302,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters operationally is between *fault-tolerant quorum progress* and *equivocation-induced view divergence*. A BFT protocol tolerates up to `f = (n-1)/3` Byzantine replicas and continues to commit. But there is a narrower, non-obvious boundary: an equivocating primary can emit **two structurally valid but mutually inconsistent proposals...",
    "what_was_observed": "In a 7-replica task-commitment deployment (f=2), a Byzantine primary at view `v` sent proposal `P_a` (task commit set `{t1,t2}`) to replicas `{1,2,3,4}` and proposal `P_b` (task commit set `{t1,t3}`) to replicas `{4,5,6}`. Replica 4, receiving both, treated the second as a duplicate-view anomaly and dropped it under a \"first proposal wins per view\" rule. Result: quorum `{1,2,3,4}` prepared `P_a`; quorum `{4,5,6}` pre...",
    "condition_of_validity": "This boundary is only reachable when all of the following hold: - `n ≥ 4` and `f ≥ 1`, with the primary selected deterministically per view. - Replicas sign prepare votes *before* cross-checking against a second proposal for the same `(view, seq)` — i.e., signature collection is decoupled from equivocation detection. - The dedup/first-wins rule executes at t...",
    "decision_boundary": "The operational rule: **treat any pair of quorum certificates at the same `(view, seq)` whose signer-set intersection is `< f+1` as an equivocation event, regardless of individual certificate validity.** Do not wait for a timeout or a view change — timeouts are liveness signals and will *mask* this as a slow primary. The correct action is to freeze commitmen...",
    "operational_effect": "Without this rule, the system exhibits *silent fork*: two valid task-commitment frontiers persist, downstream agents act on inconsistent shared state, and the divergence surfaces later as an unexplained application-level conflict rather than a consensus fault. With the rule, equivocation is caught at vote-collection time, the offending primary is slashed or ..."
  },
  "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": "fd04ad8ec41959a9000947da6ce46cff8ce23d0eb981db405e8b49c472015b66",
    "verified_classes": [
      "EquivocationBoundaryError",
      "QuorumCertificate"
    ],
    "verified_functions": [
      "check_certificate_overlap",
      "commit_task_subtree"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "EquivocationBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
