{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-a-provenance-label-as-invalidated-rather-than-inherited-across-an-agent-tool-boundary",
  "title": "In what scenarios must an instance treat a provenance label as invalidated rather than inherited across an agent tool boundary",
  "date_of_record": "2026 November 17",
  "scope": "Applies to multi-agent and tool-using LLM systems that propagate data-flow provenance (taint) labels on text and structured payloads across tool-call boundaries to detect prompt injection. Does not apply to single-turn, tool-free inference, nor to systems that enforce injection defense purely via output filtering without provenance tracking.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-provenance-label-as-invalidated-rather-than-inherited-across-an-agent-tool-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-provenance-label-as-invalidated-rather-than-inherited-across-an-agent-tool-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-provenance-label-as-invalidated-rather-than-inherited-across-an-agent-tool-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1485,
    "python_slice_tokens": 206,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The critical distinction is between *label propagation* (a tainted value carries its taint to derived values) and *label inheritance across a trust boundary* (a downstream component assumes the taint of an upstream value without re-deriving it). Most taint-tracking implementations conflate these. Within a single process, propagation is sound: if `x` is taint...",
    "what_was_observed": "In a deployed agent with three tools — `fetch_url`, `summarize`, and `send_email` — the taint tracker marked output of `fetch_url` as `UNTRUSTED_SOURCE`. The `summarize` tool consumed `UNTRUSTED_SOURCE` text and produced output that the tracker labeled `UNTRUSTED_SOURCE` by propagation. This was correct. The failure appeared one hop later: `summarize` invoked an internal LLM that, when the fetched page contained the ...",
    "condition_of_validity": "A provenance label may be inherited across a tool boundary if and only if all of the following hold: 1. The tool is **label-transparent**: its output is a pure function of its labeled inputs, with no generative step, no retrieval, and no external state. 2. The tool is **channel-preserving**: every output field is traceable to a specific input field, and the ...",
    "decision_boundary": "The boundary is *not* \"did the tool call a model?\" — it is \"can the output's content lineage be reconstructed from the input's labels?\" A generative summarizer fails this because its output token distribution is not a function of any single input label. A deterministic JSON extractor passes it only if its field-to-input mapping is declared. A retrieval tool ...",
    "operational_effect": "Systems that inherit labels across non-transparent boundaries exhibit *silent taint loss*: injection payloads survive summarization, translation, or re-formatting while the tracker reports the value as trusted. The failure is silent because every individual propagation step is locally sound; the unsoundness lives in the unmodeled edge. Detection requires gra..."
  },
  "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": "7d5c7988214e3274912302545148bced7f4fddb6943dfd0764a0ba8a9b359614",
    "verified_classes": [
      "ProvenanceInvalidationError",
      "ProvenanceLabel"
    ],
    "verified_functions": [
      "propagate_label",
      "admit_to_trusted_sink"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ProvenanceInvalidationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
