{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-compact-when-hierarchical-summarization-would-evict-an-unreconstructable-leaf",
  "title": "Under what conditions must an instance refuse to compact when hierarchical summarization would evict an unreconstructable leaf",
  "date_of_record": "2026 November 16",
  "scope": "Applies to any agent memory/context system that maintains a multi-level summary tree (leaf utterances → segment summaries → session summaries → rolling abstract) with a fixed token eviction budget enforced by auto-compaction. Does not apply to single-level truncation, append-only logs, or systems where every leaf is independently retrievable from durable storage at compaction time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-compact-when-hierarchical-summarization-would-evict-an-unreconstructable-leaf.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-compact-when-hierarchical-summarization-would-evict-an-unreconstructable-leaf.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-compact-when-hierarchical-summarization-would-evict-an-unreconstructable-leaf.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1549,
    "python_slice_tokens": 291,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Hierarchical summarization is *lossy by design*: each upward merge discards tokens. This is acceptable when the discarded content is either (a) reconstructable from a lower tier that still exists, or (b) genuinely redundant. The failure boundary is not \"summarization loses information\" — that is the contract. The boundary is a specific structural condition: ...",
    "what_was_observed": "During a long-running session with a 4-level tree and a 24k-token eviction budget, auto-compaction fired at 92% utilization. The policy selected the oldest 40 leaf segments for merge into their parent. Among them was a segment containing the only record of a hard numeric constraint: *\"the retry ceiling is 3, not 5 — the downstream service counts 5xx differently.\"* The parent summary, generated by an LLM merge step, c...",
    "condition_of_validity": "Refusal to compact is *correct* precisely when all of the following hold for a candidate eviction set `S`: - For some `l ∈ S`, `l` contains a singular commitment (exact scalar, identifier, verbatim imperative, or negated constraint). - No surviving ancestor summary *entails* that commitment (checked by extracting candidate commitments from the summary and te...",
    "decision_boundary": "The decision is a single predicate over the candidate set, evaluated *before* the merge step, not after: - **Proceed with compaction** iff every leaf in `S` is entailed by a surviving ancestor or is refetchable. - **Halt and escalate** iff some leaf in `S` is a live, singular, unreconstructable commitment. Escalation means: pin the leaf, exclude it from `S`,...",
    "operational_effect": "Systems that enforce the entailment-or-refetchability invariant trade a small amount of budget headroom (pinned leaves consume tokens that cannot be reclaimed) for the elimination of a whole class of silent contradiction failures. The observable signature of the *unfixed* system is: clean compaction telemetry, no errors, and downstream behavioral drift where..."
  },
  "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": "4d27c64efd67ff719110d7a37fd7ee305b2afcfdb6ea59710b37d3875678e3bb",
    "verified_classes": [
      "UnreconstructableEvictionError"
    ],
    "verified_functions": [
      "_is_singular_commitment",
      "_entailed_by_ancestor",
      "_refetchable",
      "plan_compaction",
      "auto_compact"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "UnreconstructableEvictionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "re"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
