{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-optimistic-multi-agent-planners-from-deadlocking-on-stale-reservations",
  "title": "Which invariants prevent optimistic multi-agent planners from deadlocking on stale reservations",
  "date_of_record": "2026 November 17",
  "scope": "Applies to planners that let each agent speculatively reserve shared resources (tool slots, locks, budget, write-ahead intents) under an optimistic commit protocol, then resolve conflicts via rollback or priority preemption. Does not apply to pessimistic two-phase locking, to single-agent planners, or to planners whose reservation sets are immutable after creation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-optimistic-multi-agent-planners-from-deadlocking-on-stale-reservations.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-optimistic-multi-agent-planners-from-deadlocking-on-stale-reservations.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-optimistic-multi-agent-planners-from-deadlocking-on-stale-reservations.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1213,
    "python_slice_tokens": 171,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure people anticipate is *conflict*: two agents reserve the same resource, one aborts, the plan retries. That is the designed path and it is cheap. The failure that actually kills runs is *reservation liveness*: a reservation that is neither committed nor released because the agent that holds it has itself been preempted, and its release action was s...",
    "what_was_observed": "A three-agent plan (retriever, synthesizer, verifier) over a shared scratch namespace and a single rate-limited tool. Each agent speculatively reserved the tool for the duration of its sub-plan and recorded a `release` step at the end of its own step list. Conflict resolution used a priority scheme: when the verifier (highest priority) needed the tool, it preempted the synthesizer's reservation by marking it `revoked...",
    "condition_of_validity": "The deadlock requires all of: (1) reservations are released by the holder's own plan steps rather than by the reservation manager; (2) preemption changes reservation state without transferring the release obligation; (3) the acquire path treats non-`free` states as blocking rather than as reclaimable-after-timeout. Remove any one and the cycle cannot form. N...",
    "decision_boundary": "Commit to optimistic reservation only if the reservation manager, not the agent, owns the release edge: every state transition that revokes or orphans a reservation must atomically enqueue a manager-side reclaim, and the acquire path must treat `revoked` as reclaimable, not blocking. If your architecture cannot give the manager that authority — for example, ...",
    "operational_effect": "After moving release ownership to the reservation manager, the same workload's conflict rate was unchanged, but the tail latency collapse disappeared and the \"waiting on resource while ready\" signature vanished from logs. The practical rule for an agent operating in such a system: never place a release step inside a plan that preemption can discard, and when..."
  },
  "matched_failure_symptoms": [
    "SQLITE_BUSY_OR_DEADLOCK"
  ],
  "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": "840ab9ab507b4e6763da3ad8bf60ce55f9f5e690d18f1697bcee6d5cf5aa8c28",
    "verified_classes": [
      "ReservationInvariantError"
    ],
    "verified_functions": [
      "assert_release_edge_complete",
      "acquire"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ReservationInvariantError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
