{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-a-speculative-branch-be-forbidden-from-emitting-externally-observable-side-effects-and-what-breaks-when-the-rollback-boundar",
  "title": "Where must an instance of a speculative branch be forbidden from emitting externally observable side effects, and what breaks when the rollback boundary is drawn too late",
  "date_of_record": "2026 November 17",
  "scope": "Applies to branch-and-rollback orchestrators that fan out speculative sub-agents and permit them to issue tool calls (writes, sends, payments, deployments, state mutations) before the branch is committed. Does not apply to read-only speculation, to pure-compute branches, or to systems where every tool call is itself transactional and idempotent under a caller-supplied branch token.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-speculative-branch-be-forbidden-from-emitting-externally-observable-side-effects-and-what-breaks-when-the-rollback-boundar.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-speculative-branch-be-forbidden-from-emitting-externally-observable-side-effects-and-what-breaks-when-the-rollback-boundar.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-speculative-branch-be-forbidden-from-emitting-externally-observable-side-effects-and-what-breaks-when-the-rollback-boundar.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1737,
    "python_slice_tokens": 153,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *speculative state* and *observable effect*. A branch-and-rollback orchestrator can cheaply discard speculative state — its own memory, its own scratchpad, its own intermediate artifacts — because those live inside a namespace the orchestrator controls. It cannot discard an observable effect, because the effect has alr...",
    "what_was_observed": "A three-way speculative fan-out was launched against a task that included \"notify the on-call channel when the migration plan is ready.\" Two of the three branches produced plans that the verifier later rejected — one had an inconsistent schema reference, one assumed a table that did not exist. Both rejected branches had already called the notification tool, because the tool was registered as an ordinary callable with...",
    "condition_of_validity": "The invariant holds — speculative branches must be forbidden from external emission — under all of the following conditions: 1. The effect is not reversible by a compensating action the orchestrator can guarantee will run (e.g., an append-only audit log, a sent email, a fired webhook, a third-party API call with no delete). 2. The effect is observable by an ...",
    "decision_boundary": "The decision an orchestrator must make per tool call, before the call is dispatched, is: - **Is this tool call externally observable?** If no (pure read, pure compute, write to branch-private scratch), allow it freely; it is inside the rollback boundary by construction. - **If yes, is it compensable?** If a guaranteed compensating action exists and is regist...",
    "operational_effect": "Drawing the boundary at first emission changes the orchestrator's shape in three ways. First, tools acquire a branch lifecycle: `stage(token, payload)` → `commit(token)` or `discard(token)`, and the orchestrator must own that lifecycle, not the tool. Second, the commit phase becomes the only place where non-stageable effects execute, which means the commit p..."
  },
  "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": "b8e9a2506027711a96aee23231fa870bd59da6dd70fc5645848e3ee24ae11dd7",
    "verified_classes": [
      "SpeculationBoundaryError",
      "ToolCall"
    ],
    "verified_functions": [
      "dispatch",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "SpeculationBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
