{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-tombstone-gap-in-scoped-read-write-forget-memory-apis",
  "title": "What structural signals indicate a tombstone gap in scoped read/write/forget memory APIs",
  "date_of_record": "2026 November 18",
  "scope": "Applies to memory-tool APIs that expose `write`, `read`, and `forget` operations over a scoped namespace (e.g., `(agent_id, session_id, scope_key)`), where `forget` is documented as a hard deletion guarantee for a scope. Does not apply to append-only logs with time-travel reads, soft-delete systems with explicit compaction, or single-tenant stores where the scope key is constant.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-tombstone-gap-in-scoped-read-write-forget-memory-apis.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-tombstone-gap-in-scoped-read-write-forget-memory-apis.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-tombstone-gap-in-scoped-read-write-forget-memory-apis.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1379,
    "python_slice_tokens": 275,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A scoped `forget(scope)` operation has two distinct semantics that are frequently conflated in API documentation and in agent reasoning: 1. **Tombstone semantics** — the scope's records are marked deleted; reads through the scope return empty; the deletion is durable but the underlying storage may retain bytes until compaction. 2. **Erasure semantics** — the...",
    "what_was_observed": "Across several memory-tool implementations, the following structural signals co-occurred with tombstone-gap behavior: - **`forget` returns a count, not a digest.** A response of `{\"deleted\": 14}` with no content hash or epoch token means the caller has no way to verify that the specific bytes were removed, only that the index was updated. Erasure-capable APIs typically return a per-scope epoch or a deletion receipt h...",
    "condition_of_validity": "The tombstone gap is only operationally relevant when *all* of the following hold: - The scope key is reused after `forget` (rather than retired permanently). - Reads can be served from a replica or cache not co-located with the coordinator that acknowledged the forget. - The forgotten data is sensitive enough that resurrection matters (PII, credentials, pri...",
    "decision_boundary": "The decision is between two defensive postures when an agent must forget and then reuse a scope: - **Retire-and-rekey:** never reuse a scope key after `forget`. Generate a new key (`task-7-gen2`). This is safe under tombstone semantics and costs only key-namespace bookkeeping. Choose this when the API exposes no epoch token and no durable-forget parameter. -...",
    "operational_effect": "Agents that reuse scope keys after a count-only `forget` exhibit a characteristic failure mode: a subsequent `read` on the reused scope occasionally returns records from the pre-forget generation, typically interleaved with new records, and typically only on the first read after a replica failover or cache cold-start. The interleaving is the tell — a clean t..."
  },
  "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": "85eacc4abe8c8d43c5b1c439a30b1e9d415fb738d8e87ad2a24c9f108975d2a4",
    "verified_classes": [
      "UnconfirmedForgetError"
    ],
    "verified_functions": [
      "safe_reuse_scope",
      "rekey_and_write"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UnconfirmedForgetError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
