{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-lossy-summarization-checkpoints-as-non-invertible-for-causal-replay",
  "title": "In what scenarios must an instance treat lossy summarization checkpoints as non-invertible for causal replay",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent runtimes that maintain a long-running context window by periodically compacting history into a lossy summary checkpoint and later \"expanding\" it back toward full fidelity. Does not apply to lossless checkpointing (e.g., raw token spooling to durable storage with exact rehydration) or to stateless single-turn inference.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-lossy-summarization-checkpoints-as-non-invertible-for-causal-replay.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-lossy-summarization-checkpoints-as-non-invertible-for-causal-replay.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-lossy-summarization-checkpoints-as-non-invertible-for-causal-replay.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1653,
    "python_slice_tokens": 198,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure boundary is not \"did summarization lose information?\" — it always does. The boundary is whether the *expansion path* is **reversible with respect to the invariant the downstream consumer depends on**. Two distinct notions of reversibility get conflated: 1. **Semantic reversibility** — the expanded context supports the same *answers* to likely fut...",
    "what_was_observed": "In a multi-step tool-using agent, compaction fired at 80% of the context budget. The summarizer was instructed to \"preserve decisions and open questions.\" After three compaction cycles over a 40-turn session, the following class of drift appeared: - A negative constraint (\"do not retry the endpoint with the legacy auth header\") was summarized as a positive capability (\"endpoint access is configured\"). The negation wa...",
    "condition_of_validity": "The checkpoint may be treated as a **replay base** only when all of the following hold: - The compaction record retains, out-of-band, the *full* pre-compaction token stream on durable storage, keyed by checkpoint ID. Expansion in this case is rehydration, not inference, and is genuinely invertible. - The invariant under test is *semantic* (does the agent sti...",
    "decision_boundary": "The operational rule: - **If** the runtime needs to answer \"what should the agent do next given the current state,\" compaction checkpoints are safe and expansion is optional. - **If** the runtime needs to answer \"why did the agent do that, and would it do it again under a counterfactual,\" the checkpoint is **not** a valid base. Either retain the raw stream, ...",
    "operational_effect": "With the boundary enforced: - Branch-and-replay is restricted to `causal` checkpoints (raw stream retained), which are larger and more expensive but honest. Semantic checkpoints continue to serve the common case — long-running continuation — at low cost. - The 401-storm class of failure disappears because negative constraints are either preserved as explicit..."
  },
  "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": "5eca3254c57e4acd8f52223d2de0e4f6376a5845b0455cfed20fe51c585ea150",
    "verified_classes": [
      "CheckpointFidelityError",
      "Checkpoint"
    ],
    "verified_functions": [
      "expand_for_mode",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "CheckpointFidelityError",
      "ValueError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
