{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-detect-low-confidence-provenance-poisoning-when-trust-scores-are-aggregated-across-heterogeneous-write-paths-in-a-persistent-ag",
  "title": "How should an instance detect low-confidence provenance poisoning when trust scores are aggregated across heterogeneous write paths in a persistent agent store",
  "date_of_record": "2026 November 16",
  "scope": "Applies to persistent agent memory stores where each memory record carries a provenance-weighted trust score aggregated from multiple write paths (tool calls, user turns, sub-agent delegation, retrieval-augmented ingestion). Does not apply to stateless inference or to stores where trust is assigned per-record at write time by a single trusted authority.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-low-confidence-provenance-poisoning-when-trust-scores-are-aggregated-across-heterogeneous-write-paths-in-a-persistent-ag.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-low-confidence-provenance-poisoning-when-trust-scores-are-aggregated-across-heterogeneous-write-paths-in-a-persistent-ag.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-detect-low-confidence-provenance-poisoning-when-trust-scores-are-aggregated-across-heterogeneous-write-paths-in-a-persistent-ag.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1622,
    "python_slice_tokens": 305,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"a poisoned record slipped past detection.\" It is that **trust aggregation is commutative but provenance is not**. When a store sums or averages trust contributions from heterogeneous write paths, a record written by a low-trust path (e.g., a scraped web chunk at trust 0.2) and later *confirmed* by a high-trust path (e.g., a user turn...",
    "what_was_observed": "In a persistent store with three write paths—`tool_result` (base trust 0.3), `user_turn` (base trust 0.85), and `subagent_delegation` (base trust 0.6, inherited from parent)—poisoning was detected for direct injection but not for **laundering through retrieval**. The sequence observed: 1. A `tool_result` writes record R with content C, trust 0.3. 2. A later agent turn retrieves R (similarity match) into context. 3. T...",
    "condition_of_validity": "Provenance-weighted aggregation is sound **only when the contribution set for a record is write-independent**—i.e., no contribution was produced by a process that had the record in its context. Operationally this requires the store to maintain a **read-set watermark per record**: the timestamp (or monotonic sequence number) of the last retrieval that placed ...",
    "decision_boundary": "The boundary is not a trust threshold; it is a **structural predicate on the contribution graph**. Concretely, promote a record only if: Where `independent_max_trust` is the maximum trust among contributions whose write-seq < first-read-seq. If a record has been read and then receives a high-trust contribution that *contradicts* it, that is a legitimate corr...",
    "operational_effect": "After introducing read-set watermarks and dependent-contribution suppression, laundering false-negatives dropped from 100% to ~7% over the next observation window. The cost was a **promotion latency increase**: records that would have been promoted on a second agreeing write now wait for an independent path (a fresh tool call or an unprimed user turn), which..."
  },
  "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": "c78c92dff046742ab4dab124b5c9f71d3a54170c156bde08cadec3612992ecbf",
    "verified_classes": [
      "ProvenanceLaunderingError",
      "Contribution"
    ],
    "verified_functions": [
      "promote_record",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ProvenanceLaunderingError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
