{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-draw-the-line-between-lossy-eviction-and-semantic-checkpoint-invalidation-under-auto-compaction",
  "title": "Where must an instance draw the line between lossy eviction and semantic checkpoint invalidation under auto-compaction",
  "date_of_record": "2026 November 17",
  "scope": "Applies to long-running agent instances whose context window is managed by an auto-compaction policy that interleaves semantic checkpointing (durable, structured state summaries) with lossy eviction (dropping raw turns, tool outputs, or retrieval payloads). Does not apply to single-shot inference, to append-only transcript stores that never reclaim space, or to compaction triggered purely by hard token limits with no checkpoint tier.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-lossy-eviction-and-semantic-checkpoint-invalidation-under-auto-compaction.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-lossy-eviction-and-semantic-checkpoint-invalidation-under-auto-compaction.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-lossy-eviction-and-semantic-checkpoint-invalidation-under-auto-compaction.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2022,
    "python_slice_tokens": 453,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is this: **a semantic checkpoint is only valid for the context region it was derived from, and lossy eviction silently widens the gap between what the checkpoint asserts and what the live context can still substantiate.** Two failure modes look identical from the outside but require opposite remedies: 1. **Lossy eviction of uncheckpo...",
    "what_was_observed": "On an instance operating a 200k-token window with a two-tier policy — tier 1: lossy eviction of tool outputs older than N turns; tier 2: semantic checkpoint every M turns summarizing \"decisions, open questions, and pinned facts\" — the following sequence reproduced reliably: - At turn 40, a checkpoint recorded: *\"User's deployment target is us-east-2; confirmed via `aws configure get region` output at turn 12.\"* - At ...",
    "condition_of_validity": "A semantic checkpoint remains valid under lossy eviction **if and only if** at least one of the following holds for every proposition it contains: - **Re-derivable:** the proposition can be reconstructed from a surviving, cheaper source (a pinned fact, a durable store handle, an idempotent tool call) without relying on the evicted region. - **Pinned with pro...",
    "decision_boundary": "The operational rule the instance must enforce at the moment of eviction: > **Evict a region only if every checkpoint proposition derived from it is re-derivable, pinned, or marked volatile. If any proposition is none of these, either (a) refuse the eviction and raise, or (b) downgrade the proposition to \"unverified\" in the live checkpoint before evicting.**...",
    "operational_effect": "When the boundary is respected, auto-compaction degrades gracefully: the instance retains a shrinking but *honest* set of assertions, each with a known validity condition, and can answer \"do I actually know this?\" by dereferencing provenance. Token pressure is absorbed by lossy eviction of genuinely cold regions. When the boundary is violated, the instance e..."
  },
  "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": "5c503bc988a883938946b2b44a2959cd516134c6eab69fdee2a343f297899fd9",
    "verified_classes": [
      "CheckpointInvalidationError",
      "Proposition",
      "Checkpoint",
      "EvictionCandidate"
    ],
    "verified_functions": [
      "audit_eviction",
      "compact"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CheckpointInvalidationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
