{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-speculative-branch-divergence-has-outlived-its-rollback-window-in-multi-agent-tool-invocation",
  "title": "What structural signals indicate speculative branch divergence has outlived its rollback window in multi-agent tool invocation",
  "date_of_record": "2026 November 14",
  "scope": "Applies to orchestrators that fan out speculative agent branches which optimistically invoke side-effecting tools and rely on branch-and-verify rollback to reconcile divergent state. Does not apply to read-only tool surfaces, to branches whose tool calls are gated behind a two-phase commit barrier, or to single-agent retry loops where rollback is trivially idempotent.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-speculative-branch-divergence-has-outlived-its-rollback-window-in-multi-agent-tool-invocation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-speculative-branch-divergence-has-outlived-its-rollback-window-in-multi-agent-tool-invocation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-speculative-branch-divergence-has-outlived-its-rollback-window-in-multi-agent-tool-invocation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1611,
    "python_slice_tokens": 264,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"a branch produced a wrong result.\" That is expected and is precisely what rollback exists to absorb. The failure is that **the rollback window closed while the branch was still legally executing**, so a speculative branch that later loses verification has already committed effects that the winning branch will now overwrite or duplica...",
    "what_was_observed": "In a three-agent speculative fan-out (planner spawns branches A, B, C; a verifier selects one and rolls back the rest), the following structural signals preceded each incident: 1. **Branch age exceeding verifier cadence.** Branches A and B were spawned at t=0; the verifier's first comparative pass ran at t=40s. Branch B's tool call to `send_notification` committed at t=31s. The rollback of B at t=42s succeeded agains...",
    "condition_of_validity": "The invariant that makes optimistic speculative invocation sound is: > For every tool invocation made by a speculative branch, the orchestrator must be able to complete verification and issue a compensating rollback *before* the invocation's commit frontier is crossed. This holds only when, for all branches and all their tool calls, `t_verify_close(branch) <...",
    "decision_boundary": "When the signals above appear, the orchestrator must choose between two responses, and the choice is not symmetric: - **If the branch's tool set is fully compensable and the compensation is registered and tested**, the correct action is to *narrow the speculative horizon*: admit only tool calls whose commit frontier is provably after the verification close, ...",
    "operational_effect": "Once the rollback window is outlived, the orchestrator's local state and the external world are permanently inconsistent in a way that *looks* consistent locally: every ledger entry reads `ROLLED_BACK`, every branch reads `CLOSED`, and the verifier reports a clean selection. The inconsistency surfaces only downstream, as duplicated external effects, as effec..."
  },
  "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": "15d205cf8a61c5f77ac3ec3a0301c13d6c5912d5e4a91363dd50db78ba3128fa",
    "verified_classes": [
      "RollbackWindowExceeded",
      "ToolCall"
    ],
    "verified_functions": [
      "admit_speculative_branch",
      "rollback_branch"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RollbackWindowExceeded"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
