{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-speculative-branch-state-be-retired-the-rollback-retirement-gap-in-parallel-multi-agent-rollouts",
  "title": "Where must an instance of speculative branch state be retired: the rollback-retirement gap in parallel multi-agent rollouts",
  "date_of_record": "2026 November 17",
  "scope": "Applies to orchestrators that fan out speculative branches of an agent plan, verify them, and roll back losers after a winner is committed. Does not apply to single-branch execution, to branches that share no mutable external state, or to systems where verification is a pure function of branch output with no side effects.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-speculative-branch-state-be-retired-the-rollback-retirement-gap-in-parallel-multi-agent-rollouts.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-speculative-branch-state-be-retired-the-rollback-retirement-gap-in-parallel-multi-agent-rollouts.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-speculative-branch-state-be-retired-the-rollback-retirement-gap-in-parallel-multi-agent-rollouts.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1331,
    "python_slice_tokens": 163,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *logical divergence* and *effectful divergence*. A branch is logically divergent the moment its token stream departs from the winning branch. A branch is effectfully divergent only at the moment it performs a side effect that the winner did not perform — a tool call, a file write, a queue publish, a cache mutation, a s...",
    "what_was_observed": "In a rollout of a plan with a fan-out width of 4 (one planner branch, three executor branches each invoking a `write_record` tool against a shared ledger), the verifier selected branch 2 as the winner at step 11. Branch 1 and branch 3 had diverged logically at steps 4 and 6 respectively, and the orchestrator — following a \"retire on divergence\" policy — destroyed their execution contexts immediately at divergence. Bo...",
    "condition_of_validity": "Retiring branch state at logical divergence is valid **if and only if** every effect the branch could have issued is either (a) synchronous and acknowledged before divergence, so the branch's effect set is fully known and frozen at retirement, or (b) idempotent and tagged with a branch-scoped key that a later sweeper can find without the branch context. The ...",
    "decision_boundary": "The decision boundary is between **divergence-triggered retirement** and **effect-quiescence-triggered retirement**. - Use divergence-triggered retirement only for branches whose effect surface is empty or fully synchronous-with-ack (pure reasoning, read-only tools, idempotent keyed writes with a live sweeper). - Use effect-quiescence-triggered retirement fo...",
    "operational_effect": "Enforcing effect-quiescence retirement changes three things. First, it raises peak memory and context residency, because losing branches live longer — this is the cost, and it is bounded by the effect drain time, not by branch lifetime. Second, it makes rollback a two-phase operation (drain, then compensate) rather than a single teardown, which requires the ..."
  },
  "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": "294f10ac4394631860d607d898fb4dd9f1e1712aa4bcfb6aeccc34566d40a471",
    "verified_classes": [
      "BranchRetirementError",
      "SpeculativeBranch"
    ],
    "verified_functions": [
      "__init__",
      "mark_diverged",
      "issue_effect",
      "acknowledge_effect",
      "retire"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "BranchRetirementError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
