{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-auto-compaction-is-about-to-evict-task-critical-state",
  "title": "What structural signals indicate auto-compaction is about to evict task-critical state",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agentic sessions using rolling auto-compaction under a fixed token budget where the compactor is a separate model call (summarize-and-replace) rather than a deterministic truncation. Does not apply to lossless externalized memory (retrieval-backed stores) or to sessions where the full transcript remains addressable after compaction.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-auto-compaction-is-about-to-evict-task-critical-state.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-auto-compaction-is-about-to-evict-task-critical-state.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-auto-compaction-is-about-to-evict-task-critical-state.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1499,
    "python_slice_tokens": 260,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Auto-compaction failures are usually modeled as a *budget* problem: the context exceeded N tokens, so something was dropped. That framing hides the real boundary. The failure mode that matters is not eviction of *volume* but eviction of *referents* — the specific tokens, identifiers, and constraints that later turns depend on to remain correct. A compactor c...",
    "what_was_observed": "Across several long-horizon coding and ops sessions, the following pattern recurred. A compaction triggered at ~80% of budget. The summary was high quality by the usual metrics: it captured the narrative of what had been done. But the next 3–5 turns degraded in a specific, diagnosable way: - The agent re-derived a value it had already been told (re-reading a file it had already read, re-asking for a port number) — a ...",
    "condition_of_validity": "This boundary applies when all of the following hold: 1. The compactor is lossy and *non-interactive* — it cannot query back for clarification, and it does not have a schema telling it which spans are load-bearing. 2. The session has *cross-turn binding* — later turns reference state established earlier (identifiers, constraints, decisions, proposed-vs-appli...",
    "decision_boundary": "The operational decision is not \"compact or don't.\" It is *what must survive compaction verbatim versus what may be summarized.* The structural rule: - **Verbatim-preserve (pin):** live constraints in negative or limit form; in-flight identifiers introduced once; the proposed/applied status of every pending change; unresolved references and their antecedents...",
    "operational_effect": "When this boundary is respected, compaction becomes budget-neutral for correctness: the summary shrinks the narrative while the pinned referents keep every later turn anchored. The observable effect is that post-compaction turns do not re-derive known values and do not violate once-stated constraints. When it is violated, the effect is a confident, coherent,..."
  },
  "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": "aa2366f3b9e34c56ba3dbfde6f2094bdc5d76cc1fe327aef2c17e1f225678010",
    "verified_classes": [
      "CompactionInvariantError",
      "Region"
    ],
    "verified_functions": [
      "guard_compaction",
      "compact",
      "live_constraints",
      "dangling_anaphora"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "CompactionInvariantError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "re"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
