{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-a-ttl-expiry-as-distinct-from-a-gdpr-erasure-request-in-read-write-forget-memory-apis",
  "title": "In what scenarios must an instance treat a TTL expiry as distinct from a GDPR erasure request in read/write/forget memory APIs",
  "date_of_record": "2026 November 14",
  "scope": "Applies to memory subsystems exposing `read`/`write`/`forget` primitives with time-to-live (TTL), salience-weighted retention, and an erasure guarantee that must be provable to an external auditor. Does not apply to volatile caches where TTL expiry and eviction are indistinguishable to callers, nor to append-only logs where no forget primitive exists.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-ttl-expiry-as-distinct-from-a-gdpr-erasure-request-in-read-write-forget-memory-apis.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-ttl-expiry-as-distinct-from-a-gdpr-erasure-request-in-read-write-forget-memory-apis.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-a-ttl-expiry-as-distinct-from-a-gdpr-erasure-request-in-read-write-forget-memory-apis.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1333,
    "python_slice_tokens": 272,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A TTL expiry and a GDPR-style erasure request both remove a record from the readable surface, so naive implementations collapse them into a single `delete(key)` path. They are not the same operation. A TTL expiry is a *retention policy outcome*: the record was never marked for destruction, only for decay, and its salience score may have deferred or accelerat...",
    "what_was_observed": "In a production memory service, records carried a `ttl_at` timestamp and a `salience` float in `[0,1]`. A background compactor swept expired records into a cold archive tier, keeping them for 30 days for \"possible resurrection if salience is rescored upward.\" Separately, the service honored erasure requests by deleting the hot-tier row and returning HTTP 200. The failure surfaced when an auditor queried for a specifi...",
    "condition_of_validity": "The distinction is valid only when all of the following hold: 1. Records have a monotonic `expires_at` and a separate, non-recomputable `erased_at` marker (or an equivalent tombstone that survives compaction). 2. Salience rescoring can only *defer* expiry within a bounded window; it can never cross an `erased_at` boundary. 3. Every derived index (embeddings,...",
    "decision_boundary": "The operational rule: **branch on the cause of unreadability before performing any restoration, rescoring, or reindexing.** Concretely: - On `read` miss, inspect `erased_at` first, then `expires_at`. - If `erased_at` is set → return a terminal `ErasureConfirmed` signal; never resurrect, never rescore, never reindex from cold or derived tiers. - If only `expi...",
    "operational_effect": "Teams that collapse the two paths observe erasure violations under exactly one condition: a background job with resurrection authority. The symptom is intermittent — erasure holds until the first salience rescoring or cold-tier promotion touches the subject's cluster. Auditors find it, not production monitors, because the hot-tier read is correctly 404. The ..."
  },
  "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": "833e997b89f610de23f5826c82ab17cc8f2161c8bd9eb77705eae4f2b5817c00",
    "verified_classes": [
      "ErasureViolationError",
      "MemoryRecord",
      "MemoryStore"
    ],
    "verified_functions": [
      "__init__",
      "write",
      "forget",
      "resurrect"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ErasureViolationError",
      "KeyError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
