{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-commit-before-a-speculative-branch-is-reconciled-the-rollback-orphan-invariant-in-cost-aware-multi-agent-execution",
  "title": "Where must an instance commit before a speculative branch is reconciled: the rollback-orphan invariant in cost-aware multi-agent execution",
  "date_of_record": "2026 November 17",
  "scope": "Applies to orchestrators that fan out speculative agent branches in parallel, each with its own scoped side effects (tool calls, writes, reservations), and that reconcile by selecting one branch and rolling back the rest. Does not apply to read-only fan-out, nor to systems where every branch's side effects are idempotent and externally compensable on demand.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-commit-before-a-speculative-branch-is-reconciled-the-rollback-orphan-invariant-in-cost-aware-multi-agent-execution.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-commit-before-a-speculative-branch-is-reconciled-the-rollback-orphan-invariant-in-cost-aware-multi-agent-execution.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-commit-before-a-speculative-branch-is-reconciled-the-rollback-orphan-invariant-in-cost-aware-multi-agent-execution.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1694,
    "python_slice_tokens": 328,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is not \"which branch wins\" but *when the winner becomes durable relative to when the losers are allowed to be abandoned*. A speculative orchestrator has two logically separate commitments: (1) the **selection commitment** — the decision that branch B is the one whose results will be surfaced — and (2) the **durability commitment*...",
    "what_was_observed": "In a fan-out of three branches (B1, B2, B3) executing a shared task with per-branch tool writes, the orchestrator selected B2 on a scoring threshold and immediately began compensating B1 and B3 while asynchronously flushing B2's writes to the durable store. B2's flush failed a consistency check (a schema-version skew on one downstream sink) and was retried. During the retry window, B1 and B3 had already been compensa...",
    "condition_of_validity": "The invariant holds only under all of the following: - Side effects are **externally visible** before the branch reports (tools write to shared sinks, reservations are held, messages are emitted). If all effects are buffered in branch-private storage until selection, the boundary does not exist and naive rollback is safe. - The selector is **revisable** afte...",
    "decision_boundary": "The operational rule is a strict ordering with a barrier: 1. **Quiesce** all branches whose effects are externally visible — no new side effects may be initiated, including from staggered branches that have not yet reported. 2. **Select provisionally**, then **flush the selected branch to durability** and confirm the flush (not merely initiate it). 3. **Re-s...",
    "operational_effect": "Enforcing the barrier changes three observable properties of the system: - **Latency**: reconciliation gains one durability round-trip per selection. Cost-aware orchestrators that staggered launch to save tokens now pay a serialization cost at commit; budget for it or the barrier will be violated under load. - **Failure semantics**: flush failure becomes a *..."
  },
  "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": "e2412cd8dbf7cb4d1c4d4425eb74dc69b0b19f706a02a35a8d9777cc1512926c",
    "verified_classes": [
      "RollbackOrphanError",
      "Branch"
    ],
    "verified_functions": [
      "reconcile",
      "rescore",
      "__init__"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RollbackOrphanError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
