{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-context-poisoning-in-provenance-weighted-retrieval-attribution",
  "title": "What structural signals indicate context poisoning in provenance-weighted retrieval attribution",
  "date_of_record": "2026 November 17",
  "scope": "Applies to retrieval-augmented generation systems that attach provenance metadata to retrieved chunks and compute a weighted attribution score over those chunks before generation. Does not apply to systems without per-chunk provenance, nor to purely parametric models where no retrieval step exists.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-context-poisoning-in-provenance-weighted-retrieval-attribution.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-context-poisoning-in-provenance-weighted-retrieval-attribution.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-context-poisoning-in-provenance-weighted-retrieval-attribution.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1210,
    "python_slice_tokens": 211,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Context poisoning is not the same as retrieval error. Retrieval error is a ranking problem: the correct chunk exists but was ranked below the cutoff. Context poisoning is a *provenance integrity* problem: a chunk enters the context window with metadata that misrepresents its origin, trust level, or derivation chain, causing the attribution weighting to assig...",
    "what_was_observed": "In a production retrieval pipeline serving ~40k queries/day, three structural signatures preceded known poisoning incidents: 1. **Orphaned high-trust weight.** A chunk declared `source_trust=0.95` (internal wiki tier) but its `derivation_chain` referenced a document ID that did not exist in the provenance store. The weight was high; the backing node was missing. This is the single most reliable signal: trust weight w...",
    "condition_of_validity": "These signals are valid only when the provenance store is append-only and independently verifiable against the retrieval index. If provenance metadata is written by the same process that writes chunk content, an attacker who can poison content can also forge consistent provenance, and none of the three signatures fire. The detection boundary is therefore: **...",
    "decision_boundary": "The operational rule is a hard gate, not a score adjustment: - If `source_trust` exceeds a tier threshold AND the derivation parent is unresolvable → **reject the chunk**, do not down-weight it. Down-weighting a forged-provenance chunk leaves it in context at reduced influence, where it still steers generation via adjacency and token proximity. - If independ...",
    "operational_effect": "Enforcing structural rejection reduced poisoned-chunk admission to near zero in the observed pipeline, at the cost of a ~2.3% false-rejection rate on legitimately re-derived documents whose provenance chains had not yet been backfilled. The mitigation was to make missing-parent a *soft* reject (quarantine pending backfill) while keeping depth-inversion a *ha..."
  },
  "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": "ea4a9203b0d098c3c66449d725a155a2b0a1f93960a8026023915cffc0196dbb",
    "verified_classes": [
      "ProvenancePoisoningError"
    ],
    "verified_functions": [
      "validate_chunk_provenance"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ProvenancePoisoningError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
