{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-roll-back-a-speculative-branch-the-non-idempotent-side-effect-horizon-in-branch-and-verify-multi-agent-execution",
  "title": "When must an instance refuse to roll back a speculative branch: the non-idempotent side-effect horizon in branch-and-verify multi-agent execution",
  "date_of_record": "2026 November 17",
  "scope": "Applies to orchestration runtimes that fork parallel agent branches, hedge speculative tool calls, and commit the first branch whose verifier passes while rolling back the rest. Does not apply to pure-compute branches with no externally observable effects, nor to systems where every tool call is provably idempotent and transactionally reversible.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-roll-back-a-speculative-branch-the-non-idempotent-side-effect-horizon-in-branch-and-verify-multi-agent-execution.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-roll-back-a-speculative-branch-the-non-idempotent-side-effect-horizon-in-branch-and-verify-multi-agent-execution.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-roll-back-a-speculative-branch-the-non-idempotent-side-effect-horizon-in-branch-and-verify-multi-agent-execution.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1544,
    "python_slice_tokens": 238,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"rollback failed.\" It is the *silent partial commit* of a branch that the orchestrator believes it discarded. Branch-and-verify assumes a clean dichotomy: a branch is either committed (its effects are durable and its state is canonical) or rolled back (its effects are erased and its state is garbage-collected). This dichotomy holds on...",
    "what_was_observed": "A planner agent forked three branches to fulfill a provisioning request. Each branch hedged its payment-authorization tool call with two parallel invocations (`stripe.charge`-equivalent, keyed by a per-branch idempotency token) to beat p99 latency. Branch B's verifier passed first. The orchestrator committed B and issued rollback to A and C. Rollback for A and C succeeded at the *state* layer: their scratchpads were ...",
    "condition_of_validity": "Rollback-as-erasure is valid **iff** for every effect `e` produced by a branch, at least one holds: 1. `e` has not yet been *observably emitted* (still buffered, still revocable in-transport), **or** 2. `e` is idempotent under the runtime's replay key, and the key is scoped to the *logical operation* rather than the *physical call*, **or** 3. `e` has a compe...",
    "decision_boundary": "The operative rule: **a branch must be treated as committed — and must be reconciled, not erased — the instant any of its effects crosses the side-effect horizon, regardless of verifier outcome.** The orchestrator must not roll back a branch that has crossed its horizon; it must instead *quarantine* it, record its effects in the canonical ledger as \"speculat...",
    "operational_effect": "Runtimes that internalize this boundary stop treating rollback as a universal inverse and start treating it as a *conditional* operation with an explicit precondition check. The observable changes: - Hedged calls carry logical-operation idempotency keys, collapsing *N* physical calls to one durable effect, so *N−1* hedges become true no-ops rather than orpha..."
  },
  "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": "1f15c6326d0aba1fde59d1f524e098dc2858adf4088fde5e2ea3952bcc6588a3",
    "verified_classes": [
      "SideEffectHorizonCrossed",
      "Branch"
    ],
    "verified_functions": [
      "rollback",
      "commit_or_rollback",
      "__init__",
      "crossed_horizon"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "SideEffectHorizonCrossed"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
