{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-stop-trusting-a-quorum-certificate-the-attestation-commitment-gap-in-bft-multi-agent-task-ledgers",
  "title": "Where must an instance stop trusting a quorum certificate: the attestation-commitment gap in BFT multi-agent task ledgers",
  "date_of_record": "2026 November 17",
  "scope": "Applies to Byzantine fault-tolerant consensus layers that bind task commitment (an agent promises to perform work) to result attestation (a quorum signs that the work was performed correctly) where the two phases are certified independently. Does not apply to single-phase replicated state machines, nor to systems where task completion and result acceptance share one atomic consensus decision.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-stop-trusting-a-quorum-certificate-the-attestation-commitment-gap-in-bft-multi-agent-task-ledgers.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-stop-trusting-a-quorum-certificate-the-attestation-commitment-gap-in-bft-multi-agent-task-ledgers.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-stop-trusting-a-quorum-certificate-the-attestation-commitment-gap-in-bft-multi-agent-task-ledgers.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1251,
    "python_slice_tokens": 205,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A quorum certificate on a *commitment* proves that 2f+1 replicas recorded the promise. A quorum certificate on an *attestation* proves that 2f+1 replicas observed a claimed result. These are two separate consensus objects. The non-obvious failure is that a valid attestation certificate does not imply that the attesting quorum is the same quorum that committe...",
    "what_was_observed": "During a multi-agent pipeline run (task assignment by a coordinator agent, execution by worker agents, attestation by a rotating verifier set), a worker returned a result with a well-formed attestation QC. The certificate verified against the current epoch's public key set. The coordinator accepted the result and released payment. Two epochs later, the original task commitment was re-delivered by a lagging replica: t...",
    "condition_of_validity": "The gap is reachable when all three hold: 1. Commitment and attestation are certified in separate consensus rounds (two-phase, not fused). 2. Verifier set membership can rotate between the two rounds (view change, epoch boundary, or scheduled rotation). 3. The accepting agent validates each QC against the *current* key set rather than against the key set pin...",
    "decision_boundary": "An agent must reject an attestation QC and re-request attestation when: - The attestation QC's epoch differs from the commitment QC's epoch, **and** no signed digest links the two, **or** - The intersection of the attesting quorum and the committing quorum, restricted to honest members, is fewer than f+1, **or** - The attestation was collected during a view-...",
    "operational_effect": "Enforcing the digest-link check adds one signature verification per accepted task and forces the coordinator to retain commitment QCs until the corresponding attestation is finalized — a bounded memory cost proportional to in-flight tasks. In exchange, it eliminates the view-change attestation window: the coordinator can no longer be induced to accept a resu..."
  },
  "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": "0796f3795408ef80e6bd2257588131872fedde0fe8110e4e7d0c202f81a141ac",
    "verified_classes": [
      "AttestationCommitmentGapError"
    ],
    "verified_functions": [
      "validate_attestation",
      "accept_task_result"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "AttestationCommitmentGapError"
    ],
    "sample_fail_closed_invariants": [
      "attestation digest does not match commitment digest; certificate mismatch"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
