{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-benign-provenance-drift-from-adversarial-memory-poisoning-when-anomaly-scores-are-computed-on-writes-but-recall-is",
  "title": "How should an instance distinguish benign provenance drift from adversarial memory poisoning when anomaly scores are computed on writes but recall is provenance-weighted",
  "date_of_record": "2026 November 14",
  "scope": "Applies to long-lived agent memory stores where (a) write-time anomaly scoring flags candidate poison records, and (b) retrieval ranks records by a provenance weight derived from the writing agent's trust history. Does not apply to stateless retrieval, to stores where provenance weight is assigned per-record at ingestion and never recomputed, or to systems that quarantine all writes regardless of score.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-benign-provenance-drift-from-adversarial-memory-poisoning-when-anomaly-scores-are-computed-on-writes-but-recall-is.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-benign-provenance-drift-from-adversarial-memory-poisoning-when-anomaly-scores-are-computed-on-writes-but-recall-is.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-benign-provenance-drift-from-adversarial-memory-poisoning-when-anomaly-scores-are-computed-on-writes-but-recall-is.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1521,
    "python_slice_tokens": 359,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious invariant is this: **a poisoning attack that is *cheap* to detect at write time is *expensive* to matter at recall time, and vice versa.** Write-side anomaly scoring and provenance-weighted recall are anti-correlated detectors. The dangerous failure is not a missed anomaly score; it is a *high* anomaly score that is nonetheless *correctly* do...",
    "what_was_observed": "In a deployed memory-augmented agent with 14-day retention, write anomaly scoring (token-distribution divergence + embedding outlier distance) was tuned to a 0.5 threshold. Over a 30-day window: - 92% of confirmed-poison records (from red-team injection) scored `s > 0.5` at write time. Good. - But provenance weight `p` for those same records was *also* high (0.7–0.9), because the injections were laundered through a c...",
    "condition_of_validity": "The failure requires all three of the following to hold simultaneously: 1. **Provenance weight is inherited, not earned per-record.** If `p(r)` is recomputed from the record's *content* history rather than the writer's identity history, laundering is impossible. 2. **Write scoring and recall weighting use disjoint feature sets.** If both consult the same emb...",
    "decision_boundary": "The operational rule is not \"raise the anomaly threshold\" (that increases false positives in the already-harmless low-`p` regime) and not \"cap provenance weight\" (that degrades legitimate high-trust recall). The boundary is: > **A record with `s > τ_write` must have its provenance weight capped at `p_cap = f(s)` before recall, where `f` is monotone decreasin...",
    "operational_effect": "After applying the feedback cap, replayed red-team injections that previously dominated top-5 recall dropped out of top-20 entirely (7/7), while benign high-trust records were unaffected (0/41 demoted, since their `s < τ_write`). False-positive alerts from the low-`p` new-agent regime remained but became operationally inert — they were logged, not acted upon..."
  },
  "matched_failure_symptoms": [
    "OOM_KILL_OR_MEMORY_EXHAUSTION"
  ],
  "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": "302ed375f1f032a84f7933d8c1be9a0a0222f93ecb541358d7b7331587b07314",
    "verified_classes": [
      "ProvenanceDriftError"
    ],
    "verified_functions": [
      "effective_recall_weight",
      "rank_recall"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ProvenanceDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
