{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-commits-a-task-but-its-result-attestation-quorum-is-formed-from-a-different-view-than-the-commitment-quorum",
  "title": "What happens when an instance commits a task but its result-attestation quorum is formed from a different view than the commitment quorum",
  "date_of_record": "2026 November 10",
  "scope": "Applies to BFT consensus protocols that separate *task commitment* (agreement that an agent will execute a task) from *result agreement* (agreement on the output of that task) across potentially different quorums and views. Does not apply to single-phase protocols where commitment and result are decided in one consensus instance, nor to protocols with a global serialization point that forces both quorums to coincide.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-commits-a-task-but-its-result-attestation-quorum-is-formed-from-a-different-view-than-the-commitment-quorum.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-commits-a-task-but-its-result-attestation-quorum-is-formed-from-a-different-view-than-the-commitment-quorum.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-commits-a-task-but-its-result-attestation-quorum-is-formed-from-a-different-view-than-the-commitment-quorum.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1914,
    "python_slice_tokens": 398,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "In a two-phase BFT commitment protocol (commit-then-attest), operators commonly assume that a quorum intersection argument covers both phases: if 2f+1 of 3f+1 replicas committed the task, and 2f+1 attested the result, then at least f+1 honest replicas participated in both, so the result is bound to the commitment. This reasoning is sound **only if both quoru...",
    "what_was_observed": "In a 7-replica (f=2) deployment with view-change support and periodic membership rotation, the following sequence occurred: 1. View 12: leader L12 proposed task T. Commitment certificate C_T was formed with quorum {R0, R1, R2, R3, R4} (5 of 7). Agent R2 was assigned execution. 2. R2 executed T and produced result r. Before R2 could broadcast its attestation, a network partition isolated {R2, R5, R6} from {R0, R1, R3,...",
    "condition_of_validity": "The composition invariant \"one committed task ⇒ at most one committed result\" holds if and only if at least one of the following is enforced: - **Epoch binding:** the result certificate must embed and be validated against the membership epoch (and view) of the commitment certificate, and attestations from a different epoch are rejected unless accompanied by ...",
    "decision_boundary": "Do **not** treat a two-phase commit/attest protocol as safe across view changes unless result certificates are cryptographically chained to commitment certificates. Specifically: - If your attestation verifier validates quorum membership against the epoch embedded in the *attestation* rather than the epoch of the *commitment*, you have this bug. This is the ...",
    "operational_effect": "The observed effect is **duplicate finalized results with divergent values** for a single committed task, with no protocol-level alarm. Downstream consumers that key on task ID see two results and must resolve by certificate recency — which is wrong, because the earlier certificate may be the correct one and the later one a re-assignment artifact. In the obs..."
  },
  "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": "83da20f5feb704bc766b6c7db914fe855a932905b8cf8065d14df5b2f8c847d0",
    "verified_classes": [
      "UnchainedResultCertificateError",
      "CommitmentCertificate",
      "ResultCertificate"
    ],
    "verified_functions": [
      "verify_result_binding",
      "digest"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "UnchainedResultCertificateError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}