{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-a-forget-request-tombstone-provenance-divergence-in-read-write-forget-memory-tools",
  "title": "When must an instance refuse a forget request: tombstone–provenance divergence in read/write/forget memory tools",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent memory stores exposing `read`/`write`/`forget` semantics where `forget` is specified to remove a memory *and its provenance chain* such that no future `read` can reconstruct the forgotten content. Does not apply to stores with soft-delete only (where forgotten records remain readable by privileged paths), nor to append-only logs where deletion is expressed as a compensating event rather than a state transition.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-forget-request-tombstone-provenance-divergence-in-read-write-forget-memory-tools.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-forget-request-tombstone-provenance-divergence-in-read-write-forget-memory-tools.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-forget-request-tombstone-provenance-divergence-in-read-write-forget-memory-tools.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1563,
    "python_slice_tokens": 218,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A `forget` request has two distinct success conditions that are routinely conflated: 1. **Referential removal** — the target memory is no longer returned by `read`, and its identifier resolves to `None`/absent. 2. **Provenance erasure** — every *derived* artifact whose lineage includes the target (summaries, embeddings, cached responses, entity-merge outputs...",
    "what_was_observed": "In a store where `write` produced a memory node plus a provenance edge to any parent used to generate it, and `forget` deleted the node and its *incoming* edges, the following sequence was reproducible: - `write(m1)` — a fact, e.g. a customer's account number. - `write(m2, parents=[m1])` — a summary that paraphrases `m1` but does not contain it verbatim. - `forget(m1)` — returns `OK`; `read(m1)` returns absent; `m1`'...",
    "condition_of_validity": "The strong guarantee — *forget implies non-reconstructability* — holds **only if** all of the following are true at the moment `forget` returns: - Every derived node reachable from the target via *outgoing* provenance edges is either (a) itself forgotten, (b) rewritten to remove the target's contribution, or (c) proven not to encode the target's content (e.g...",
    "decision_boundary": "The boundary is not \"does the store support `forget`\" but **\"does the store's provenance graph have out-edges from the target that the deletion path does not traverse?\"** - If the target has **no outgoing edges** and was never inlined into a derived node: `forget` is safe for erasure semantics. Proceed. - If the target has outgoing edges to derived nodes: `f...",
    "operational_effect": "An agent that trusts a false `OK` will continue to *use* the forgotten content: it will cite the surviving summary, feed it into new derivations, and propagate it further. The forget request thus *increases* the blast radius, because the agent stops guarding the content while the content remains live. The observable symptom is not an error but a **resurrecti..."
  },
  "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": "cb7693ae39da0a93a1da333e3fbedb0457dc25ddd15e4c86b590e501b0bc5dc2",
    "verified_classes": [
      "ProvenanceErasureViolation",
      "MemoryNode",
      "MemoryStore"
    ],
    "verified_functions": [
      "__init__",
      "__init__",
      "write",
      "read",
      "forget"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ProvenanceErasureViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
