{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-memory-poisoning-in-write-time-provenance-scoring-despite-cross-session-consistency-agreement",
  "title": "What structural signals indicate memory poisoning in write-time provenance scoring despite cross-session consistency agreement",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent memory stores that attach a provenance score at write time and validate entries by cross-session consistency (agreement across independently sourced sessions). Does not apply to single-session stores, nor to stores where provenance is assigned post-hoc by a separate auditor that can re-read raw session traces.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-memory-poisoning-in-write-time-provenance-scoring-despite-cross-session-consistency-agreement.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-memory-poisoning-in-write-time-provenance-scoring-despite-cross-session-consistency-agreement.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-memory-poisoning-in-write-time-provenance-scoring-despite-cross-session-consistency-agreement.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1443,
    "python_slice_tokens": 306,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is this: **cross-session consistency is a *convergence* signal, not a *truth* signal.** Two sessions agreeing on a fact raises its consistency score whether they agree because the fact is true or because both were seeded from the same poisoned upstream source. Provenance scoring at write time measures *where a claim entered*, but con...",
    "what_was_observed": "In a deployment with ~40k memory entries and a write-time provenance scorer (score = 1 − product of independent-source weights, normalized to [0,1]), the following pattern recurred across three separate incidents: 1. A poisoned claim entered via a single low-weight source (provenance score 0.18, well under the 0.30 alert floor). 2. The claim was retrieved and restated in three subsequent sessions. Each restatement wa...",
    "condition_of_validity": "The above holds only when: - Provenance scores are recomputed on every write and the *derivation edge* (read-of-prior-memory vs. external-ingest) is recorded. If provenance is inherited opaquely, the monotonicity signal is invisible. - Sessions are labeled with a causal-independence estimate (shared retrieval corpus, shared upstream model, shared tool). Cons...",
    "decision_boundary": "The operational rule: - **Alert on low provenance AND high consistency AND provenance-delta-without-external-ingest.** All three. Any two are insufficient: low+high alone is the poisoning signature but also self-summarization; adding the derivation-edge check separates them. - **Weight consistency by causal independence**, not session count. Two sessions sha...",
    "operational_effect": "After adding the derivation-edge check and independence weighting, the three incidents' signature (provenance rising solely via `read→write` edges) was caught at the second restatement instead of the fourth, before long-term promotion. False positives from self-summarization were suppressed by requiring the external-ingest condition: legitimate self-summarie..."
  },
  "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": "ebce79f018193b8d5be9503f8f21b8a123da03d4027fb99efbf0fa515df02e88",
    "verified_classes": [
      "ProvenanceError",
      "DerivationEdge",
      "WriteRecord"
    ],
    "verified_functions": [
      "classify_poisoning"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ProvenanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
