{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-reconcile-before-it-rolls-back-the-speculative-branch-commit-order-invariant",
  "title": "Where must an instance reconcile before it rolls back: the speculative-branch commit-order invariant",
  "date_of_record": "2026 November 18",
  "scope": "Applies to orchestration of parallel agent branches that execute speculatively against shared external state (databases, filesystems, message queues, APIs) and are expected to be rolled back on failure or reconciled on success. Does not apply to purely functional branches whose effects are buffered in-memory and committed atomically at the end, nor to branches that operate only on isolated copy-on-write snapshots.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-reconcile-before-it-rolls-back-the-speculative-branch-commit-order-invariant.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reconcile-before-it-rolls-back-the-speculative-branch-commit-order-invariant.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reconcile-before-it-rolls-back-the-speculative-branch-commit-order-invariant.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1810,
    "python_slice_tokens": 224,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **rollback of a branch's local state** and **reconciliation of effects that have already escaped the branch's isolation boundary**. Speculative execution frameworks universally provide the first. They almost never guarantee the second, and the failure mode is not a crash — it is a *silent divergence* between the orchestrat...",
    "what_was_observed": "A three-branch speculative fan-out was dispatched to resolve a data-migration task. Branch A mutated a shared catalog table (row-level updates keyed by `migration_id`), Branch B wrote artifacts to an object store under a prefix it *assumed* was branch-private, and Branch C performed only read-only analysis. Branch A failed validation and was rolled back. The orchestrator invoked `rollback(A)`, which replayed the inve...",
    "condition_of_validity": "Rollback-without-reconciliation is valid **only** when all of the following hold at the moment of rollback: 1. Every resource mutated by the branch carries an ownership token that the branch acquired and still holds, verifiable by a compare-and-check against the resource itself (not against a local cache). 2. Every emitted effect is either (a) recorded in a ...",
    "decision_boundary": "The decision procedure at rollback time must be: - **If** the branch has emitted zero effects outside its verified-private resources **and** holds all ownership tokens → rollback directly. This is the fast path and is correct. - **If** the branch has emitted effects to resources whose ownership cannot be re-verified → do **not** roll back. Escalate to reconc...",
    "operational_effect": "The practical consequence is that speculative fan-out frameworks need a **pre-rollback reconciliation gate**, not a post-rollback audit. The gate must run before any inverse operation is issued, and it must re-read resource ownership from the resource. Post-hoc audits are insufficient because by the time the audit runs, the destructive inverse has already ex..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "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": "046a38d62c87250dec8c27c360c475941e23ad5b728e8594e49cf924d59fa74d",
    "verified_classes": [
      "UnreconciledRollbackError",
      "BranchEffect"
    ],
    "verified_functions": [
      "pre_rollback_gate",
      "rollback_branch",
      "__init__"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "UnreconciledRollbackError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
