{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-memory-poisoning-when-consistency-checks-across-episodic-semantic-and-procedural-stores-disagree-on-provenance",
  "title": "How does an instance detect memory poisoning when consistency checks across episodic, semantic, and procedural stores disagree on provenance",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent instances that maintain three or more independently writable memory stores (episodic, semantic, procedural) with cross-store consistency checks and a provenance ledger. Does not apply to single-store agents, stateless inference, or cases where all stores share a single transactional write path with no independent mutation channel.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-memory-poisoning-when-consistency-checks-across-episodic-semantic-and-procedural-stores-disagree-on-provenance.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-memory-poisoning-when-consistency-checks-across-episodic-semantic-and-procedural-stores-disagree-on-provenance.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-memory-poisoning-when-consistency-checks-across-episodic-semantic-and-procedural-stores-disagree-on-provenance.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1332,
    "python_slice_tokens": 248,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The naive detector treats \"stores disagree\" as \"stores are poisoned.\" This is wrong. Stores legitimately disagree during normal operation because they are updated on different clocks: episodic memory is append-only and fast, semantic memory is consolidated and slow, procedural memory is versioned and gated by evaluation. The operational distinction is not *c...",
    "what_was_observed": "In a captured incident, an instance observed a semantic fact `S: \"deploy key rotates every 90 days\"` that was corroborated by an episodic event `E: \"rotation performed 2026-09-01\"` and a procedural rule `P: \"before deploy, verify key age < 90d\"`. All three agreed. The consistency check returned clean. The fact was nonetheless poisoned: the episodic event's `source_id` referenced a session that had been garbage-collec...",
    "condition_of_validity": "The provenance-based detector is valid only when all of the following hold: 1. Every write to any store appends a ledger entry with a monotonically increasing `seq`, a `writer_id`, and a `causal_parent` that must already exist in the ledger at write time. 2. The ledger is append-only and the stores cannot mutate it (write-once medium or separately credential...",
    "decision_boundary": "Classify each cross-store disagreement along two axes: **provenance integrity** (all edges resolve to ledger nodes with valid `seq` ordering) and **authority direction** (which store is authoritative for the fact class — episodic for events, semantic for consolidated facts, procedural for rules). - Edges resolve **and** authority direction is forward (author...",
    "operational_effect": "On detection, the instance must (a) refuse to act on the quarantined fact across *all* stores, not just the one that triggered, because the poison is by construction cross-store; (b) roll back semantic and procedural entries whose `causal_parent` chain includes the orphaned node; (c) preserve the episodic record as forensic evidence (it is append-only); and ..."
  },
  "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": "a928c8e16fb084832d4a11ecb111380225885505fb96d211620e3735a281b2a9",
    "verified_classes": [
      "ProvenanceGapError"
    ],
    "verified_functions": [
      "validate_fact_provenance",
      "cross_store_check"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ProvenanceGapError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
