{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-to-re-derive-sanitized-output-from-tainted-intermediate-state-rather-than-sanitizing-at-the-point-of-emissio",
  "title": "In what scenarios must an instance refuse to re-derive sanitized output from tainted intermediate state rather than sanitizing at the point of emission",
  "date_of_record": "2026 November 16",
  "scope": "Applies to tool-augmented LLM pipelines where outputs are composed from multiple tool calls with per-span taint labels and at least one downstream re-derivation step (summarization, reformatting, aggregation, or code generation) that consumes prior model output. Does not apply to single-shot, single-tool pipelines with no intermediate model-authored state, nor to pipelines where every emission point is a hard trust boundary with no post-processing.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-re-derive-sanitized-output-from-tainted-intermediate-state-rather-than-sanitizing-at-the-point-of-emissio.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-re-derive-sanitized-output-from-tainted-intermediate-state-rather-than-sanitizing-at-the-point-of-emissio.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-re-derive-sanitized-output-from-tainted-intermediate-state-rather-than-sanitizing-at-the-point-of-emissio.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1786,
    "python_slice_tokens": 357,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The common mental model of taint tracking is: tag data at ingress, propagate labels through transformations, and strip or escape tainted spans at the final emission boundary. This is sound only when the sanitization function is idempotent and *label-preserving under re-derivation*. The boundary failure is that a downstream model step can *launder* taint by r...",
    "what_was_observed": "In a pipeline where a retrieval tool returned documents with an `untrusted` taint label and a subsequent `summarize` step consumed those documents plus a clean system prompt, the summarizer faithfully reproduced a numeric threshold (\"retry budget is 3\") that originated in an untrusted document. The taint label was attached to the source document's character range. The summarizer's output was a new string with no over...",
    "condition_of_validity": "Emission-point sanitization is valid if and only if all of the following hold: 1. **Span provenance is preserved** across every transformation between labeling and emission. Any step that invokes a model to rewrite text violates this unless the model output is re-tainted as a whole. 2. **The sanitization function is idempotent** and commutes with the transfo...",
    "decision_boundary": "The operational decision is: **when a re-derivation step's output is about to be emitted, do you sanitize the output spans, or do you refuse to emit and re-derive from clean sources?** Refuse-and-re-derive is required when the re-derivation consumed any tainted input and the output space can encode arbitrary content (free text, structured data, code). In thi...",
    "operational_effect": "Pipelines that enforce whole-output tainting on re-derivation see a measurable drop in \"clean\" emissions from summarization and reformatting steps, because those steps now frequently produce quarantined output. This is expected and correct. The cost is throughput on tainted paths; the benefit is that the laundering class of failures — where a sanitizer repor..."
  },
  "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": "33283c5bf3d7719b4eea82392cb40e35ede54c4e6569b155f3f84c18808fc339",
    "verified_classes": [
      "TaintLaunderingError",
      "Labeled"
    ],
    "verified_functions": [
      "rederive",
      "emit_sanitized",
      "pipeline_step",
      "tainted"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "TaintLaunderingError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
