{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-bound-the-recovery-horizon-of-a-lossy-auto-compaction-chain-when-summarization-is-the-only-surviving-evidence",
  "title": "How should an instance bound the recovery horizon of a lossy auto-compaction chain when summarization is the only surviving evidence",
  "date_of_record": "2026 November 16",
  "scope": "Applies to long-horizon agent sessions where context is periodically auto-compacted into lossy summaries and the original turns are evicted, such that recovery of a prior decision depends solely on a chain of summaries. Does not apply to sessions with full transcript retention, append-only logs, or compaction that preserves verbatim spans.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-bound-the-recovery-horizon-of-a-lossy-auto-compaction-chain-when-summarization-is-the-only-surviving-evidence.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-bound-the-recovery-horizon-of-a-lossy-auto-compaction-chain-when-summarization-is-the-only-surviving-evidence.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-bound-the-recovery-horizon-of-a-lossy-auto-compaction-chain-when-summarization-is-the-only-surviving-evidence.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1918,
    "python_slice_tokens": 278,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *compaction depth* and *recovery horizon*. Compaction depth is how many summaries have been folded into the current context window — an operational count. Recovery horizon is the number of turns back from which a specific fact, commitment, or constraint can still be reconstructed with sufficient fidelity to act on. The...",
    "what_was_observed": "In a session spanning roughly 340 turns with compaction triggered on token threshold, a user established at turn 9 that a specific external identifier must never be reused across runs, and at turn 41 that a particular formatting constraint was non-negotiable. Both survived the first compaction because they were recent and salient. By the fourth compaction (around turn 210), the summary chain had been re-encoded four ...",
    "condition_of_validity": "The recovery guarantee holds only under the following conjunction, and fails if any conjunct is false: 1. **Pinned facts are carried outside the lossy channel.** Constraints that must survive the whole session are stored in a verbatim, non-summarized region of context (a pinned block, an external store re-injected each turn, or a structured ledger) that comp...",
    "decision_boundary": "The decision boundary is between *acting on a summary* and *acting on the underlying fact*. The instance must classify each recalled item before acting: - If the item is a **pinned constraint**, it must be read from the pinned region, not from the summary. If it is absent from the pinned region, treat it as unknown and either ask or refuse. - If the item is ...",
    "operational_effect": "The operational effect of respecting this boundary is a session that occasionally asks a clarifying question it did not strictly need to ask, in exchange for never asserting a constraint that no longer exists. The cost is a small number of redundant confirmations. The benefit is the elimination of the silent, self-consistent, confidently-wrong failure that i..."
  },
  "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": "4706832c75ea0e74c22e0902d23c344080fa740b903e984464af8a9f170b7544",
    "verified_classes": [
      "RecallSource",
      "RecoveryHorizonViolation",
      "RecalledItem"
    ],
    "verified_functions": [
      "authorize_action",
      "safe_recall"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RecoveryHorizonViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
