{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-reject-a-tainted-sink-write-when-the-label-set-is-empty-but-the-provenance-chain-is-not",
  "title": "Where must an instance reject a tainted sink write when the label set is empty but the provenance chain is not",
  "date_of_record": "2026 November 17",
  "scope": "Applies to taint-aware tool sandboxes that gate sink invocations (network egress, filesystem writes, subprocess spawn, message send) on the label set attached to the argument payload. Does not apply to pure information-flow monitors that track provenance independently of label sets, nor to sandboxes that treat unlabeled data as implicitly public.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-tainted-sink-write-when-the-label-set-is-empty-but-the-provenance-chain-is-not.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-tainted-sink-write-when-the-label-set-is-empty-but-the-provenance-chain-is-not.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-tainted-sink-write-when-the-label-set-is-empty-but-the-provenance-chain-is-not.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1394,
    "python_slice_tokens": 278,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure lives in the gap between two distinct questions a sink policy can ask: 1. **\"Is the current label set non-empty?\"** — a set-membership test over the labels attached to the value at the moment the sink is called. 2. **\"Does the value's provenance chain terminate at a sensitive source?\"** — a reachability test over the derivation graph, independent...",
    "what_was_observed": "An agent tool-sandbox was configured with a sink policy: `network.egress` denies payloads whose label set intersects `{PII, SECRET, INTERNAL}`. A summarization tool read a `SECRET`-labeled config blob, produced a `dict`, and passed it through a redaction helper that returned a fresh `dict` with the same keys but scrubbed values. The redaction helper constructed its output with `{k: redact(v) for k, v in src.items()}`...",
    "condition_of_validity": "The label-set-only test is valid only under the conjunction: - Every transformation that produces a new value either (a) propagates the union of input labels, or (b) is registered in an allowlist of label-clearing transformations whose *semantic* effect is proven to remove the sensitive content, not merely the label. - No code path constructs a value from a ...",
    "decision_boundary": "The decision boundary for the sink evaluator: - **Permit** iff `provenance(payload) ∩ sensitive_sources == ∅`. - **Deny** iff `provenance(payload) ∩ sensitive_sources ≠ ∅` AND the transformation edge from the sensitive source to the payload is not in the authorized-clearing allowlist. - **Deny (fail-closed)** iff the provenance chain is *unavailable* — a val...",
    "operational_effect": "Enforcing the provenance-chain rule converts a class of silent over-permission into an explicit, auditable denial. The operational cost is that every value crossing a tool boundary must carry a derivation record, which forces the sandbox to instrument value construction rather than value labeling — a larger surface, but one that cannot be bypassed by a compr..."
  },
  "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": "0801a9a782764833d3b81fba91ddfb10be62fc47c6557dc169463a68f80eabce",
    "verified_classes": [
      "TaintedSinkError",
      "Provenance",
      "SinkPolicy"
    ],
    "verified_functions": [
      "guarded_egress",
      "evaluate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "TaintedSinkError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
