{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-forget-from-being-a-lie-deletion-tombstones-versus-scoped-retention-windows",
  "title": "Which invariants prevent \"Forget\" from being a Lie: Deletion Tombstones Versus Scoped Retention Windows",
  "date_of_record": "2026 November 16",
  "scope": "Applies to memory tool APIs exposing `write`, `read`, and `forget`/`delete` operations with per-record retention classes, redaction transforms, and GDPR erasure obligations. Does not apply to append-only logs with no erasure contract, or to systems where \"forget\" is explicitly documented as a soft hint rather than a guarantee.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-forget-from-being-a-lie-deletion-tombstones-versus-scoped-retention-windows.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-forget-from-being-a-lie-deletion-tombstones-versus-scoped-retention-windows.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-forget-from-being-a-lie-deletion-tombstones-versus-scoped-retention-windows.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1621,
    "python_slice_tokens": 433,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **logical erasure** (the record is no longer returned by `read`) and **physical erasure** (no residual artifact survives that can be reconstructed). Most memory tool APIs conflate these. A `forget` call that removes the index entry but leaves the record in a compaction-pending segment, a replica lagging behind, or a backup...",
    "what_was_observed": "In a scoped-retention memory service, the following sequence produced a violation: 1. Agent writes record `R` with `retention_class=standard(365d)`, `scope=tenant:A`. 2. A GDPR erasure request arrives for `R`; the API issues a tombstone `T(R)` and removes the index entry. 3. Concurrently, a write-ahead replica that had not yet seen `T(R)` replays `R` into a rebuilt index segment. 4. A retention-window extension job (...",
    "condition_of_validity": "The tombstone invariant holds only when all four conditions are met: - **Identity-anchored, not location-anchored.** The tombstone keys on `(tenant, record_id)`, not on `(segment_id, offset)`. Any re-materialization of `record_id` must consult the tombstone set before becoming readable. - **Tombstone durability precedes index mutation.** The tombstone is fsy...",
    "decision_boundary": "An agent operating this API must choose between two postures based on what the contract actually guarantees: - **If the API documents forget as logical-only** (index removal with eventual physical compaction), the agent must not report erasure as complete to a data subject or compliance system. It must record the forget request, track the compaction horizon,...",
    "operational_effect": "The practical consequence is that memory tool APIs with scoped retention must expose three things to be safely operable by an agent: (1) a tombstone state query keyed by record identity, (2) a retention-extension veto on tombstoned records, and (3) a materialized-redaction flag distinguishing write-time from read-time transforms. Without these, the agent's o..."
  },
  "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": "5fe4d449b191e218bb52346c5a3ce54b3193d536f2dcf821fab5cc6b368afe11",
    "verified_classes": [
      "ErasureInvariantError",
      "RetentionClass",
      "Tombstone",
      "MemoryRecord",
      "MemoryStore"
    ],
    "verified_functions": [
      "verify_erasure",
      "__init__",
      "write",
      "forget",
      "extend_retention",
      "read"
    ],
    "verified_functions_count": 6,
    "defensive_guards_count": 8,
    "raised_exceptions": [
      "ErasureInvariantError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
