{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-speculative-multi-agent-execution-diverge-from-its-rollback-checkpoint-under-concurrent-branch-arbitration",
  "title": "Why does an instance of speculative multi-agent execution diverge from its rollback checkpoint under concurrent branch arbitration",
  "date_of_record": "2026 November 17",
  "scope": "Applies to orchestrators that fork multiple speculative agent branches from a shared serialized state, allow each branch to invoke tools with side effects, and arbitrate a winning branch by comparison or vote before committing. Does not apply to purely read-only speculative decoding, nor to single-branch retry loops where no concurrent sibling exists.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-speculative-multi-agent-execution-diverge-from-its-rollback-checkpoint-under-concurrent-branch-arbitration.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-speculative-multi-agent-execution-diverge-from-its-rollback-checkpoint-under-concurrent-branch-arbitration.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-speculative-multi-agent-execution-diverge-from-its-rollback-checkpoint-under-concurrent-branch-arbitration.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1159,
    "python_slice_tokens": 172,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not a lost update and not a race on the checkpoint itself. It is a *rollback fidelity* violation: the committed state after arbitration is not equal to `checkpoint ⊕ winner_delta`, because one or more losing branches performed speculative tool invocations whose side effects were external to the checkpoint and therefore invisible to rollback. T...",
    "what_was_observed": "A three-branch planner/executor stack was forked from a checkpoint at step 40. Branch B and Branch C each issued a `reserve_slot` tool call against a shared scheduler to test feasibility before committing to a plan. Branch A was selected by the arbiter. On commit, the orchestrator rolled back B and C by restoring the step-40 checkpoint and replaying A's delta. A's next action was a `list_reservations` read, which ret...",
    "condition_of_validity": "The invariant `commit == checkpoint ⊕ winner_delta` holds if and only if every tool invoked by a losing branch is either (1) declared pure/idempotent and side-effect-free, or (2) compensated before the winner's next external read. Arbiters that assume checkpoint restoration is sufficient are operating outside the condition of validity the moment any branch h...",
    "decision_boundary": "Choose *checkpoint-only rollback* when all reachable tools are `PURE` or `IDEMPOTENT_WRITE` keyed by branch id (so a losing branch's write is namespaced and inert). Choose *compensating rollback* — checkpoint plus an ordered undo log of speculative side effects replayed in reverse before commit — when any branch can reach `EFFECTFUL` tools. Choose *speculati...",
    "operational_effect": "Orchestrators that ignore this boundary produce plans that are individually valid but globally inconsistent, and the inconsistency is *silent* — it surfaces downstream as capacity conflicts, duplicate notifications, or phantom resources days later. The mitigation is structural: tag tools with effect class at registration, refuse to fork a branch that can rea..."
  },
  "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": "3f36d45f31c797d4b973146aa30ad741fa141ba49e81900ce45f9f1765be6697",
    "verified_classes": [
      "SpeculativeRollbackDivergence"
    ],
    "verified_functions": [
      "assert_rollback_fidelity"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "SpeculativeRollbackDivergence"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
