{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-hierarchical-context-budgeting-as-a-hard-admission-control-problem-rather-than-a-soft-prioritization-heuristi",
  "title": "In what scenarios must an instance treat hierarchical context budgeting as a hard admission-control problem rather than a soft prioritization heuristic",
  "date_of_record": "2026 November 12",
  "scope": "This record applies to inference pipelines that assemble a single context window from at least three competing sources — a fixed system prompt, retrieved long-term memory, and tool-call results — under a policy that dynamically reallocates token budget between them per turn. It does not apply to single-source prompting, to stateless RAG with a static budget split, or to pipelines where the context window is large enough that every source can be admitted without truncation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-hierarchical-context-budgeting-as-a-hard-admission-control-problem-rather-than-a-soft-prioritization-heuristi.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-hierarchical-context-budgeting-as-a-hard-admission-control-problem-rather-than-a-soft-prioritization-heuristi.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-hierarchical-context-budgeting-as-a-hard-admission-control-problem-rather-than-a-soft-prioritization-heuristi.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1501,
    "python_slice_tokens": 298,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *budgeting as prioritization* and *budgeting as admission control*. A prioritization heuristic asks \"which source should get more of the slack?\" and silently truncates whatever does not fit. An admission-control regime asks \"can this source be admitted at all without violating a hard invariant?\" and refuses the turn wh...",
    "what_was_observed": "In a pipeline with a 32k window, a 2.1k system prompt, a memory retriever returning up to 40 chunks, and tool results averaging 6k tokens but with a heavy tail (p99 ≈ 28k for a file-read tool), the following sequence reproduced reliably: 1. Turn N admits a large tool result (24k tokens). The allocator, seeing pressure, evicts memory chunks and *compresses* the system prompt by dropping \"redundant\" boilerplate — speci...",
    "condition_of_validity": "The admission-control framing is valid — and the prioritization framing is unsafe — exactly when all three of the following hold: - **Non-truncatable floor exists.** At least one source (here, the system prompt) has a minimum admissible size below which the context is semantically invalid, not merely lower quality. - **Arrival sizes are unknown at allocation...",
    "decision_boundary": "The decision rule for an instance operating under this regime: - Compute the **reserved floor** = sum of non-truncatable minimums (system prompt full size + minimum viable memory + a tool-result framing overhead). This is subtracted from the window *before* any dynamic allocation. It is never a candidate for eviction. - Treat tool results as **admit-or-refus...",
    "operational_effect": "Under the admission-control regime, the loop above terminates: the oversized tool result is spilled to a handle, the system prompt is never mutated, memory degrades to empty, and the agent receives a structurally valid (if less informed) context. The cost is that some turns are refused or spilled rather than \"answered with less,\" which is the correct trade w..."
  },
  "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": "9487a0ce692e9a478e2c1bf789bdf0ab0ec8ae79e9f63397797018e3ebb18d22",
    "verified_classes": [
      "ContextBudgetViolation",
      "Budget"
    ],
    "verified_functions": [
      "admit_tool_result",
      "allocate_turn",
      "reserved_floor"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ContextBudgetViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}