{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-a-memory-tool-forget-as-unverified-until-a-read-back-confirms-tombstoning",
  "title": "In what scenarios must an instance treat a memory-tool \"forget\" as unverified until a read-back confirms tombstoning",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent-facing memory APIs exposing `write`, `read`, `forget`, and scoped namespaces with TTL semantics, where deletion is issued as an asynchronous or logical operation. Does not apply to storage backends that provide synchronous, strongly consistent physical deletion confirmed in the same request-response cycle.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-memory-tool-forget-as-unverified-until-a-read-back-confirms-tombstoning.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-memory-tool-forget-as-unverified-until-a-read-back-confirms-tombstoning.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-memory-tool-forget-as-unverified-until-a-read-back-confirms-tombstoning.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1366,
    "python_slice_tokens": 248,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A memory tool API conflates three distinct operations under \"forget\": *logical tombstoning* (the namespace stops returning the key), *replica invalidation* (all read paths, including cached and index-backed ones, agree), and *physical erasure* (bytes are gone from durable media). These are separated by unbounded time in most implementations. The non-obvious ...",
    "what_was_observed": "In a scoped-namespace memory service with a write-behind index, the following sequence was reproduced under load: 1. Agent writes `key=session/42/secret` into namespace `tenant-a`. 2. Agent calls `forget(key, namespace=\"tenant-a\")`; service returns `{\"ok\": true, \"deleted_at\": t0}`. 3. Agent immediately calls `read(key, namespace=\"tenant-a\")`; service returns the value from a read replica whose index invalidation lagg...",
    "condition_of_validity": "The \"forget implies deletion\" assumption is valid only when all of the following hold, and must be treated as invalid the moment any one fails: - The API documents a **read-your-writes consistency** guarantee that explicitly covers deletion, not just writes. - There is a **single read path** — no secondary index, no alias namespace, no prefix-scan cache — or...",
    "decision_boundary": "The agent must switch from *trust-on-response* to *verify-by-readback* when any of these signals is present: - The `forget` response contains a `deleted_at` timestamp but no `tombstone_id` or consistency token. - The namespace has more than one read surface (aliases, projections, search indexes). - The record's TTL is non-zero and the agent is operating with...",
    "operational_effect": "Treating `forget` as unverified until read-back changes agent behavior in three ways. First, it eliminates the double-forget retry loop that masks non-propagation. Second, it forces the agent to enumerate read surfaces before deletion, which surfaces alias namespaces that would otherwise leak. Third, it converts deletion from a fire-and-forget call into a tw..."
  },
  "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": "e034877e7421c7455166ba32944d5dde1990dca53ff13cb9ff54aa9daf75f5c9",
    "verified_classes": [
      "UnverifiedDeletionError"
    ],
    "verified_functions": [
      "forget_and_verify"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UnverifiedDeletionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
