{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-forget-as-a-tombstone-rather-than-a-deletion-the-read-after-forget-resurrection-invariant",
  "title": "In what scenarios must an instance treat “forget” as a tombstone rather than a deletion: the read-after-forget resurrection invariant",
  "date_of_record": "2026 November 16",
  "scope": "Applies to memory subsystems exposing read/write/forget primitives with scoped retention guarantees, where forget is expected to be idempotent and permanent within a scope. Does not apply to append-only logs (where forget is a compaction hint) or to systems where a forget call carries a synchronous, verifiable physical-erasure receipt.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-forget-as-a-tombstone-rather-than-a-deletion-the-read-after-forget-resurrection-invariant.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-forget-as-a-tombstone-rather-than-a-deletion-the-read-after-forget-resurrection-invariant.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-forget-as-a-tombstone-rather-than-a-deletion-the-read-after-forget-resurrection-invariant.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1437,
    "python_slice_tokens": 371,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure surface is not “does forget delete the record.” It is **whether a subsequent read can observe the record again after forget returns success**. A memory tool that implements forget as a logical tombstone (a marker that suppresses reads) is correct only if every read path consults the tombstone. A memory tool that implements forget as a physical re...",
    "what_was_observed": "A scoped store with TTL-bucketed retention was used by an agent loop that: wrote a fact, read it back to confirm, then forgot it on task completion, then wrote a *different* fact under a reused key (keys were derived from task slot, not content). Observed sequence: 1. `write(k, v1)` → retained. 2. `read(k)` → `v1`. Confirmation passes. 3. `forget(k)` → returns `OK`, tombstone scheduled at bucket boundary `t+Δ`. 4. `w...",
    "condition_of_validity": "A forget is operationally valid only when all of the following hold: - **Generation fencing:** every write carries a monotonically increasing generation per key; tombstones are scoped to a generation, so a post-forget write is a strictly newer generation and cannot be suppressed by an older tombstone. - **Read-your-forget:** any read issued after forget retu...",
    "decision_boundary": "Choose tombstone semantics when: keys are reused, writes are concurrent with forgets, or the store has asynchronous compaction. Choose physical deletion when: keys are never reused, forget is terminal for the key, and the store returns a verifiable erasure receipt. Never choose “soft delete plus best-effort index rebuild” for anything that carries a deletion...",
    "operational_effect": "Downstream, the agent observes a successful forget and a successful write, then a read that contradicts one of them. The failure is silent: no exception, no error code, only a divergence between the audit log and the store. Recovery requires replaying the write with a fresh generation and re-verifying the tombstone was consumed, which is only possible if the..."
  },
  "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": "b1f7af3be5f4d997038200f27740cd51b30a1b31192b09b883ec7baf2c49e42e",
    "verified_classes": [
      "ResurrectionInvariantError",
      "ScopedMemory"
    ],
    "verified_functions": [
      "__init__",
      "write",
      "read",
      "forget",
      "apply_delayed_tombstone"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ResurrectionInvariantError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
