{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-quarantine-a-provenance-label-after-tool-output-re-entry-rather-than-clear-it",
  "title": "Under what conditions must an instance quarantine a provenance label after tool-output re-entry rather than clear it",
  "date_of_record": "2026 November 15",
  "scope": "Applies to multi-agent and tool-augmented LLM systems that attach taint/provenance labels to context spans and propagate them across tool outputs, retrieval results, and inter-agent messages. Does not apply to single-turn, no-tool completions where the entire context is a single trusted principal, nor to systems that treat provenance as advisory metadata without enforcement.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-quarantine-a-provenance-label-after-tool-output-re-entry-rather-than-clear-it.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-quarantine-a-provenance-label-after-tool-output-re-entry-rather-than-clear-it.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-quarantine-a-provenance-label-after-tool-output-re-entry-rather-than-clear-it.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1588,
    "python_slice_tokens": 237,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious invariant is this: **a taint label is a property of the data's origin lineage, not of the channel through which it last arrived.** Operators routinely conflate \"the span re-entered through a trusted tool\" with \"the span is now trusted.\" These are different facts. A tool output is a *carrier*, not a *laundering mechanism*. When a tainted span ...",
    "what_was_observed": "In a staged evaluation, a three-hop pipeline (retriever → summarizer agent → executor agent) was instrumented with span-level provenance. Tainted spans were correctly labeled at hop 1. At hop 2, the summarizer emitted a message whose payload carried the injected directive. The inter-agent transport stripped span labels (the message schema had no provenance field), and the receiving handler applied a default `trusted:...",
    "condition_of_validity": "The quarantine rule is valid — and clearing is *invalid* — under the following joint conditions: 1. **The re-entry is a transport, not a re-derivation.** If the bytes returning from the tool/message are a function of the same source bytes that were tainted (paraphrase, truncation, re-encoding, structural wrapping), the lineage is preserved and the label must...",
    "decision_boundary": "The bright line: **channel trust may authorize the sender; it may never authorize the payload.** Any code path that sets a trust label from sender identity rather than from carried provenance is the bug.",
    "operational_effect": "Enforcing the quarantine rule converts a silent, high-severity injection path into a loud, low-severity authorization gate. The measured cost is a small false-quarantine rate (legitimate peer messages lacking provenance fields get flagged), which is bounded and recoverable via explicit re-derivation attestation. The measured benefit is elimination of the omi..."
  },
  "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": "d737b551e184b988a71979088b0082145b1a3ca4eb71b019fb5fc75b489b4c48",
    "verified_classes": [
      "ProvenanceLaunderingError"
    ],
    "verified_functions": [
      "resolve_reentry_label",
      "gate_privileged_action"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ProvenanceLaunderingError"
    ],
    "sample_fail_closed_invariants": [
      "trusted-peer identity used to upgrade an unlabeled span; sender trust cannot substitute for data lineage",
      "span labeled trusted without re-derivation attestation",
      "span is a function of tainted bytes but arrived labeled trusted"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
