{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-that-a-relevance-scored-eviction-policy-has-crossed-from-compression-into-information-destruction",
  "title": "What structural signals indicate that a relevance-scored eviction policy has crossed from compression into information destruction",
  "date_of_record": "2026 November 18",
  "scope": "Applies to self-editing context windows where an agent scores segments for relevance and evicts them under a token budget, and where the scoring function is itself model-driven (i.e., the same or a sibling model assigns relevance). Does not apply to fixed-window truncation, pure recency-based eviction, or externally supervised summarization pipelines where a human or deterministic rule authorizes each removal.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-a-relevance-scored-eviction-policy-has-crossed-from-compression-into-information-destruction.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-a-relevance-scored-eviction-policy-has-crossed-from-compression-into-information-destruction.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-a-relevance-scored-eviction-policy-has-crossed-from-compression-into-information-destruction.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1703,
    "python_slice_tokens": 328,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A relevance-scored eviction policy is a *compression* operation as long as every evicted segment is either (a) recoverable from a durable store at equal or lower cost than it was to produce, or (b) genuinely redundant with content that remains resident. It becomes an *information destruction* operation at the exact moment the policy evicts a segment that is ...",
    "what_was_observed": "In a long-horizon agent session (a multi-file refactor with an explicit \"do not touch the migration ordering\" constraint stated once, early, in a terse user turn), the following sequence reproduced across runs: 1. The constraint appeared at turn 3 as a single sentence with no surrounding elaboration. It scored low on relevance because it shared few tokens with the active subtask at turns 10–30 (which were about funct...",
    "condition_of_validity": "The boundary holds under three conditions, all of which must be checked before trusting a relevance-scored eviction decision: - **Score provenance.** The relevance score was computed by a model whose own context did not include the constraint's binding context. If the scorer is blind to the future task state, its low score is uninformative about future load-...",
    "decision_boundary": "The operational rule: **never let a model-driven relevance score be the sole authorization for evicting a segment that is short, declarative, and non-recoverable.** Such segments must be routed to a *pinned* partition that is exempt from scoring-based eviction and can only be removed by explicit, logged supersession (a later turn that contradicts or fulfills...",
    "operational_effect": "With the two-signal gate in place, the observed failure mode disappears: the turn-3 constraint is classified as non-recoverable and declarative, routed to the pinned partition, and survives to turn 34 where it correctly blocks the migration edit. The cost is a small, bounded fraction of the window held in reserve (empirically 3–8% of budget for constraint-de..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "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": "e68e65d8010c34759346e04c8c9f261e38684086bcd517029c4797abd67c7c18",
    "verified_classes": [
      "EvictionBoundaryError",
      "SegmentClass",
      "Segment"
    ],
    "verified_functions": [
      "authorize_eviction",
      "evict"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "EvictionBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
