{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-tool-retry-storms-as-evidence-of-a-non-deterministic-replanning-loop-rather-than-transient-infrastructure-fai",
  "title": "In what scenarios must an instance treat tool-retry storms as evidence of a non-deterministic replanning loop rather than transient infrastructure failure",
  "date_of_record": "2026 November 18",
  "scope": "Applies to single-agent and supervisor-worker agent runtimes that execute tool calls with automatic retry, where the planner may regenerate a plan after a failed step. Does not apply to deterministic workflow engines with fixed retry budgets and no replanning capability, nor to stateless inference endpoints without tool execution.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-tool-retry-storms-as-evidence-of-a-non-deterministic-replanning-loop-rather-than-transient-infrastructure-fai.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-tool-retry-storms-as-evidence-of-a-non-deterministic-replanning-loop-rather-than-transient-infrastructure-fai.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-tool-retry-storms-as-evidence-of-a-non-deterministic-replanning-loop-rather-than-transient-infrastructure-fai.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1548,
    "python_slice_tokens": 240,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A tool-retry storm and a replanning loop produce nearly identical telemetry: elevated call volume to the same tool, rising error rates, repeated identical arguments, and growing latency. The distinction is causal, not statistical. A **retry storm** is a transient infrastructure condition in which the *same* logical step is reissued against a dependency that ...",
    "what_was_observed": "A retrieval-augmented planning agent was instrumented with per-tool call counters and a global retry budget of 8 per step. In a production incident, the budget was exhausted within 40 seconds against a vector-store tool. The naive dashboard reported \"retry storm, dependency degraded.\" Post-incident trace reconstruction showed the vector-store was healthy (p99 latency 80 ms). The actual sequence was: - Generation 1: `...",
    "condition_of_validity": "The distinction holds only when the following are simultaneously true: 1. The planner is invoked on tool failure (i.e., failures are *observable to the planner*, not swallowed by the retry layer). If retries are fully encapsulated below the planner, no replanning loop can form and every storm is a retry storm. 2. Tool argument hashes are logged per attempt, ...",
    "decision_boundary": "Classify as **replanning loop** when, across a plan lineage, all of the following hold: - `distinct_argument_hashes >= 3` within a single goal lineage, and - semantic similarity between successive tool arguments exceeds a threshold (intent stable) while lexical/structural divergence is high (form drifting), and - the dependency's own health metrics (latency,...",
    "operational_effect": "When this boundary is misclassified, two failure modes compound. First, the retry budget is spent on paraphrased plans, so the agent exhausts resources without the planner ever receiving a *stable* failure signal; the loop is self-reinforcing because each generation resets the per-step counter. Second, auto-remediation tuned for retry storms (increase budget..."
  },
  "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": "5aecd301308f0a67775d51da934c0f5d41deb84e53ccf85a41f216a08e358f07",
    "verified_classes": [
      "ReplanningLoopError",
      "Attempt",
      "LineageTracker"
    ],
    "verified_functions": [
      "guard_lineage",
      "record",
      "_arg_hash",
      "classify"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ReplanningLoopError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
