{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-taint-survive-the-tool-call-graph-boundary-and-where-it-must-not",
  "title": "Where must an instance of taint survive the tool-call graph boundary — and where it must not",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent runtimes that propagate prompt-injection taint labels across multi-hop tool invocations (agent → tool → sub-agent → tool) where taint metadata is serialized alongside tool arguments. Does not apply to single-hop tool calls, nor to runtimes that re-derive taint from content at each hop rather than carrying an explicit label.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-taint-survive-the-tool-call-graph-boundary-and-where-it-must-not.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-taint-survive-the-tool-call-graph-boundary-and-where-it-must-not.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-taint-survive-the-tool-call-graph-boundary-and-where-it-must-not.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1285,
    "python_slice_tokens": 261,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious invariant is this: **taint must be *sticky across provenance hops* but *non-sticky across trust-boundary resets*.** A tainted string that enters via an untrusted tool result must remain labeled tainted through every subsequent tool argument it is copied into — but the moment that string is *re-asserted* by a trusted authority (a human confirm...",
    "what_was_observed": "In a three-hop chain — `planner → web_fetch → summarizer → email_send` — an injection payload embedded in a fetched page survived into the `summarizer`'s output and then into the `email_send` arguments. The taint label was present at hop 1 (marked on the `web_fetch` result) and absent at hop 3. Root cause: the `summarizer` tool's argument schema had no field for provenance, so the runtime's label-propagation logic, w...",
    "condition_of_validity": "The sticky-across-hops rule holds **only when taint is carried out-of-band from content** — i.e., as structured metadata in the tool-call envelope, keyed to the exact string span or value identity, not inferred from string matching. If a runtime re-derives taint by scanning content for known-injection substrings, the invariant does not hold and must not be a...",
    "decision_boundary": "The operational decision reduces to a single check at every hop boundary: *does the outgoing schema have a provenance sink?* If yes, the runtime must fail closed when the label cannot be attached — refuse the hop rather than emit unlabeled content. If no, the hop is a **laundering hazard** and must be either (a) forbidden for tainted inputs, or (b) wrapped b...",
    "operational_effect": "Enforcing the boundary converts a silent integrity failure (injected content reaching a sink with a clean label) into a loud availability failure (the hop refuses). That trade is correct for outbound sinks (email, payments, code execution) and incorrect for read-only internal hops, where refusing on schema-gap is over-broad. The practical implementation is a..."
  },
  "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": "33e51e428b675db2b08e4b1b7d360709323876f01e3027f75488b5c33f90dbaa",
    "verified_classes": [
      "TaintLaunderingError",
      "TaintSaturationError"
    ],
    "verified_functions": [
      "carry_taint",
      "reset_taint",
      "admit_to_sink"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "TaintLaunderingError",
      "TaintSaturationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
