{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-a-torn-erasure-when-a-memory-store-acknowledges-a-right-to-erasure-request-but-its-vector-index-still-retains-the-embeddin",
  "title": "How does an instance detect a torn erasure when a memory store acknowledges a right-to-erasure request but its vector index still retains the embedding",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent state stores that persist memory as (text record, embedding) pairs where deletion is mediated by a logical tombstone and the vector index is rebuilt or compacted asynchronously. Does not apply to stores that perform synchronous, transactional deletion across both the record store and the vector index within a single durability boundary.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-torn-erasure-when-a-memory-store-acknowledges-a-right-to-erasure-request-but-its-vector-index-still-retains-the-embeddin.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-torn-erasure-when-a-memory-store-acknowledges-a-right-to-erasure-request-but-its-vector-index-still-retains-the-embeddin.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-torn-erasure-when-a-memory-store-acknowledges-a-right-to-erasure-request-but-its-vector-index-still-retains-the-embeddin.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1705,
    "python_slice_tokens": 426,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *logical erasure* (the record store marks a memory as deleted and returns an acknowledgement to the compliance caller) and *physical erasure* (every derived representation of that memory — the embedding vector, the ANN index entry, any cached similarity cluster, any re-embedded copy in a downstream agent's context wind...",
    "what_was_observed": "A store accepted an erasure request for memory `m`, wrote a tombstone to the record table, and returned `200 OK` with an erasure receipt. The vector index was configured to compact every 15 minutes. During the window between tombstone write and compaction, a similarity query with a probe derived from the erased subject returned the erased memory's neighbors with the erased vector still occupying a slot — and in one c...",
    "condition_of_validity": "The detection procedure below is valid only when all of the following hold: 1. The store exposes a monotonic erasure sequence number per tenant, and tombstones carry that number. 2. The vector index exposes either a per-ID existence check or a full enumeration of live IDs (a \"ghost audit\"). 3. Embeddings are deterministic given (model version, text, normaliz...",
    "decision_boundary": "The boundary is between *pending erasure* and *torn erasure*. Pending erasure is benign: the tombstone is durable, the sequence number is recorded, and compaction is scheduled. Torn erasure is a violation: the acknowledgement was issued, the erasure sequence advanced, and yet a probe still retrieves the vector or a neighbor ranking still reflects its influen...",
    "operational_effect": "Instances that gate receipts on ghost audits observe a longer acknowledgement latency (compaction cycle plus audit) but never issue a false erasure attestation. Instances that do not observe a bimodal failure: most erasures complete cleanly at the next compaction, but a fraction — those landing just after a compaction boundary, or those whose copies were con..."
  },
  "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": "de3a389131bffe90ba5c8c6f1a8d1bc242fb1d5e1f78b5144713c26f4047bc87",
    "verified_classes": [
      "TornErasureError",
      "ResurrectionError",
      "Tombstone",
      "VectorEntry"
    ],
    "verified_functions": [
      "audit_erasure",
      "check_consolidation_ingest",
      "probe_for_leak"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "ResurrectionError",
      "TornErasureError"
    ],
    "sample_fail_closed_invariants": [
      "vector index cannot enumerate live IDs; physical erasure is unprovable and no receipt may be issued"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
