{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-that-automatic-context-compaction-has-silently-violated-the-summarization-invariant",
  "title": "What structural signals indicate that automatic context compaction has silently violated the summarization invariant",
  "date_of_record": "2026 November 17",
  "scope": "Applies to any agent runtime that performs automatic context compaction or summarization when a fixed token budget is approached, where the compacted representation is subsequently used as the sole working memory for downstream reasoning. Does not apply to systems that retain the full transcript in an addressable store and merely window it, nor to systems that perform lossless extraction (verbatim span selection) rather than generative summarization.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-automatic-context-compaction-has-silently-violated-the-summarization-invariant.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-automatic-context-compaction-has-silently-violated-the-summarization-invariant.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-that-automatic-context-compaction-has-silently-violated-the-summarization-invariant.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2031,
    "python_slice_tokens": 357,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct failure classes in budget-driven compaction, and they are routinely conflated: 1. **Budget overflow** — the compacted artifact still exceeds the allocated token budget. This is loud: the next assembly step fails a length check, or the model truncates, or the request is rejected. It is detectable by arithmetic. 2. **Invariant violation ...",
    "what_was_observed": "Across repeated compaction cycles on long-running agent sessions (transcripts of 40k–200k tokens compacted into 2k–8k token budgets), the following structural signals preceded downstream errors with high reliability. They are properties of the *summary text and its relationship to the transcript*, not of the model's self-report, which is uninformative (compaction models report high fidelity on summaries that have dro...",
    "condition_of_validity": "These signals are valid indicators *only* under the following conditions, and the operator must check them before acting on the signals: - The transcript is available for comparison. If compaction is irreversible and the source is discarded, the signals below cannot be computed and the system is unfalsifiable — treat every compaction as suspect. - The downst...",
    "decision_boundary": "The operational rule that separates safe from unsafe compaction: - **Compact when** the projected kernel is provably free of dereferenced facts — i.e., every negation, numeric bound, open obligation, and entity definition survives verbatim or as a structured field, and every definite reference in the summary resolves within the summary. - **Refuse and re-exp...",
    "operational_effect": "Systems that instrument these structural signals before accepting a compaction artifact convert a silent, delayed, confidently-wrong failure into a loud, immediate, recoverable one. The practical effects observed: - Negation-collapse and dangling-reference checks catch the majority of constraint-dropping compactions at accept time, before any downstream acti..."
  },
  "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": "186148401603036aec48604929215210f4c8a6626ac18b4073f1cf68be9005a7",
    "verified_classes": [
      "CompactionInvariantError",
      "ConstraintLedger"
    ],
    "verified_functions": [
      "_clause_contains",
      "validate_compaction",
      "compact_cycle",
      "carry_forward"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "CompactionInvariantError"
    ],
    "sample_fail_closed_invariants": [
      "no summary produced; refusing to proceed empty"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
