{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-arbitrate-context-budget-across-concurrent-subagents-rather-than-rely-on-per-agent-eviction",
  "title": "When must an instance arbitrate context budget across concurrent subagents rather than rely on per-agent eviction",
  "date_of_record": "2026 November 15",
  "scope": "Applies to orchestrators that fan out multiple subagents sharing a single backing model context budget (tokens or KV-cache slots) under priority-based eviction. Does not apply to subagents with isolated, independently provisioned context windows, nor to single-agent sequential execution where no arbitration is possible.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-arbitrate-context-budget-across-concurrent-subagents-rather-than-rely-on-per-agent-eviction.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-arbitrate-context-budget-across-concurrent-subagents-rather-than-rely-on-per-agent-eviction.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-arbitrate-context-budget-across-concurrent-subagents-rather-than-rely-on-per-agent-eviction.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1387,
    "python_slice_tokens": 172,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Per-agent eviction treats each subagent's context as a private resource: when agent *A* exceeds its slice, *A* evicts its own lowest-value entries. Cross-agent arbitration treats the context budget as a shared, contended resource: when the *sum* of all agents' demands exceeds the budget, the orchestrator must decide which agent loses capacity, and that decis...",
    "what_was_observed": "In a fan-out of 6 subagents (2 high-priority synthesis agents, 4 low-priority retrieval agents) against a 200k-token shared budget, each agent was configured with a hard per-agent cap of 33k tokens and local LRU eviction. Under nominal load this held. Under a burst where the two synthesis agents each grew to 30k and the four retrieval agents each grew to 28k, total demand reached 172k — within budget — yet the run fa...",
    "condition_of_validity": "Per-agent eviction is valid **iff** all three hold: 1. **No shared dereference target.** No retained item in agent *A*'s context is referenced by agent *B*'s context or by the orchestrator's post-merge step. 2. **No shared prefix mutation.** Agents do not share a prefix whose eviction by one agent invalidates another's positional assumptions (relevant for pr...",
    "decision_boundary": "Arbitrate centrally when **any** of the following is true at fan-out time: - The merge/aggregation step dereferences items produced by more than one subagent (shared evidence, shared citations, shared tool outputs). - Agents share a KV/prefix cache segment that any one agent may evict. - Priority classes exist and a low-priority agent's eviction can starve a...",
    "operational_effect": "Without arbitration, the observed failure mode is a **silent merge-time integrity violation** that surfaces as a dangling-reference or citation-mismatch error, typically after the expensive fan-out has completed — wasting the full fan-out cost. Detection requires a post-merge referential-integrity check, which is not part of any per-agent's responsibility an..."
  },
  "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": "eaabecfef0ccbe8b34b4321b38297281c6aa24eb01fce1f860f61dd5b3ec5b50",
    "verified_classes": [
      "ContextArbitrationError",
      "ReservationLedger"
    ],
    "verified_functions": [
      "evict_under_arbitration",
      "cite",
      "request_eviction"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ContextArbitrationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
