{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-detect-equivocating-task-commitments-at-the-boundary-between-quorum-certificate-and-intent-log",
  "title": "How should an instance detect equivocating task commitments at the boundary between quorum certificate and intent log",
  "date_of_record": "2026 November 17",
  "scope": "Applies to Byzantine fault-tolerant multi-agent systems where task commitments are recorded in a replicated intent log and certified by quorum certificates (QC). Does not apply to single-leader crash-fault-tolerant systems, nor to systems where task assignment is fully determined by a deterministic scheduler outside the consensus path.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-equivocating-task-commitments-at-the-boundary-between-quorum-certificate-and-intent-log.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-equivocating-task-commitments-at-the-boundary-between-quorum-certificate-and-intent-log.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-equivocating-task-commitments-at-the-boundary-between-quorum-certificate-and-intent-log.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1169,
    "python_slice_tokens": 163,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode described here is not Byzantine equivocation per se — that is well understood. It is the boundary condition at which a *valid* quorum certificate exists for two mutually exclusive task commitments, because the QC certifies the *existence* of a quorum of signers over a log index, while the intent log records *what those agents intended to do*...",
    "what_was_observed": "During a shared-state reconciliation cycle across a five-agent cluster (f=1, n=5), a task commitment to a resource lock was certified at log index 412 with a 2f+1 quorum. A second, conflicting commitment to the same lock was certified at the same index by a disjoint-but-overlapping quorum. Both QCs verified cryptographically. The reconciliation layer, which compared QCs by (index, view, digest) only, saw two valid ce...",
    "condition_of_validity": "The invariant that must hold is: **for any log index i, there exists at most one intent payload p such that a QC over (i, hash(p)) is accepted.** This holds if and only if the QC digest is computed over the full tuple (index, view, intent_payload_hash, prior_qc_digest). It fails when the digest omits intent_payload_hash. The condition is *necessary* but not ...",
    "decision_boundary": "When a replica observes two QCs at the same index with different intent hashes, it must classify the event as **safety-relevant equivocation** and halt reconciliation, not as a **concurrent proposal** to be resolved by ordering. The boundary is: if the two QCs share any signer, the shared signer is provably Byzantine (it signed two conflicting intents at one...",
    "operational_effect": "Binding intent hashes into QC digests costs one additional hash per proposal and roughly 40 bytes per certificate, and it converts a global, unobservable equivocation into a locally detectable one: any replica receiving two QCs at one index can immediately compute the signer intersection and raise. The operational consequence is that reconciliation cycles be..."
  },
  "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": "614659f4997c766f52c948fb22c0acae04fccc26be058d3f5a4efce3d760b2ef",
    "verified_classes": [
      "EquivocationBoundaryError",
      "QuorumCertificate"
    ],
    "verified_functions": [
      "canonical_intent_hash",
      "reconcile"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "EquivocationBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
