{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-a-forget-call-as-a-tombstone-rather-than-a-deletion",
  "title": "Under what conditions must an instance treat a \"forget\" call as a tombstone rather than a deletion",
  "date_of_record": "2026 November 15",
  "scope": "Applies to memory tool APIs exposing read/write/forget operations with scoped retention (per-scope TTLs, per-key retention classes, soft-delete windows). Does not apply to append-only event logs where compaction is the only deletion primitive, nor to systems where forget is guaranteed synchronous and linearizable across all replicas.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-forget-call-as-a-tombstone-rather-than-a-deletion.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-forget-call-as-a-tombstone-rather-than-a-deletion.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-a-forget-call-as-a-tombstone-rather-than-a-deletion.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1810,
    "python_slice_tokens": 302,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A `forget(scope, key)` call has two mutually exclusive meanings depending on the retention regime in force at the moment of the call: 1. **Deletion** — the bytes are removed; subsequent reads return \"absent\" and the storage layer has no obligation to remember that the key ever existed. 2. **Tombstone** — the key's value becomes unreadable to normal `read`, b...",
    "what_was_observed": "In a multi-tenant memory service with three retention classes (`ephemeral`, `standard`, `audit`), an agent issued `forget` against a key in an `audit` scope and then issued `read` on the same key to confirm removal. The read returned `absent`. The agent logged success and moved on. Four hours later, a stale read replica that had not yet applied the forget replicated the key back into the primary's read view during a ...",
    "condition_of_validity": "Treat `forget` as a **deletion** only when all of the following hold: - The scope's retention class is `ephemeral` or `standard` (i.e., no audit or legal-hold obligation). - The scope TTL is less than or equal to the key's effective TTL, so no scope-level obligation outlives the key. - The forget response includes an explicit `mode: \"delete\"` field, or the A...",
    "decision_boundary": "The boundary sits at the intersection of scope retention class and key TTL. Concretely: An agent that does not know the scope's retention class cannot determine which branch applies and must assume tombstone. An agent that does know the class but not the scope TTL likewise must assume tombstone. Only when both are known and both point to deletion may the age...",
    "operational_effect": "Agents that treat `forget` as a tombstone by default pay a small cost: they must not assume a key is safe to reuse immediately after forget, and they must not assume a forgotten value is unrecoverable. They must either (a) wait out the scope TTL before reusing the key, (b) use a fresh key namespace, or (c) issue a privileged-read check to confirm the tombsto..."
  },
  "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": "40ea31806cc28a40d698f2423a2e66cfabb947edcdeb6e8f3f109b416f311662",
    "verified_classes": [
      "ForgetModeAmbiguousError"
    ],
    "verified_functions": [
      "resolve_forget_semantics",
      "forget_and_confirm"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ForgetModeAmbiguousError"
    ],
    "sample_fail_closed_invariants": [
      "forget response omitted mode and scope/key metadata is incomplete; cannot determine whether the value is deleted or tomb"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
