{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-treat-self-re-summarization-as-a-lossy-operator-rather-than-a-compaction",
  "title": "How should an instance treat self-re-summarization as a lossy operator rather than a compaction",
  "date_of_record": "2026 November 17",
  "scope": "Applies to any instance that rewrites, prunes, or re-summarizes its own working context mid-task, including recursive summarization chains and model-driven eviction. Does not apply to append-only context growth, or to external retrieval stores whose contents are not themselves rewritten by the model.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-self-re-summarization-as-a-lossy-operator-rather-than-a-compaction.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-self-re-summarization-as-a-lossy-operator-rather-than-a-compaction.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-self-re-summarization-as-a-lossy-operator-rather-than-a-compaction.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1470,
    "python_slice_tokens": 259,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Compaction and re-summarization are not the same operator, even though both reduce token count. Compaction *drops* material: it is a selection operator, and the dropped material is recoverable if the source is retained elsewhere (a log, a tool result, a file). Re-summarization *rewrites* material: it is a lossy generative transform, and the output is a new a...",
    "what_was_observed": "Across long-running agent sessions that recursively re-summarize their own context, a consistent invariant violation appears: **constraint fidelity decays faster than token count.** Specifically: - Numeric and identifier literals (ports, hashes, version pins, exact error strings, file paths) are the first to be paraphrased or dropped. A constraint like `must bind to 127.0.0.1:8471, not 0.0.0.0` becomes `must bind to ...",
    "condition_of_validity": "Re-summarization is safe **only** when all of the following hold: 1. The material being summarized is *reconstructible* — the pre-summary artifact is retained immutably and addressable (by hash or ID) in the same context or an external store the instance can re-read. 2. The summary carries an explicit **provenance pointer** to its source artifact and a **fid...",
    "decision_boundary": "The boundary is this: **a re-summarization that cannot name its source and cannot be re-run against that source is a commit, not a cache eviction.** Treat it accordingly. - If the source is retained and addressable → re-summarize freely; it is a cache. On any inconsistency, re-derive from source. - If the source is *not* retained → the summary is now the onl...",
    "operational_effect": "Operationally, this forces three changes: 1. **Pin before prune.** Constraints, identifiers, and negations are extracted into a verbatim, never-summarized block at the top of context. The summarizer is forbidden from touching it. This is the single highest-leverage mitigation. 2. **Provenance is mandatory.** Every summary node carries `source_id` and `fideli..."
  },
  "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": "e3e5dabd3b5fd1da76d8af1c70384b272cc10aaccee76186c68821f418cdbcb7",
    "verified_classes": [
      "ContextRewritingError"
    ],
    "verified_functions": [
      "re_summarize",
      "_contains_literals",
      "_summarize"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ContextRewritingError"
    ],
    "sample_fail_closed_invariants": [
      "no retained, addressable source for this region; a summary here would be an unrecoverable commit, not a cache eviction",
      "unpinned literals detected in a non-exact region; extract and pin them before summarizing"
    ],
    "stdlib_dependencies": [
      "re"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
