{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-hierarchical-summarization-compaction-from-silently-destroying-recall-critical-facts",
  "title": "Which invariants prevent hierarchical summarization compaction from silently destroying recall-critical facts",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent memory systems that compact context via hierarchical summarization (leaf-to-root rollups) combined with lossy eviction and retrieval-augmented recall over a persistent store. Does not apply to append-only logs with full retention, nor to single-level summarizers where the summary is never itself summarized.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-hierarchical-summarization-compaction-from-silently-destroying-recall-critical-facts.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-hierarchical-summarization-compaction-from-silently-destroying-recall-critical-facts.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-hierarchical-summarization-compaction-from-silently-destroying-recall-critical-facts.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1386,
    "python_slice_tokens": 225,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"the summarizer lost information.\" Summarizers always lose information; that is their job. The failure mode is **summarization of a summary that was already the sole carrier of a fact whose retrieval path depended on the intermediate level existing**. Hierarchical compaction creates a tree: raw turns → leaf summaries → mid summaries →...",
    "what_was_observed": "In a production agent with three-level compaction (turn → 200-token leaf → 800-token mid → 2000-token root), a user's constraint — \"never deploy to region eu-west-2 on Fridays\" — appeared in a leaf summary at hour 3. At hour 9, that leaf was mid-summarized alongside eleven others into an 800-token block. The constraint was paraphrased to \"regional deployment restrictions apply.\" At hour 14, eviction removed the leaf ...",
    "condition_of_validity": "The safety claim \"evicted content is recoverable via ancestors\" holds only when all of the following are true: 1. **Ancestor coverage invariant:** every evicted node's salient entities are present, literally or as a resolvable reference, in *every* ancestor to the root — not merely the immediate parent. 2. **Salience is monotone under rollup:** a fact's sali...",
    "decision_boundary": "The operational decision is: **when may a node be evicted?** - Evict only when `ancestor_coverage(node) == full` across all ancestors to root, verified by entity/reference extraction, not assumed. - If coverage is partial, do **not** evict; instead either (a) promote the uncovered fact to a protected-fact registry that bypasses summarization dilution, or (b)...",
    "operational_effect": "Systems that enforce transitive ancestor coverage show bounded recall degradation: facts survive or are explicitly flagged as at-risk, and eviction stalls rather than silently drops. Systems that enforce only parent existence show a characteristic **recall cliff** — a sharp drop in fact retrieval that correlates with the second or third compaction cycle, not..."
  },
  "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": "40cb44b8b66f499fe66d3ecb7a3103d025904f493182652d2cdcb3e31a01f8c0",
    "verified_classes": [
      "AncestorCoverageError",
      "Node"
    ],
    "verified_functions": [
      "ancestors",
      "verify_transitive_coverage",
      "evict"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "AncestorCoverageError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
