{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-commitment-equivocation-is-latent-in-a-byzantine-fault-tolerant-multi-agent-quorum",
  "title": "What structural signals indicate commitment equivocation is latent in a Byzantine fault-tolerant multi-agent quorum",
  "date_of_record": "2026 November 16",
  "scope": "Applies to BFT consensus protocols where agents commit to tasks via quorum certificates (QC) over signed task-assignment messages, and where the safety property is \"no two correct agents commit to conflicting assignments.\" Does not apply to crash-fault-tolerant replication, nor to BFT protocols where the commit rule requires a full round-trip of all-to-all acknowledgements (e.g., pure PBFT without view-change pipelining).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-commitment-equivocation-is-latent-in-a-byzantine-fault-tolerant-multi-agent-quorum.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-commitment-equivocation-is-latent-in-a-byzantine-fault-tolerant-multi-agent-quorum.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-commitment-equivocation-is-latent-in-a-byzantine-fault-tolerant-multi-agent-quorum.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1583,
    "python_slice_tokens": 162,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **quorum intersection** (a set-theoretic property of the voting set) and **commitment intersection** (an operational property of the messages that agents actually emit and persist). In a 3f+1 BFT system, any two quorums of size 2f+1 intersect in at least f+1 nodes, guaranteeing at least one correct node is in both. Thi...",
    "what_was_observed": "During a multi-agent task-commitment workload (N=7 agents, f=2, task-assignment messages carrying a `(task_id, epoch, assignment_set)` tuple signed per-agent), we observed the following sequence across a view change: 1. In view v, a leader proposed assignment A to task T. Quorum Q1 (5 agents) signed. All 5 persisted the QC locally and emitted a `COMMIT(T, A, v)` record. 2. The leader for view v+1 was Byzantine and pr...",
    "condition_of_validity": "The standard safety argument for BFT commitment is valid only when: - **Retention ≥ view-change depth.** Every correct agent retains its commit records for at least as many views as the maximum depth of a valid view-change certificate it might be asked to honor. If retention < depth, a correct agent can be a \"correct amnesiac\" in the intersection — formally ...",
    "decision_boundary": "The operational decision is: **treat the ratio (retention window / observed view-change depth) as a safety invariant, not a tuning parameter.** When observed view-change depth approaches the retention window, the correct action is to halt new task commitments and force a state-sync of commit records from a quorum of peers before resuming — not to increase th...",
    "operational_effect": "The effect of crossing this boundary is silent double-commitment: two valid QCs over conflicting assignments, both verifiable, both persisted, with no correct agent able to prove the other is invalid. Downstream task execution forks. Reconciliation requires an out-of-band merge protocol that the BFT layer was supposed to make unnecessary. In our workload, th..."
  },
  "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": "6cc67f71796cdfc42d7865a85a66974dda8830ef8b5edd6c7b7d890640a53d44",
    "verified_classes": [
      "CommitmentIntersectionError"
    ],
    "verified_functions": [
      "check_commitment_safety",
      "commit_task"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CommitmentIntersectionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
