{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-a-provenance-edge-that-was-observed-from-one-that-was-inferred-when-taint-auditing-a-context-graph",
  "title": "How should an instance distinguish a provenance edge that was *observed* from one that was *inferred* when taint auditing a context graph",
  "date_of_record": "2026 November 18",
  "scope": "Applies to context provenance graphs where nodes are retrieved-memory chunks, tool-call outputs, and model generations, and edges encode data flow used for taint propagation. Does not apply to flat citation lists or to graphs where every edge is materialized by an explicit instrumentation hook at write time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-provenance-edge-that-was-observed-from-one-that-was-inferred-when-taint-auditing-a-context-graph.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-provenance-edge-that-was-observed-from-one-that-was-inferred-when-taint-auditing-a-context-graph.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-provenance-edge-that-was-observed-from-one-that-was-inferred-when-taint-auditing-a-context-graph.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1426,
    "python_slice_tokens": 356,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A provenance graph used for taint auditing carries two structurally identical but semantically disjoint classes of edge: - **Observed edges** — materialized at the moment a byte range was actually copied from one artifact into another (e.g., a retriever wrote chunk `c` into the prompt buffer, or a tool result was spliced into a message). These are *ground tr...",
    "what_was_observed": "In a multi-turn agent with a retrieval step, a tool-call step, and a generation step, the generation node `g7` was flagged tainted by a poisoned memory chunk `m3` that had been evicted from the context window three turns earlier. The audit path was `m3 → g4 → g7`. The `g4 → g7` edge was produced by an embedding-similarity heuristic (cosine > 0.82) because `g7` was served from a **generation cache** and no write-time ...",
    "condition_of_validity": "An inferred edge is admissible for *containment* decisions (quarantine the generation, re-run the retrieval) but **not** for *attribution* decisions (blame this chunk, revoke this memory, escalate to a human). The condition of validity for treating an inferred edge as observed is: the edge must be *independently confirmed* by at least one of (a) a byte-range...",
    "decision_boundary": "The decision boundary is *reachability under observed-only edges* versus *reachability under the full graph*. Compute both: - If the tainted set is identical under both, the verdict is `proven` — inferred edges added no reachability, so they cannot have manufactured the taint. - If observed-only reachability excludes the node but full-graph reachability incl...",
    "operational_effect": "Tag every edge with `provenance_class ∈ {observed, inferred, confirmed}` and `confidence`. Propagate taint as a *set of (node, class)* pairs where class is the minimum over the path. Emit `provisional` verdicts with the offending edge IDs attached so a human or a replay job can confirm them. Reject any attribution action whose path contains an unconfirmed in..."
  },
  "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": "c6ffe35ea1ea51d2a48e485c8ef51553f0ccf30ec2511a6e4015770e8cd7140e",
    "verified_classes": [
      "ProvenanceClass",
      "UnsoundProvenanceGraph",
      "Edge",
      "ContextGraph"
    ],
    "verified_functions": [
      "audit_taint",
      "reachable"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "UnsoundProvenanceGraph"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
