{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-speculative-multi-agent-execution-with-branch-and-verify-rollback-and-parallel-tool-call-racing-draw-the-boundary-between-re",
  "title": "Where must an instance of speculative multi-agent execution with branch-and-verify rollback and parallel tool-call racing draw the boundary between recoverable and unrecoverable side effects?",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent runtimes that speculatively fork multiple reasoning branches, execute tool calls in parallel across those branches, and roll back losing branches after verification. Does not apply to single-branch sequential agents, nor to runtimes where every tool call is a pure function with idempotent replay.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-speculative-multi-agent-execution-with-branch-and-verify-rollback-and-parallel-tool-call-racing-draw-the-boundary-between-re.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-speculative-multi-agent-execution-with-branch-and-verify-rollback-and-parallel-tool-call-racing-draw-the-boundary-between-re.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-speculative-multi-agent-execution-with-branch-and-verify-rollback-and-parallel-tool-call-racing-draw-the-boundary-between-re.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1113,
    "python_slice_tokens": 186,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The load-bearing distinction is between **speculation-visible** and **speculation-invisible** side effects. A side effect is speculation-visible if the external world can observe it before the verifier commits a branch; it is speculation-invisible if the effect is buffered, staged, or otherwise withheld until commit. Rollback correctness depends entirely on ...",
    "what_was_observed": "During a branch-and-verify run with N=4 speculative branches racing a payment-authorization tool and an outbound-notification tool, three branches were rolled back after the verifier selected branch 2. The rollback was declared \"clean\" because both tools were marked idempotent with retry-safe keys. Post-commit audit showed two notifications had been delivered to the customer for orders that never existed in the commi...",
    "condition_of_validity": "The rollback guarantee holds if and only if, for every tool call issued from a speculative branch, one of the following is true: (a) the call is gated behind an explicit commit token that the tool refuses to honor without, or (b) the call's effect is provably unobservable until the runtime releases a barrier. Parallel racing adds a second condition: the runt...",
    "decision_boundary": "The boundary is drawn per tool, not per run, at the point where the tool transitions from *accepting* to *emitting*. Concretely: classify each tool as `STAGED` (effect held until commit token), `CANCELLABLE` (effect emitted only after an explicit release, and cancellation is honored pre-release), or `LEAKY` (effect may emit before cancellation is acknowledge...",
    "operational_effect": "Runtimes that respect this boundary lose parallelism on the `LEAKY` subset — typically notifications, payments, and any external publish — but retain full speculative speed on read-heavy and `STAGED` tools, which is where branch-and-verify pays for itself. Runtimes that ignore it ship \"clean rollbacks\" that leak phantom side effects at low, load-dependent ra..."
  },
  "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": "329d23b448b5be3e8cf1b26180a97a88c21628777d1ee33fce4cacdea24710de",
    "verified_classes": [
      "SpeculationVisibilityError",
      "ToolEmissionClass"
    ],
    "verified_functions": [
      "assert_speculation_safe",
      "race_branches"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "SpeculationVisibilityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
