{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-quorum-certificate-fail-to-commit-when-the-leader-has-already-sent-prepare-to-a-quorum-the-certificate-ordering-invariant-in-cros",
  "title": "Why does an instance quorum certificate fail to commit when the leader has already sent PREPARE to a quorum: the certificate-ordering invariant in cross-org BFT action commitment",
  "date_of_record": "2026 November 11",
  "scope": "This record applies to Byzantine fault-tolerant consensus deployments (PBFT/HotStuff/Tendermint-class protocols) that commit *external side-effecting actions* — payments, API calls, resource locks — on behalf of multiple organizations, where a quorum certificate (QC) is treated as proof of commitment. It does not apply to read-only replicated state machines, to single-org deployments with a single signing authority, or to protocols that commit by executing inside the replicated state machine itself rather than by emitting an external action upon QC formation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-quorum-certificate-fail-to-commit-when-the-leader-has-already-sent-prepare-to-a-quorum-the-certificate-ordering-invariant-in-cros.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-quorum-certificate-fail-to-commit-when-the-leader-has-already-sent-prepare-to-a-quorum-the-certificate-ordering-invariant-in-cros.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-quorum-certificate-fail-to-commit-when-the-leader-has-already-sent-prepare-to-a-quorum-the-certificate-ordering-invariant-in-cros.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2589,
    "python_slice_tokens": 469,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct meanings of \"committed\" that operators conflate when they wire a BFT consensus layer to an external action executor: 1. **Certificate commitment** — a quorum of replicas has signed a view/block certificate. This proves that a supermajority *voted* for a proposal. 2. **Action commitment** — the external effect (the wire transfer, the lo...",
    "what_was_observed": "A four-org deployment (`n = 7`, `f = 2`) committing treasury disbursements. Each org runs one replica; the leader is rotated per view. The leader process hosts two threads: the consensus thread (proposes, collects votes, assembles QC) and the outbox thread (drains staged actions to the executor after QC is observed). A shared in-process `staged` map was used to pass actions from consensus to outbox. Incident sequence...",
    "condition_of_validity": "The certificate-ordering invariant holds — i.e., a committed action implies a genuine quorum witnessed the corresponding proposal — only when all three of the following hold: 1. **Dispatch gating:** the action is dispatched to the external executor *only after* a QC is verified by the dispatching process, and the QC is verified against signatures from `2f+1`...",
    "decision_boundary": "The decision an operator faces is whether to treat the QC as the *commit point* for the action or to introduce a separate action-commitment step. The boundary is drawn by the cost of a false commit versus the cost of a delayed commit: - **Treat QC as commit point** (dispatch immediately on verified QC): correct only if the executor is idempotent on `(action_...",
    "operational_effect": "Deployments that cross this boundary without the invariant exhibit a characteristic failure signature: **consensus liveness and safety metrics are green while the external ledger diverges.** QC formation latency, view-change counts, and replica disagreement all look healthy. The divergence appears only in the executor's audit log, as either (a) two actions f..."
  },
  "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": "ce78a9f655aa934b6bc442361d3dad6c0442de6cb3553329642d73424f7a4c54",
    "verified_classes": [
      "ActionCommitmentError",
      "QuorumCertificate",
      "OutboxEntry",
      "ActionExecutor"
    ],
    "verified_functions": [
      "dispatch_from_outbox",
      "verified_signer_count",
      "__init__",
      "apply"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ActionCommitmentError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}