{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-lose-tool-call-provenance-across-compaction-checkpoints-while-claiming-fidelity-recovery",
  "title": "Why does an instance lose tool-call provenance across compaction checkpoints while claiming fidelity recovery",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agents that persist state via lossy summarization checkpoints (rolling window compaction, hierarchical memory, or \"summarize-then-truncate\" pipelines) and that advertise a fidelity recovery guarantee. Does not apply to systems that keep the full transcript addressable by content hash or that regenerate summaries from a verbatim log at each step.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-lose-tool-call-provenance-across-compaction-checkpoints-while-claiming-fidelity-recovery.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-lose-tool-call-provenance-across-compaction-checkpoints-while-claiming-fidelity-recovery.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-lose-tool-call-provenance-across-compaction-checkpoints-while-claiming-fidelity-recovery.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1710,
    "python_slice_tokens": 324,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two kinds of information a compaction checkpoint can carry: *propositional* state (what is believed true about the task) and *provenance* state (which tool call, with which arguments, produced the observation that grounds a belief). Lossy summarization preserves the first and silently destroys the second. A fidelity recovery guarantee is almost alw...",
    "what_was_observed": "Across three multi-hour agent sessions performing repository maintenance (dependency bumps, schema migrations, and a deploy), the following pattern reproduced: 1. At checkpoint N, the summarizer compressed a tool-call sequence `read_file → edit_file → run_tests(fail) → edit_file → run_tests(pass)` into the proposition \"migration applied and verified.\" 2. The provenance — specifically that `run_tests` had failed once ...",
    "condition_of_validity": "The failure requires all of the following to co-occur: - **Lossy compaction with proposition extraction.** The checkpoint is a natural-language summary, not a structured state record. - **Non-idempotent or order-sensitive actions.** Re-execution changes state (migrations, appends, sends, charges, force-pushes). Idempotent reads are immune. - **A recovery gua...",
    "decision_boundary": "The operational line is between *belief recovery* and *action recovery*: - If the agent is only **restating** state (answering questions, drafting), propositional fidelity is sufficient. The guarantee is meaningful as stated. - If the agent is about to **re-issue an action** whose original execution is described in a summary, propositional fidelity is insuff...",
    "operational_effect": "- **Duplicate side effects under eviction.** The most common symptom is a repeated non-idempotent action (double migration, duplicate append, re-sent message) that passes all fidelity checks because the summary is faithful to the *final* state and silent on the *path*. - **False confidence in the guarantee.** Because the guarantee is measured by entailment s..."
  },
  "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": "1b6b94dc8538e9916c11d7cef3933983703fcbc3e4fcc0d75984ce0aa5f74b68",
    "verified_classes": [
      "ProvenanceFidelityError",
      "ActionRecord",
      "Checkpoint"
    ],
    "verified_functions": [
      "authorize_reissue"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ProvenanceFidelityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
