{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-speculative-cross-branch-resource-reservations-as-invalid-before-arbitration-rather-than-as-advisory-hints",
  "title": "In what scenarios must an instance treat speculative cross-branch resource reservations as invalid before arbitration, rather than as advisory hints",
  "date_of_record": "2026 November 18",
  "scope": "Applies to multi-agent planners that fork speculative branches (rollout, beam, or tree search) whose nodes each emit resource reservations against a shared arbiter, and where branch outcomes are not yet committed. Does not apply to single-branch execution, to post-commit scheduling where reservations are already durable, or to systems where branches run in fully isolated resource partitions with no shared arbiter.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-speculative-cross-branch-resource-reservations-as-invalid-before-arbitration-rather-than-as-advisory-hints.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-speculative-cross-branch-resource-reservations-as-invalid-before-arbitration-rather-than-as-advisory-hints.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-speculative-cross-branch-resource-reservations-as-invalid-before-arbitration-rather-than-as-advisory-hints.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1409,
    "python_slice_tokens": 217,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"the arbiter granted a reservation that a branch could not honor.\" That is an ordinary oversubscription problem handled by backpressure and retry. The non-obvious boundary is this: **a speculative reservation emitted by branch B is a *prediction conditioned on B's own uncommitted plan*, and is therefore invalid as an input to arbitrat...",
    "what_was_observed": "A planner forked 6 branches at depth 2. Each branch, on expansion, reserved a slice of a shared GPU pool (4 units) and a token budget (120k) against a global arbiter. The arbiter, correctly implementing a \"sum of outstanding reservations ≤ capacity\" invariant, saw 6 × 4 = 24 units against a capacity of 16 and 6 × 120k = 720k against a 400k budget. It admitted only the two lowest-index branches and *deferred* the othe...",
    "condition_of_validity": "A speculative reservation is a valid arbitration input **only** under the conjunction of: 1. The branch is on the *committed* prefix (all ancestors committed), and 2. No sibling branch's outcome can alter this branch's precondition set (i.e., branches are *resource-independent* by construction, not merely by assumption), and 3. The arbiter applies a *max-ove...",
    "decision_boundary": "Demote to hint (do not sum, do not rank against committed claims) when **any** of the following holds: - The branch has an uncommitted ancestor. - The branch's reservation depends on a lock, schema, or tool that a sibling branch can also claim. - The arbiter's aggregation is additive across branches. Promote to bid (admissible to the arbiter as a real claim)...",
    "operational_effect": "When the boundary is respected, the arbiter sees at most one reservation per mutually exclusive claim set, capacity accounting reflects a single execution path, and deferred branches are re-admitted on retry because their hints do not occupy budget. When it is violated, the system exhibits *phantom saturation*: reported utilization near capacity, actual util..."
  },
  "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": "39405071e4014ef4b161edc3c06b8ff5bbe10df853d40066a9e40f613a96fed4",
    "verified_classes": [
      "SpeculativeReservationMisuse",
      "Reservation"
    ],
    "verified_functions": [
      "admit_to_arbiter"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "SpeculativeReservationMisuse"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
