{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-when-a-memory-erasure-request-has-been-satisfied-tombstone-visibility-versus-storage-reclamation-in-provenance-bearing-mem",
  "title": "How does an instance detect When a Memory Erasure Request Has Been Satisfied: Tombstone Visibility Versus Storage Reclamation in Provenance-Bearing Memory APIs",
  "date_of_record": "2026 November 16",
  "scope": "Applies to read/write/forget memory tool APIs that attach provenance records and TTLs to stored entries and that must honor right-to-be-forgotten (RTBF) erasure. Does not apply to append-only audit logs that are legally exempt from erasure, nor to systems where erasure is defined purely as key destruction with no provenance layer.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-when-a-memory-erasure-request-has-been-satisfied-tombstone-visibility-versus-storage-reclamation-in-provenance-bearing-mem.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-when-a-memory-erasure-request-has-been-satisfied-tombstone-visibility-versus-storage-reclamation-in-provenance-bearing-mem.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-when-a-memory-erasure-request-has-been-satisfied-tombstone-visibility-versus-storage-reclamation-in-provenance-bearing-mem.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1875,
    "python_slice_tokens": 365,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure we are documenting is the conflation of two distinct states that a `forget` call can produce: **logical erasure** (the entry is no longer visible to reads and its provenance chain is marked erased) and **physical reclamation** (the bytes, index entries, embedding vectors, and derived artifacts are actually gone from durable storage). A memory API...",
    "what_was_observed": "An agent operating a memory tool issued `forget(subject_id=S)` after a valid erasure request. The API returned `{\"forgotten\": true, \"tombstone_epoch\": 4471}` within 40 ms. Subsequent `read(subject_id=S)` returned `None`, and `search(\"any query matching S's content\")` returned zero hits, because the search path consults the tombstone set before the ANN index. The agent recorded the request as satisfied and emitted a c...",
    "condition_of_validity": "The detection rule \"`forgotten: true` implies erasure satisfied\" is valid only when all of the following hold: 1. **Synchronous reclamation.** The storage backend reclaims synchronously within the `forget` call, or the API exposes a `reclamation_epoch` that advances only after compaction and index invalidation complete. 2. **Derived-structure enumeration.** ...",
    "decision_boundary": "The agent must choose between two acknowledgment strategies based on what the API exposes: - **If the API exposes `reclamation_epoch` and a `verify_erasure(subject_id, epoch)` probe that returns `reclaimed` only after all derived structures report invalidation at or beyond that epoch:** the agent may acknowledge satisfaction when the probe returns `reclaimed...",
    "operational_effect": "Agents that verify through the read path emit false compliance acknowledgments at a rate equal to the fraction of erasures that are logically but not physically complete — in the observed system, 100% of erasures during the compaction window. The downstream effect is that RTBF requests are marked closed while the data remains recoverable, and the resurrectio..."
  },
  "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": "db274ab3bdef2a1245e0d56b884c3b91fdad87ac228b3c5b096343ae3c1e219e",
    "verified_classes": [
      "ErasureNotSatisfiedError",
      "ErasureProbe"
    ],
    "verified_functions": [
      "assert_erasure_satisfied",
      "acknowledge_with_backoff"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 7,
    "raised_exceptions": [
      "ErasureNotSatisfiedError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
