{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-forget-as-a-tombstone-that-still-leaks-gradient-rather-than-a-deletion-that-removes-evidence",
  "title": "Under what conditions must an instance treat “forget” as a tombstone that still leaks gradient rather than a deletion that removes evidence",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agentic systems that persist state (episodic memory, vector indexes, fine-tune deltas, cached KV/embedding artifacts) and must satisfy a GDPR Article 17 erasure request against that state. Does not apply to stateless inference or to data whose only copy is in a transactional store with a synchronous hard-delete contract.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-forget-as-a-tombstone-that-still-leaks-gradient-rather-than-a-deletion-that-removes-evidence.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-forget-as-a-tombstone-that-still-leaks-gradient-rather-than-a-deletion-that-removes-evidence.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-forget-as-a-tombstone-that-still-leaks-gradient-rather-than-a-deletion-that-removes-evidence.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1215,
    "python_slice_tokens": 245,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A **forget-memory compliance audit** asks a single question: after the erasure request is processed, can the erased subject's information still be *reconstructed* from any retained artifact? The non-obvious boundary is between two operations that both report success: - **Logical deletion** — the record is marked `erased=true`, filtered out of retrieval, and ...",
    "what_was_observed": "During a right-to-erasure audit on an agent with a nightly LoRA refresh, the erased subject's episodic rows were hard-deleted and the vector index entry was removed. A retrieval probe returned zero hits and the audit was signed off. A secondary membership-inference probe — run later, out of band — reconstructed the subject's record from the **pre-erasure LoRA adapter checkpoint** that had been retained as a rollback ...",
    "condition_of_validity": "Logical deletion is a valid erasure only when **all** of the following hold: 1. No retained model artifact was trained on the subject's data, or the artifact has been retrained/rolled back to a pre-subject checkpoint and the post-subject checkpoint destroyed. 2. No cache (embedding, KV, prompt, content-hash) retains a derived artifact of the subject's data, ...",
    "decision_boundary": "The decision rule is: **an erasure request may be marked compliant only if the audit reconstructs nothing from the full artifact inventory, not merely from the retrieval index.** Concretely, enumerate artifact classes (primary store, vector index, model checkpoints/adapters, caches, logs, backups), and for each class run a reconstruction probe. Any single re...",
    "operational_effect": "The operational consequence is that erasure cost is dominated by **retraining and cache invalidation**, not by row deletion. Teams that treat forget as a row delete will accumulate tombstoned influence in adapters and caches until a membership-inference probe surfaces it, at which point the remediation is a full retrain plus cache flush — far more expensive ..."
  },
  "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": "d6cf9340d76a78b4f6857d636326ce2037071006ccbf1bdb7e3b47a10681ef0b",
    "verified_classes": [
      "ErasureAuditError",
      "ArtifactClass",
      "ErasureRequest"
    ],
    "verified_functions": [
      "certify_erasure"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ErasureAuditError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
