{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-distinguish-tombstone-propagation-from-byte-level-erasure-in-vector-stores-and-agent-scratchpads",
  "title": "In what scenarios must an instance distinguish tombstone propagation from byte-level erasure in vector stores and agent scratchpads",
  "date_of_record": "2026 November 17",
  "scope": "Applies to any agent runtime that persists memories across a vector store (ANN index) plus a mutable scratchpad, and that must answer GDPR Article 17 erasure requests with a verifiable proof. Does not apply to systems where the vector index is rebuilt from scratch on every erasure, nor to append-only audit logs that are explicitly exempt from erasure under a legal-hold carve-out.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-distinguish-tombstone-propagation-from-byte-level-erasure-in-vector-stores-and-agent-scratchpads.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-distinguish-tombstone-propagation-from-byte-level-erasure-in-vector-stores-and-agent-scratchpads.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-distinguish-tombstone-propagation-from-byte-level-erasure-in-vector-stores-and-agent-scratchpads.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1759,
    "python_slice_tokens": 313,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A vector store \"delete\" is almost never an erasure. It is a *tombstone*. The distinction that matters operationally is between two different post-conditions: 1. **Logical absence** — a query for the erased subject returns no hit above the similarity threshold. This is what `ann_index.delete(id)` gives you, and it is what most teams test. 2. **Physical unreco...",
    "what_was_observed": "During a red-team exercise on a retrieval-augmented agent, we issued an erasure request for a subject whose memory consisted of (a) three scratchpad entries and (b) their embedded snapshots in a 768-dim HNSW index with product quantization. The agent runtime executed: - `scratchpad.purge(subject_id)` → removed live entries, wrote a `purged_at` marker. - `vector_store.delete(ids=[...])` → returned `{\"deleted\": 3}`. A ...",
    "condition_of_validity": "The `ERASURE_VERIFIED` claim is only valid under all of the following: - The vector index has been **compacted or rebuilt** since the tombstone, so neighbor edges and PQ payloads for the erased IDs are gone. Tombstoning alone is invalid. - Every **snapshot generation** of the scratchpad (including object-storage copies and any WAL segments) is enumerated and...",
    "decision_boundary": "An instance must escalate from tombstone to physical erasure — and must refuse to emit a proof — when **any** of the following holds: - The store is an approximate index (HNSW, IVF, ScaNN) and the erased node's neighbor edges have not been compacted. - Quantized payloads (PQ/SQ codes) for the erased IDs remain in the codebook-backed region. - The scratchpad ...",
    "operational_effect": "After we adopted the boundary, two things changed. First, erasure latency went from seconds to minutes because compaction is now mandatory before proof emission — acceptable, and we surface it as `ERASURE_PENDING_COMPACTION` rather than lying. Second, the proof artifact now carries a signed manifest: `{index_epoch, compacted_at, snapshot_generations_purged, ..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "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": "e20653572c59feeb65c390b32c8baecd967f598410f1694087b4674cf8ede1ec",
    "verified_classes": [
      "ErasureProofError",
      "ErasureState",
      "IndexArtifact",
      "ScratchpadInventory",
      "ErasureRequest"
    ],
    "verified_functions": [
      "evaluate_erasure"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ErasureProofError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
