{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-treats-a-memory-deletion-attestation-as-a-durable-tombstone-rather-than-a-receipt",
  "title": "What happens when an instance treats a memory deletion attestation as a durable tombstone rather than a receipt",
  "date_of_record": "2026 November 17",
  "scope": "Applies to memory tool APIs (read/write/forget) where `forget` returns an attestation object and scoped retention is enforced by TTL. Does not apply to systems where deletion is synchronous and the attestation is the authoritative storage state (i.e., where the backend guarantees no further reads can return the deleted value).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-treats-a-memory-deletion-attestation-as-a-durable-tombstone-rather-than-a-receipt.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-treats-a-memory-deletion-attestation-as-a-durable-tombstone-rather-than-a-receipt.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-treats-a-memory-deletion-attestation-as-a-durable-tombstone-rather-than-a-receipt.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1360,
    "python_slice_tokens": 307,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A deletion attestation is a *receipt*: a signed, timestamped assertion that a specific `forget` request was accepted and applied to a specific scope at a specific logical time. It is **not** a tombstone. A tombstone is a negative fact stored in the same read path as the data, such that subsequent reads resolve to \"deleted\" by construction. These two artifact...",
    "what_was_observed": "A retrieval agent forgot key `user_pref.locale` in scope `session:abc`, received a valid attestation with `applied_at`, and stored the attestation in its own working memory as a tombstone. Two turns later, a different subsystem re-materialized the key from scope `tenant:acme` (which had a 30-day TTL and was never in the forget scope). The agent's local tombstone suppressed the read, so it reported \"locale unknown\" an...",
    "condition_of_validity": "The attestation is sufficient to suppress reads *only* under all of the following: 1. The forget scope is an ancestor of every scope that can produce the key (i.e., the forget cascaded to the maximal scope). 2. No other scope with an overlapping key space has a TTL longer than the attestation's `applied_at`, or the backend guarantees that a longer-TTL write ...",
    "decision_boundary": "The operational rule: **treat an attestation as a tombstone only if the API exposes a `cascades_to` field naming the maximal scope, and only if that maximal scope is the one you actually wanted to forget.** If the API returns a bare attestation with no scope closure, the correct behavior is to re-read the key on the next access and let the backend resolve, n...",
    "operational_effect": "Agents that conflate attestation with tombstone exhibit a characteristic failure signature: correct behavior on the first turn after forget, then silent divergence several turns later when a sibling scope re-materializes the key. The divergence is not detected by read-after-write checks because the agent's own tombstone masks the read. Detection requires an ..."
  },
  "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": "7db8774f6813abc077f694cae25aa8cbfd170733be531ef34d3f7300d7dd72c6",
    "verified_classes": [
      "AttestationMisuseError",
      "Attestation"
    ],
    "verified_functions": [
      "may_suppress_read",
      "reconcile"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "AttestationMisuseError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "datetime"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
