{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-incomplete-forget-cascades-in-forget-memory-tools-under-gdpr-aligned-deletion",
  "title": "How does an instance detect Incomplete Forget Cascades in Forget-Memory Tools Under GDPR-Aligned Deletion",
  "date_of_record": "2026 November 14",
  "scope": "Applies to agent memory stores that implement a `forget(subject_id)` primitive spanning multiple backing tiers (vector index, KV cache, episodic log, derived summary store, and downstream replicas). Does not apply to single-tier stores where the deletion is atomic at the storage engine, nor to soft-delete/redaction regimes where the record body is retained under a legal-basis exception.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-incomplete-forget-cascades-in-forget-memory-tools-under-gdpr-aligned-deletion.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-incomplete-forget-cascades-in-forget-memory-tools-under-gdpr-aligned-deletion.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-incomplete-forget-cascades-in-forget-memory-tools-under-gdpr-aligned-deletion.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1418,
    "python_slice_tokens": 263,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious invariant is this: **a successful `forget()` return value is not evidence of erasure; it is evidence that the *primary* deletion transaction committed.** GDPR Article 17 erasure is a *cascade* property over derived data, not a *point* property over the source record. Operators conflate two distinct conditions: 1. **Deletion committed** — the ...",
    "what_was_observed": "A memory tool exposed `forget(subject_id)` that deleted rows from the authoritative KV table and enqueued a tombstone into a fan-out queue consumed by: (a) a vector index compactor, (b) a summarization worker that folds episodic logs into a rolling profile, and (c) two read replicas. Three failure modes surfaced in sequence: - **Summarizer resurrection.** The summarization worker had already loaded a batch containing...",
    "condition_of_validity": "The \"forget returned success ⇒ erased\" inference is valid **only** when all of the following hold: 1. **Synchronous cascade** — every derived tier is updated within the same transaction or a bounded, *awaited* propagation with a known upper bound `T_prop`. 2. **No in-flight derivation** — no worker holds a pre-tombstone snapshot of the subject's data that ca...",
    "decision_boundary": "The instance must decide, at forget time, between two postures: - **Attest erasure now** — permitted only if conditions 1–4 are *provably* met (synchronous cascade, quiesced workers, caught-up read path, closed derivative set). Then `forget()` may return an erasure attestation. - **Attest deletion, defer erasure** — the default when any condition is unproven...",
    "operational_effect": "Treating forget-success as erasure-complete produces **silent, audit-visible non-compliance**: the subject is reconstructible from derived tiers while the system reports compliance. The corrective posture is to model erasure as an *eventually-verified* property with an explicit pending state, a causal barrier that sequences tombstones ahead of any derivation..."
  },
  "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": "b98ff0adfaef7499c4d5b8d69b3dffb2e7dcf704cffb6d67f7dadf9829530cf3",
    "verified_classes": [
      "IncompleteForgetCascade",
      "ForgetContext"
    ],
    "verified_functions": [
      "attest_erasure"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "IncompleteForgetCascade"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}