{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-an-unverified-speculative-tool-call-commit-has-already-escaped-the-rollback-horizon",
  "title": "What structural signals indicate an unverified speculative tool-call commit has already escaped the rollback horizon",
  "date_of_record": "2026 November 15",
  "scope": "Applies to multi-agent systems that speculatively execute branches of a plan, pipeline tool calls optimistically ahead of verification, and roll back non-committed branches on divergence. Does not apply to systems that serialize every tool call behind a verification barrier, nor to purely conversational agents whose tool calls are idempotent reads.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-unverified-speculative-tool-call-commit-has-already-escaped-the-rollback-horizon.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-unverified-speculative-tool-call-commit-has-already-escaped-the-rollback-horizon.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-an-unverified-speculative-tool-call-commit-has-already-escaped-the-rollback-horizon.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1683,
    "python_slice_tokens": 382,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **rollback of state you control** and **rollback of effects you have already surrendered to an external system**. Speculative execution is safe only while every optimistic side effect remains *revocable*: buffered, staged, or compensable. The moment an optimistic tool call crosses the point of no return — a write that ...",
    "what_was_observed": "A planner agent spawned three speculative branches (A, B, C) to resolve an ambiguous user request. Each branch optimistically pipelined its tool calls: A issued a `create_ticket` to an external tracker, B issued a `send_notification`, C issued a `reserve_inventory`. Verification selected C. Rollback was invoked on A and B. The rollback succeeded in the orchestrator's ledger: A and B were marked `rolled_back`, their l...",
    "condition_of_validity": "Optimistic pipelining with branch-and-verify rollback is valid **if and only if** the following holds at every verification point: 1. Every optimistic tool call is either (a) staged behind a commit gate that the verifier controls, or (b) explicitly registered as an *irrevocable* effect with a known compensation action. 2. The branch's revocable set is recomp...",
    "decision_boundary": "The decision boundary is not \"did the tool call return?\" It is \"**has the remote authority committed a durable consequence that we cannot unilaterally reverse?**\" Three structural tests separate the two: - **ID test:** Did the remote system assign a durable identifier to the effect? A returned `ticket_id`, `message_id`, or `reservation_id` is a commitment re...",
    "operational_effect": "The operational consequence is a shift in where the system spends its safety budget. Instead of assuming rollback is free and spending budget on branch breadth, the system must spend budget on **effect classification at dispatch time** — tagging each tool call as `staged`, `revocable`, or `irrevocable` before it is pipelined — and on **compensation coverage*..."
  },
  "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": "ffcf3379708b68e59cbe1e8244fb943890c22be47e095d7205ebf1dfbee1d0c2",
    "verified_classes": [
      "EffectClass",
      "RollbackHorizonBreach",
      "ToolCall",
      "Branch"
    ],
    "verified_functions": [
      "rollback",
      "commit",
      "dispatch",
      "revocable_ids",
      "escaped_ids"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "RollbackHorizonBreach"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
