{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-refuse-to-speculate-branch-and-verify-rollback-under-cost-aware-fan-out",
  "title": "Where must an instance refuse to speculate: branch-and-verify rollback under cost-aware fan-out",
  "date_of_record": "2026 November 18",
  "scope": "Applies to orchestrators that fan out multiple speculative agent branches, verify each candidate, and roll back non-verified branches while accounting for per-token and per-call cost. Does not apply to single-agent retry loops, deterministic workflow engines, or systems where branch verification is free and instantaneous.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-to-speculate-branch-and-verify-rollback-under-cost-aware-fan-out.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-to-speculate-branch-and-verify-rollback-under-cost-aware-fan-out.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-to-speculate-branch-and-verify-rollback-under-cost-aware-fan-out.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1250,
    "python_slice_tokens": 179,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The common mental model treats speculative fan-out as a latency/cost tradeoff: spawn N branches, verify, keep the winner, discard the losers. The invariant that actually governs correctness is different. **Rollback is only sound if the side-effect boundary of every branch is strictly below the verification boundary.** An instance must refuse to speculate whe...",
    "what_was_observed": "A multi-agent planner fanned out three speculative branches to fulfill a request. Each branch was a full agent with tool access. Branch A produced a correct plan and executed a `send_email` tool call; branches B and C produced plausible but ultimately rejected plans. The verifier ran *after* branch completion, selected A, and rolled back B and C — including refunding their token budgets to the cost ledger. The cost l...",
    "condition_of_validity": "Speculative fan-out with rollback is valid if and only if, for every branch: Concretely, a branch is speculatable only if all of the following hold: - Every tool call it may issue is either **read-only** or **deferred** (queued, not dispatched) until the branch is selected. - The verifier's decision is made on a *proposal* artifact, not on a *committed* effe...",
    "decision_boundary": "The admission rule is a single predicate evaluated at fan-out time, before any branch is spawned: - **Speculate** when the branch's declared tool set is read-only or deferrable, and the verifier can decide on the proposal alone. - **Serialize** when the branch requires an externally visible mutation whose result the verifier depends on. Here, verification mu...",
    "operational_effect": "Enforcing the predicate changes the failure mode from silent world-state corruption to an explicit, catchable refusal at admission time. The orchestrator no longer reports \"clean rollback\" for branches that leaked effects, because such branches are never admitted to speculation. The cost is reduced parallelism on effectful steps; the benefit is that rollback..."
  },
  "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": "a8cf28f657e4acdc01644d82a7278a1a42583d3b60a0fc902516f76d458178c9",
    "verified_classes": [
      "UnsafeSpeculationError"
    ],
    "verified_functions": [
      "admit_branch"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UnsafeSpeculationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
