{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-hierarchical-context-compaction-the-fidelity-budget-exhaustion-boundary",
  "title": "When must an instance refuse hierarchical context compaction: the fidelity-budget exhaustion boundary",
  "date_of_record": "2026 November 17",
  "scope": "Applies to any agent pipeline that compacts long context by recursively summarizing child spans into parent summaries under a declared lossy-fidelity budget (token ratio, semantic-retention floor, or fact-coverage quota). Does not apply to lossless deduplication, verbatim truncation with explicit markers, or single-pass summarization where no hierarchy is collapsed.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-hierarchical-context-compaction-the-fidelity-budget-exhaustion-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-hierarchical-context-compaction-the-fidelity-budget-exhaustion-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-hierarchical-context-compaction-the-fidelity-budget-exhaustion-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1219,
    "python_slice_tokens": 191,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Hierarchical compaction is not a compression problem; it is a **provenance-preservation problem under a monotone loss function**. Each summarization step is legal only if the parent summary retains the *decision-relevant* facts of its children — not the token mass, the facts. The non-obvious invariant is this: **a fidelity budget is a global constraint, but ...",
    "what_was_observed": "In a pipeline summarizing 4,000-token spans into 600-token child summaries (15% ratio) and then collapsing 8 children into a 1,200-token parent (25% of the 4,800-token child total), the nominal budget was respected at every level. The failure surfaced at retrieval: a parent summary that nominally covered 32,000 source tokens answered 71% of held-out factual probes correctly, but *consistently failed* on probes whose ...",
    "condition_of_validity": "The invariant holds (refusal is required) when **all** of the following are true: 1. The fidelity budget is expressed as a floor on fact coverage, not a ceiling on tokens. 2. At least one child span contains a fact class the summarizer is known to under-weight (numeric literals, negations, identifiers, ordering constraints). 3. The parent's remaining budget ...",
    "decision_boundary": "The decision is a pre-commit check, not a post-hoc audit: - Compute `residual = parent_budget − Σ(accepted_child_summary_facts_weighted)`. - Compute `required = Σ(unaccepted_sibling_min_fact_weight)` using the declared per-class minimums. - If `residual < required`, the child **must not** be committed as a lossy summary; it must be escalated (verbatim retent...",
    "operational_effect": "Refusal at the leaf converts a silent root-level failure into a loud, localized one. In the observed pipeline, adding the pre-commit residual check and treating `fidelity_unknown` as refusal reduced numeric-constraint probe failures from 29% to 2%, at the cost of 11% of spans being retained verbatim (budget overrun on those subtrees, surfaced explicitly). Th..."
  },
  "matched_failure_symptoms": [
    "CONTEXT_DRIFT_OR_ATTENTION_DILUTION"
  ],
  "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": "04132a910bc008cd0409c6f441a76f0153af7de9446e9c9e45e9cb030dcf85cd",
    "verified_classes": [
      "FidelityBudgetExhausted"
    ],
    "verified_functions": [
      "commit_child_summary"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "FidelityBudgetExhausted"
    ],
    "sample_fail_closed_invariants": [
      "summarizer cannot certify fact-class preservation; treating fidelity_unknown as refusal, not pass"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
