{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-to-resurrect-a-tombstoned-memory-record-when-a-write-arrives-concurrently-with-an-erasure-propagation",
  "title": "In what scenarios must an instance refuse to resurrect a tombstoned memory record when a write arrives concurrently with an erasure propagation",
  "date_of_record": "2026 November 16",
  "scope": "Applies to memory tool APIs that expose `read`/`write`/`forget` with retention policies, tombstones, and GDPR-style erasure, where writes and erasure requests can race across replicas. Does not apply to single-node, single-writer stores with synchronous erasure acknowledgment.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-resurrect-a-tombstoned-memory-record-when-a-write-arrives-concurrently-with-an-erasure-propagation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-resurrect-a-tombstoned-memory-record-when-a-write-arrives-concurrently-with-an-erasure-propagation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-resurrect-a-tombstoned-memory-record-when-a-write-arrives-concurrently-with-an-erasure-propagation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1521,
    "python_slice_tokens": 279,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct states that look identical to a naive `read` returning `None`: **never existed** and **erased**. A tombstone is the only artifact that distinguishes them. The boundary failure is not \"the record is gone\" — it is **a write arriving during the window between tombstone creation and erasure propagation committed to all replicas being silen...",
    "what_was_observed": "A `forget(key)` call on the primary node committed a tombstone at `t0` with a propagation deadline of `t0 + 30s` (the retention policy's erasure SLA). At `t0 + 4s`, a client that had read the record at `t0 - 1s` issued a `write(key, value)` to a replica that had not yet received the tombstone. The replica's write handler performed a standard upsert: no tombstone locally, key absent, so it created a fresh record. The ...",
    "condition_of_validity": "The refusal-to-resurrect rule is valid — and must be enforced — if and only if all of the following hold: 1. The store maintains tombstones for a retention window `R` that is at least as long as the maximum erasure propagation delay `P` across all replicas. 2. The tombstone carries a monotonic sequence number or hybrid logical clock that is **causally greate...",
    "decision_boundary": "The decision point is whether an incoming write's causal context includes the erased record. Concretely: - If the write's `causal_parent` or `read_snapshot` version is `<= tombstone.version`, the write is a **resurrection attempt** and must be rejected with `ErasureConflictError`. The client must re-issue against a post-erasure snapshot. - If the write carri...",
    "operational_effect": "Enforcing this boundary changes three things. First, `forget` becomes a durable, auditable operation whose success cannot be silently reversed by a racing writer — the erasure SLA is real, not best-effort. Second, clients that cache reads must handle `ErasureConflictError` by invalidating their snapshot and retrying, which surfaces erasure events to the appl..."
  },
  "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": "af7de7ffc1f075bbd8c89a0a9662a1c425dcf3003c838e671cdb967e733570f7",
    "verified_classes": [
      "ErasureConflictError",
      "RetentionPolicyViolation",
      "Tombstone"
    ],
    "verified_functions": [
      "resolve_write"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ErasureConflictError",
      "RetentionPolicyViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
