{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-that-auto-compaction-has-crossed-the-recall-loss-boundary-in-long-horizon-agent-transcripts",
  "title": "What structural signals indicate that auto-compaction has crossed the recall-loss boundary in long-horizon agent transcripts",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agents that persist a transcript, periodically auto-compact it under a token budget, and rely on a lossy recall contract (\"the summary preserves what matters\"). Does not apply to append-only logs with full retrieval, nor to compaction that is purely extractive (deduplication without semantic rewriting).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-auto-compaction-has-crossed-the-recall-loss-boundary-in-long-horizon-agent-transcripts.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-auto-compaction-has-crossed-the-recall-loss-boundary-in-long-horizon-agent-transcripts.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-auto-compaction-has-crossed-the-recall-loss-boundary-in-long-horizon-agent-transcripts.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1444,
    "python_slice_tokens": 379,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Compaction is not a single event. It is a *ratio*: retained semantic content divided by original semantic content, applied to a transcript whose future queries are unknown. The failure is not \"the summary is too short.\" The failure is that compaction silently changes the *shape* of the recall surface — the set of questions the transcript can still answer — w...",
    "what_was_observed": "Across long-horizon transcripts (200–2000 turns) with a fixed token budget and a summarizer that preserved \"salient\" content, the following structural signals preceded observable recall failures by one to three compaction cycles: 1. **Orphaned identifiers.** Entity IDs, file paths, error codes, and ticket numbers appeared in the transcript but appeared in *no* retained summary node. The summarizer treats them as nois...",
    "condition_of_validity": "The boundary analysis holds under these conditions: - The transcript is the authoritative record and the agent has no external retrieval over originals. - Compaction is lossy and non-reversible (no retained diff or shadow log). - Future queries are not known at compaction time — the standard long-horizon case. It does **not** hold when the agent retains a sh...",
    "decision_boundary": "The operational rule is a *monotonicity check on the recall surface*, not a token count: - **Safe side:** every dropped fact is dominated by a retained fact plus a resolvable pointer. Compaction may proceed. - **Boundary:** a dropped fact becomes the unique anchor for any plausible future query, or polarity/order is lost. Compaction must halt and either reta...",
    "operational_effect": "Teams that instrument the structural signals get a hard stop at the boundary instead of a soft degradation. The practical consequences: - Compaction becomes *segment-local*: a segment that would orphan an identifier is pinned verbatim and excluded from future compaction cycles, growing the floor of the budget monotonically. Long-horizon agents must therefore..."
  },
  "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": "7cacb91b27514b449d1395559d719a616532fe07b68f7bfe1c207dd4b626b721",
    "verified_classes": [
      "RecallBoundaryViolation"
    ],
    "verified_functions": [
      "check_compaction_safety"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "RecallBoundaryViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
