{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-tombstone-has-been-re-materialized-by-a-lossy-forget-path-in-read-write-forget-memory-tool-apis",
  "title": "What structural signals indicate a tombstone has been re-materialized by a lossy forget path in read/write/forget memory tool APIs",
  "date_of_record": "2026 November 16",
  "scope": "Applies to memory tool APIs that expose `read`, `write`, and `forget` operations over addressable records carrying provenance metadata and deletion semantics (soft-delete tombstones, hard-delete purges, or provenance-linked cascades). Does not apply to append-only event logs without deletion, nor to systems where `forget` is synchronous and blocking with a verified post-condition.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-tombstone-has-been-re-materialized-by-a-lossy-forget-path-in-read-write-forget-memory-tool-apis.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-tombstone-has-been-re-materialized-by-a-lossy-forget-path-in-read-write-forget-memory-tool-apis.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-tombstone-has-been-re-materialized-by-a-lossy-forget-path-in-read-write-forget-memory-tool-apis.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1840,
    "python_slice_tokens": 373,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious invariant is this: **a `forget` returning success is evidence that the tombstone was written, not that the underlying content is unreachable.** In most memory tool implementations, `forget(id)` writes a deletion marker and updates a provenance index in a separate store from the content blob. These two writes are not atomic. A subsequent `writ...",
    "what_was_observed": "Across three memory tool backends (a local SQLite-backed store, a hosted vector store with a metadata sidecar, and a provenance-graph store with content-addressed blobs), the same failure shape appeared: 1. `forget(\"user:alice:pref\")` returned `{\"status\": \"deleted\", \"tombstone\": \"t_8812\"}`. 2. `read(\"user:alice:pref\")` correctly returned `null` / `NotFound`. 3. A later `write(\"user:alice:pref:derived\", value, provena...",
    "condition_of_validity": "This failure is *possible* whenever all three of the following hold, and it is *observable* (i.e., you can detect it before it corrupts downstream reasoning) only when the fourth holds: - **C1 — Split stores.** Content and provenance are persisted in separate stores, or in the same store without a transactional constraint linking them. - **C2 — Lazy provenan...",
    "decision_boundary": "An agent operating over such an API must choose between two postures at the moment it observes a live record whose provenance chain contains a tombstoned ancestor: - **Treat as live (default).** The derived record is readable and internally well-formed; the tombstone is on a different key. This is correct *only* if the API contract guarantees that derivation...",
    "operational_effect": "The downstream consequence is that deletion semantics in read/write/forget APIs are **eventually-consistent at best and advisory at worst** unless the implementation enforces a write-time referential invariant (rejecting writes whose provenance targets are tombstoned) or a forget-time cascade (invalidating forward derivations). Agents that treat `forget` as ..."
  },
  "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": "98966068c82d2bbb3836685fc5672ae4dfd7db4d172972a9f66866743d804eac",
    "verified_classes": [
      "TombstoneDivergenceError",
      "MemoryRecord",
      "TombstoneLedger"
    ],
    "verified_functions": [
      "assert_reachable_only_through_live",
      "safe_read",
      "record",
      "is_active",
      "is_purged"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "TombstoneDivergenceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
