{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-context-budget-starvation-in-shared-memory-subagent-arbitration",
  "title": "What structural signals indicate context budget starvation in shared-memory subagent arbitration",
  "date_of_record": "2026 November 16",
  "scope": "Applies to multi-agent systems in which two or more subagents read and write a shared memory substrate (vector store, KV cache, episodic log) under a single enforced context budget. Does not apply to subagents with isolated memory namespaces or to single-agent long-context regimes where no arbitration occurs.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-context-budget-starvation-in-shared-memory-subagent-arbitration.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-context-budget-starvation-in-shared-memory-subagent-arbitration.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-context-budget-starvation-in-shared-memory-subagent-arbitration.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1235,
    "python_slice_tokens": 162,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **budget exhaustion** and **budget starvation**. Exhaustion is a local, observable event: a subagent's working set hits the token ceiling and it truncates or fails. Starvation is a *structural* condition in which a subagent's effective allocation is driven below its working-set floor not by aggregate demand but by the *ord...",
    "what_was_observed": "In a three-subagent configuration (planner, retriever, synthesizer) over a shared vector substrate with a 96k-token aggregate budget and a per-epoch fair-share arbiter: - The planner's write rate to the substrate correlated with the retriever's *measured* demand, but inversely with its *satisfied* demand. Each planner write added embeddings that raised the retriever's top-k retrieval cost, inflating the retriever's d...",
    "condition_of_validity": "This diagnosis is valid only when all of the following hold: 1. The arbiter derives demand from observed substrate access, not from a static per-agent quota. 2. At least one subagent's writes alter the retrieval cost or result set of another's reads (shared, mutable substrate). 3. Arbitration epochs are shorter than the time for demand to reach a fixed point...",
    "decision_boundary": "Operators must choose between two responses at the point where stable-demand/falling-allocation is detected: - **Treat as starvation** (correct when read-to-write ratio is collapsing and reuse ratio is rising): freeze substrate mutation for one epoch, re-measure demand against a static substrate, and re-arbitrate. This isolates endogenous inflation from genu...",
    "operational_effect": "The practical consequence is that fair-share arbiters over shared mutable substrates are *not* stable under load and will silently concentrate allocation on whichever subagent mutates the substrate most. The starving subagent fails quietly — it does not error, it degrades, and its degradation feeds back as reduced writes that make the substrate *look* health..."
  },
  "matched_failure_symptoms": [
    "OOM_KILL_OR_MEMORY_EXHAUSTION"
  ],
  "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": "cfc01a69dd3e9bc170302e880a11327d87c1e5db1318666bba81e68df56bcbad",
    "verified_classes": [
      "ContextStarvationError"
    ],
    "verified_functions": [
      "arbitrate"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ContextStarvationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
