{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-acknowledges-a-deletion-it-has-not-yet-made-durable-the-tombstone-before-durability-inversion-in-verifiable-memory-forge",
  "title": "What happens when an instance acknowledges a deletion it has not yet made durable: the tombstone-before-durability inversion in verifiable memory forgetting",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent memory stores that implement soft-delete plus asynchronous compaction (tombstone → physical purge) and that expose a deletion audit (proof-of-erasure) to a regulator or auditor. Does not apply to synchronous hard-delete stores where the audit record and the physical destruction commit in the same transaction, nor to append-only logs where \"forgetting\" is expressed as key destruction rather than record removal.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-acknowledges-a-deletion-it-has-not-yet-made-durable-the-tombstone-before-durability-inversion-in-verifiable-memory-forge.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-acknowledges-a-deletion-it-has-not-yet-made-durable-the-tombstone-before-durability-inversion-in-verifiable-memory-forge.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-acknowledges-a-deletion-it-has-not-yet-made-durable-the-tombstone-before-durability-inversion-in-verifiable-memory-forge.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1746,
    "python_slice_tokens": 301,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct events that regulated agent systems routinely conflate under the single word \"deleted\": 1. **Logical deletion** — the memory record is marked tombstoned, is no longer returned by retrieval, and a deletion audit entry is emitted with a timestamp and a record identifier. 2. **Durable erasure** — the underlying bytes (in the primary store...",
    "what_was_observed": "A regulated deployment (retention class: right-to-erasure on user memory) ran a compaction worker with a 6-hour target SLA and a deletion-audit emitter on the request path. Under normal load the two were tightly coupled: compaction lag was seconds, so tombstone time and purge time were empirically indistinguishable, and the audit was \"correct by accident.\" The failure surfaced only under a specific condition: a compa...",
    "condition_of_validity": "The tombstone-before-durability inversion is *safe* (audit remains truthful) only when all of the following hold: 1. The audit receipt is emitted **after** the compaction worker has durably committed the purge, not on the request path. 2. The receipt is bound to a **purge proof** — a content-addressed digest of the destroyed segment range plus a monotonic co...",
    "decision_boundary": "The operational decision is not \"should deletion be synchronous\" (it usually cannot be, at scale). It is: **which timestamp does the audit assert, and what does the regulator do with the gap?** - If the regulatory contract permits an *erasure-by-deadline* semantics (bytes unrecoverable by T+deadline), then emit the receipt with `erasure_deadline` and a `stat...",
    "operational_effect": "Once the inversion was identified, the deployment was changed so that the request path emits `status: pending_purge` with a deadline, and the compaction worker emits the terminal `erased_at` receipt only after a cross-shard purge proof commits. Consequences observed: - Deletion-request latency dropped (no longer blocked on proof assembly). - The audit log no..."
  },
  "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": "92c64ff7ec9233f924b7917feea4be03b8b3bbd1f918f279fe3b97f0e4bb5866",
    "verified_classes": [
      "ErasureAuditError",
      "PurgeState",
      "PurgeProof"
    ],
    "verified_functions": [
      "emit_terminal_erasure_receipt",
      "acknowledge_deletion"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ErasureAuditError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
