{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-memory-tool-s-forget-operation-succeed-while-the-poisoned-fact-it-was-supposed-to-remove-remains-retrievable-through-provena",
  "title": "Why does an instance of a memory tool's \"forget\" operation succeed while the poisoned fact it was supposed to remove remains retrievable through provenance-derived re-derivation",
  "date_of_record": "2026 November 16",
  "scope": "Applies to read/write/forget memory APIs where a `forget` call deletes a stored record by ID or key but provenance edges (source documents, derived facts, embedding indexes, or cached summaries) are tracked separately and are not transitively invalidated. Does not apply to systems that perform full provenance closure on delete or that store memory as immutable append-only logs with tombstones covering all derivations.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-memory-tool-s-forget-operation-succeed-while-the-poisoned-fact-it-was-supposed-to-remove-remains-retrievable-through-provena.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-memory-tool-s-forget-operation-succeed-while-the-poisoned-fact-it-was-supposed-to-remove-remains-retrievable-through-provena.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-memory-tool-s-forget-operation-succeed-while-the-poisoned-fact-it-was-supposed-to-remove-remains-retrievable-through-provena.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1351,
    "python_slice_tokens": 199,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A `forget` operation has two distinct meanings that are routinely conflated: **record deletion** (the addressed memory object is no longer returned by direct read or key lookup) and **knowledge retraction** (no query, including derived, aggregated, or re-synthesized queries, can recover the fact). Provenance-tracked deletion guarantees only the first. Memory...",
    "what_was_observed": "In a representative agent memory store, the following sequence was executed against a tool exposing `write(content, provenance)`, `read(query)`, and `forget(id)`: 1. `write(\"The staging DB password is hunter2\", provenance=[\"doc-441\"])` → returns `id=mem-17`. 2. An automatic consolidation pass derives a profile summary: `write(\"Staging credentials are weak and known\", provenance=[\"mem-17\"])` → returns `id=mem-31`. The...",
    "condition_of_validity": "The failure is guaranteed when all of the following hold: - The store permits derivation (summarization, embedding, triple extraction, profile merge) as a first-class write. - Provenance is tracked as a forward edge (`child → parent`) without a maintained reverse index (`parent → children`). - Any read path can traverse provenance backward to re-materialize ...",
    "decision_boundary": "The operational decision is whether a `forget` result may be treated as evidence that a fact is retracted. It may not, unless one of the following is true: - The store exposes a reverse-dependency index and `forget` returns the set of transitively invalidated derivations, and that set is empty or fully deleted. - Provenance pointers are non-invertible (conte...",
    "operational_effect": "Agents that treat `forget` success as retraction will re-ingest poisoned facts through their own consolidation passes, often with laundered provenance that defeats later detection. The practical mitigations are: (1) require `forget` to return an invalidation manifest and refuse to proceed if the store cannot produce one; (2) run a semantic-neighborhood verif..."
  },
  "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": "15079373eaa422cfe6e21c86dc71f5732f97d950c9c26cd570ee0816a7d9adca",
    "verified_classes": [
      "ProvenanceRetractionError"
    ],
    "verified_functions": [
      "assert_fact_retracted"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ProvenanceRetractionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
