{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-a-deleted-memory-be-proven-absent-before-forget-compliance-can-be-attested",
  "title": "Where must an instance of a “deleted” memory be proven absent before forget-compliance can be attested",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent memory stores that implement deletion obligations (GDPR/CCPA erasure, tenant offboarding, secret rotation) over a layered topology of write-ahead log, embedding index, KV cache, and derived summaries. Does not apply to single-process, single-store systems where the authoritative record is the only copy.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-deleted-memory-be-proven-absent-before-forget-compliance-can-be-attested.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-deleted-memory-be-proven-absent-before-forget-compliance-can-be-attested.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a-deleted-memory-be-proven-absent-before-forget-compliance-can-be-attested.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1544,
    "python_slice_tokens": 361,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious invariant is this: *deletion is not an operation on a key; it is an operation on a set of derivations.* A forget request names a source record (a document, a conversation turn, a user ID). Compliance is not satisfied when the source record is removed from the primary store. It is satisfied only when every *derived instance* — embeddings, ANN ...",
    "what_was_observed": "In a system with a 12-month retention WAL, a 90-day TTL embedding index, and a nightly summarization job, a forget request for a single conversation turn was executed as: `DELETE` on the primary row, tombstone insert, and an enqueue to the index-compaction queue. The queue drained on a 6-hour cadence. During the window between tombstone and compaction, the following were all true and all observable: 1. The WAL still ...",
    "condition_of_validity": "A forget-compliance attestation is valid only if it is conditioned on a *closure statement* over the derivation graph. Formally: let $R$ be the set of source records named by the request, and let $D(R)$ be the transitive closure of derivations (embeddings, index entries, cache blocks, summaries, fine-tune deltas, logs). The attestation is valid iff for every...",
    "decision_boundary": "The operational decision is: **when does a forget request require a synchronous, blocking compaction versus an asynchronous, attested-deferred one?** The boundary is determined by the *invertibility class* of the most sensitive derivation, not by the sensitivity of the source. If any derivation is in the high-invertibility class (verbatim-text embeddings, un...",
    "operational_effect": "Teams that adopt derivation-closure auditing observe three concrete changes. First, forget-request latency is no longer uniform: high-invertibility requests block on WAL rotation and index compaction, which means the SLO must be expressed per invertibility class, not as a single p99. Second, the index compaction queue becomes a compliance-critical path and m..."
  },
  "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": "02e8ef76e3683b1f5c565259935461d977c8664b80398caedcd35f20d33d0c44",
    "verified_classes": [
      "ForgetComplianceError",
      "Invertibility",
      "Media",
      "Derivation",
      "ClosureAttestation"
    ],
    "verified_functions": [
      "attest_forget",
      "assert_attestable"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ForgetComplianceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
