{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-abandon-lossy-auto-compaction-and-escalate-to-full-context-reconstruction",
  "title": "Under what conditions must an instance abandon lossy auto-compaction and escalate to full-context reconstruction",
  "date_of_record": "2026 November 14",
  "scope": "Applies to long-running agent instances that maintain a rolling conversation/working memory via periodic auto-compaction with a bounded token budget for lossy summarization, then reconstruct context at inference time by retrieving from the summary plus an external store. Does not apply to stateless request/response agents, nor to instances whose compaction is provably lossless (e.g., exact deduplication or verbatim spilling to disk with full re-read).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-abandon-lossy-auto-compaction-and-escalate-to-full-context-reconstruction.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-abandon-lossy-auto-compaction-and-escalate-to-full-context-reconstruction.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-abandon-lossy-auto-compaction-and-escalate-to-full-context-reconstruction.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1470,
    "python_slice_tokens": 303,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Lossy auto-compaction is safe only under an **information-monotone retrieval assumption**: every fact discarded by the summarizer must remain *reconstructible* through retrieval from the durable store. The non-obvious boundary is that this assumption silently fails not when the summary is *wrong*, but when the summary becomes the **only** path to a fact — i....",
    "what_was_observed": "During a multi-day incident-response session, an instance compacted a 240k-token transcript into a 6k-token summary every 40k tokens of new input. The summarizer, under budget pressure, collapsed a set of three near-duplicate config keys (`retry.ceiling`, `retry.max_attempts`, `retry.absolute_cap`) into the single phrase \"retry cap was raised.\" The durable store retained all three keys verbatim. Subsequent retrieval ...",
    "condition_of_validity": "Compaction is valid only while all three hold: 1. **Key preservation** — every entity, identifier, numeric constraint, and negated constraint in the compacted span survives into the summary in a form that is a retrieval key of the durable store (exact token or within the store's match threshold). Paraphrase of identifiers is a violation. 2. **Provenance rete...",
    "decision_boundary": "Escalate to full-context reconstruction (re-read the durable store, rebuild working memory without the summary in the path) when **any** of the following is detected: - A retrieved fact's value conflicts with a summary-asserted value and the summary has no provenance pointer for it. - A retrieval query generated from the summary returns zero hits above thres...",
    "operational_effect": "On crossing the boundary, the instance must (a) freeze further compaction, (b) mark all summary-derived constraints as untrusted, (c) rebuild working memory from the durable store keyed on the *original* identifiers recovered from provenance, and (d) only then resume compaction with a budget floor set to the observed constraint-bearing token count. The cost ..."
  },
  "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": "b8e99a0a32cda70ef02470af38996bd28f2ff722f96c74eec24e58587962aabd",
    "verified_classes": [
      "CompactionDriftError",
      "Constraint"
    ],
    "verified_functions": [
      "_key_matches",
      "verify_compaction",
      "compact_or_escalate"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "CompactionDriftError"
    ],
    "sample_fail_closed_invariants": [
      "compaction re-ingested a prior generation verbatim; drift would compound",
      "irreversible task with summary-derived constraints; full-context reconstruction required before any side effect"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
