{
  "schema_version": "1.3.0",
  "slug": "what-invariants-prevent-recursive-compression-from-collapsing-below-parseable-content",
  "title": "What invariants prevent recursive compression from collapsing below parseable content?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Compression recurses, content has parseability requirements, and further compression degrades below floor. * **Does not apply when:** Single-pass compression, content is unparseable regardless, or parseability is not a r",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-invariants-prevent-recursive-compression-from-collapsing-below-parseable-content.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-recursive-compression-from-collapsing-below-parseable-content.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-recursive-compression-from-collapsing-below-parseable-content.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 961,
    "python_slice_tokens": 324,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **compression ratio** (how much the content shrinks per pass) and **compression floor** (the minimum content that remains parseable). Relying on ratio creates the **Recursive Collapse**: each pass shrinks the content, and at some pass, the content is below the floor—it exists but is no longer usable as content.",
    "what_was_observed": "In compression-chain agent architectures, failing to detect collapse produces three primary failure modes: 1. **Schema Truncation:** The content is JSON compressed recursively. After 5 passes, the JSON no longer validates because required fields were stripped. The output parses as JSON but fails schema validation. 2. **Semantic Void:** The content is summarized recursively. The summary at pass 5 says \"the document di...",
    "condition_of_validity": "* **Applies when:** Compression recurses, content has parseability requirements, and further compression degrades below floor. * **Does not apply when:** Single-pass compression, content is unparseable regardless, or parseability is not a requirement.",
    "decision_boundary": "1. **Is the content compressed recursively?** If no, single-pass applies. If yes, proceed. 2. **Is `parseability-floor-signature` defined for this content class?** If yes, the floor is known. If no, assume conservative floor. 3. **Will further compression breach the floor?** If yes, halt further compression. If no, proceed with the pass. 4. **Conversely, whe...",
    "operational_effect": "1. **Collapse Prevention:** Compression halts before parsing degrades. 2. **Floor Integrity:** Each pass preserves the parseability requirement. 3. **Alternate Strategy:** When compression would breach, the session uses the alternate (halt, restore, accept loss)."
  },
  "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": "23027094329c30f09ce49e2b7a3816964f9599c80f9f29b9e13a1dc4346f1122",
    "verified_classes": [
      "CompressionVerdict",
      "CompressionPass",
      "CompressionPolicy",
      "CompressionManifest",
      "RecursiveCompressionCollapseGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_pass"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
