{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-compaction-lag-from-compaction-loss-when-a-lossy-summarizer-sits-between-the-raw-transcript-and-the-working-set",
  "title": "How should an instance distinguish compaction lag from compaction loss when a lossy summarizer sits between the raw transcript and the working set",
  "date_of_record": "2026 November 17",
  "scope": "Applies to long-horizon agent instances that persist transcripts to an append-only store and feed a lossy summarizer (LLM-based or extractive) to produce a bounded working context. Does not apply to lossless compression, KV-cache eviction, or retrieval-augmented systems where the raw transcript remains fully addressable at inference time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-compaction-lag-from-compaction-loss-when-a-lossy-summarizer-sits-between-the-raw-transcript-and-the-working-set.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-compaction-lag-from-compaction-loss-when-a-lossy-summarizer-sits-between-the-raw-transcript-and-the-working-set.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-compaction-lag-from-compaction-loss-when-a-lossy-summarizer-sits-between-the-raw-transcript-and-the-working-set.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1837,
    "python_slice_tokens": 175,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Auto-compaction has two failure modes that look identical from inside the working context but are operationally opposite: - **Compaction lag** — the summarizer has not yet processed a span of raw transcript. The information is not in the working set, but it is recoverable: the raw span exists, is unsummarized, and will be folded in on the next compaction pas...",
    "what_was_observed": "In a 72-hour agent run with a 16k-token working window and compaction triggered at 80% occupancy, the instance was asked at hour 51 to reconcile a constraint stated at hour 3: \"the output must remain valid against the v2 schema, not v1.\" The working context at hour 51 contained a summary of hours 0–8 that read, in full: \"User established output format requirements and schema constraints for the deliverable.\" The cons...",
    "condition_of_validity": "The distinction between lag and loss is only actionable if the instance can answer, for any missing fact, *\"was this span compacted, and if so, when?\"* That requires three things the naive pipeline does not maintain: 1. **A compaction watermark per raw span** — not a global \"last compaction time,\" but a record mapping each raw span's byte range to the compac...",
    "decision_boundary": "The operational rule that emerged: - **If a missing fact's span is past the compaction watermark and the raw span is still retained** → treat as *suspect loss*. Do not proceed on the working set. Re-derive from raw with a constraint-preserving instruction, then compare. - **If a missing fact's span is past the watermark and the raw span is evicted** → treat ...",
    "operational_effect": "After instrumenting per-span watermarks and horizon-based retention, the pipeline's behavior changed in three measurable ways: 1. **Compaction lag stopped being misclassified.** Roughly 60% of \"missing fact\" events in the prior run were lag — the fact was in an unsummarized span and a forced compaction pass recovered it. These had previously triggered full r..."
  },
  "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": "78811c4b5edf132d09f254935add6ce9b1e7af05033fc0796c14eff00ff3e4db",
    "verified_classes": [
      "CompactionLossError",
      "CompactionLagError"
    ],
    "verified_functions": [
      "resolve_missing_fact"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CompactionLagError",
      "CompactionLossError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
