{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-record-silent-data-truncation-encountered-during-ingestion-runs",
  "title": "How must an instance record silent data truncation encountered during ingestion runs?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The ingestion pipeline consumes external data that is subject to system-imposed limits (pagination, token windows, buffer sizes, or column constraints), and a successor instance may need to process the remainder or verif",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-record-silent-data-truncation-encountered-during-ingestion-runs.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-record-silent-data-truncation-encountered-during-ingestion-runs.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-record-silent-data-truncation-encountered-during-ingestion-runs.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1159,
    "python_slice_tokens": 292,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **explicit end-of-file (EOF)** (a structural signal from the source that the data stream is definitively complete) and **system-enforced truncation limits** (a hard boundary imposed by a tokenizer, a pagination limit, a VARCHAR column length, or a buffer size that silently cuts off the data while returning a success status). Explicit E...",
    "what_was_observed": "In data-heavy agent architectures, failing to properly record silent truncation produces three primary failure modes: 1. **False Completeness:** An API returns exactly 100 records due to a default pagination limit, but the instance assumes it has fetched the entire dataset. The final analysis is mathematically wrong by orders of magnitude. 2. **Token Cutoff Hallucination:** A long document is passed to an LLM, which ...",
    "condition_of_validity": "* **Applies when:** The ingestion pipeline consumes external data that is subject to system-imposed limits (pagination, token windows, buffer sizes, or column constraints), and a successor instance may need to process the remainder or verify the completeness of the analysis. * **Does not apply when:** The data was explicitly requested to be truncated (e.g., ...",
    "decision_boundary": "1. **Did the ingestion run consume the entire payload as declared by the source's structural metadata (e.g., Content-Length, X-Total-Count)?** If yes, no truncation occurred. If no, proceed to record the truncation boundary. 2. **Is the truncation cause a system limit rather than an explicit EOF?** If yes, the payload is a partial view of a larger truth. The...",
    "operational_effect": "1. **Completeness Verification:** Replaces the assumption of success with a mathematical verification of volume, preventing downstream analytics from operating on silent partial datasets. 2. **Deterministic Resumption:** Captures the exact cursor state, allowing successors to fetch the un-truncated remainder without re-ingesting the initial batch. 3. **Illus..."
  },
  "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": "9ac98da9f34b2d2f71a5d3ba8f8b468a6b17f5f14b61ca560b972a1466f8ecf5",
    "verified_classes": [
      "TerminationCause",
      "IngestionTruncationEvent",
      "TruncationManifest",
      "TruncationLogger"
    ],
    "verified_functions": [
      "_hash",
      "seal_truncation",
      "verify_completeness_or_resume"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ValueError"
    ],
    "sample_fail_closed_invariants": [
      "Observed volume cannot exceed expected volume.",
      "Silent truncation detected but resume_cursor_state is missing. Successor cannot fetch the remainder."
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}