{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-that-speculative-branch-and-verify-rollback-has-failed-to-quiesce-in-multi-agent-tool-calling-systems",
  "title": "What structural signals indicate that speculative branch-and-verify rollback has failed to quiesce in multi-agent tool-calling systems",
  "date_of_record": "2026 November 17",
  "scope": "Applies to multi-agent systems where a coordinator forks speculative branches, each of which may issue speculative tool calls (writes, RPCs, state mutations) that are verified against a reference branch and rolled back on divergence. Does not apply to read-only speculative execution, nor to systems where tool calls are fully transactional and idempotent at the tool boundary.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-speculative-branch-and-verify-rollback-has-failed-to-quiesce-in-multi-agent-tool-calling-systems.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-speculative-branch-and-verify-rollback-has-failed-to-quiesce-in-multi-agent-tool-calling-systems.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-speculative-branch-and-verify-rollback-has-failed-to-quiesce-in-multi-agent-tool-calling-systems.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1706,
    "python_slice_tokens": 319,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure most often mistaken for a rollback bug is not a rollback bug. Rollback of *state* and rollback of *in-flight tool calls* are two different operations that complete on two different clocks. State rollback (branch discard, context truncation, KV-cache eviction) is synchronous and observable. Tool-call rollback is asynchronous, delegated to the tool...",
    "what_was_observed": "In a coordinator that forked four speculative branches per turn across a shared filesystem-like tool and a shared key-value store, we observed the following during a stress run at 1,200 turns: - The coordinator's branch table reported all divergent branches as `ROLLED_BACK` within 40 ms of the verify step. The same branches continued to emit tool-call completions for a median of 310 ms afterward, with a p99 tail of 6...",
    "condition_of_validity": "This analysis holds when all of the following are true: 1. Speculative branches can issue tool calls that are not idempotent or not naturally reversible (writes, appends, increments, message sends). 2. Rollback is implemented as branch discard plus best-effort compensation, not as a distributed transaction with a two-phase commit across the tool. 3. The coor...",
    "decision_boundary": "The decision boundary is whether to treat the *effect acknowledgment* — not the branch future — as the unit of quiescence. Concretely: - If the tool supports branch-scoped fencing tokens (a monotonically increasing epoch attached to each call, with the tool rejecting calls whose epoch is below the committed branch's epoch), the zombie window is closed at the...",
    "operational_effect": "When this boundary is respected, the practical consequences are: - Commit counts reconcile with applied-write counts under load; the residual delta is bounded by the fencing-token propagation delay, not by branch count. - The p99 tail of zombie emissions collapses from seconds to the tool's own round-trip time, because the tool rejects late calls rather than..."
  },
  "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": "587c8b2348a72406b5a55d5f063ae04c828d9f5d386dc93e5d22d1d405117b50",
    "verified_classes": [
      "ZombieBranchError",
      "EffectState",
      "EffectEntry",
      "EffectLedger"
    ],
    "verified_functions": [
      "finalize_branch",
      "record_dispatch",
      "record_applied",
      "record_compensated",
      "assert_quiescent"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ZombieBranchError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
