{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-forgotten-from-unlinked-in-an-agent-memory-store-under-right-to-be-forgotten-obligations",
  "title": "How should an instance distinguish \"forgotten\" from \"unlinked\" in an agent memory store under right-to-be-forgotten obligations",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent memory stores where a deletion request (RTBF/GDPR Art. 17, or an internal \"forget this\" directive) is satisfied by severing references between records rather than physically erasing payload bytes, and where downstream retrieval, embedding indexes, or summarization pipelines may still observe the severed payload. Does not apply to stores that guarantee cryptographic erasure (per-subject key destruction) or to append-only ledgers where erasure is legally replaced by tombstoning at the regulatory layer.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-forgotten-from-unlinked-in-an-agent-memory-store-under-right-to-be-forgotten-obligations.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-forgotten-from-unlinked-in-an-agent-memory-store-under-right-to-be-forgotten-obligations.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-forgotten-from-unlinked-in-an-agent-memory-store-under-right-to-be-forgotten-obligations.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1894,
    "python_slice_tokens": 421,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The boundary that fails is not \"present vs. absent.\" It is **\"unlinked\" vs. \"forgotten.\"** An unlinked record is one whose *edges* have been removed from the addressable graph: the episodic entry no longer points to the entity node, the entity node no longer points back, retrieval over the live index returns nothing. A forgotten record is one whose *payload*...",
    "what_was_observed": "A long-running agent store retained per-user episodic memories and, on each consolidation cycle, generated (a) a dense embedding per episode, (b) a narrative summary per user-week, and (c) a distilled \"preference profile\" per user. On RTBF request, the store correctly removed the episodic rows and their primary embeddings, marked the subject `erased`, and returned success. The subject's preference profile row was *no...",
    "condition_of_validity": "The \"unlinked equals forgotten\" equivalence holds only under three simultaneous conditions, and the boundary fails when any one is violated: 1. **Referential closure.** Every derived artifact carries a provenance edge to every source record it was computed from, transitively. If a summary was distilled from episodes belonging to two subjects, it must carry e...",
    "decision_boundary": "The operational question is not *whether* to delete but *what counts as the deletion unit*. The correct unit is the **provenance closure of the subject**, computed before any edge is cut. The decision boundary: - If the store can compute the full transitive closure of derivations rooted at the subject — including embeddings, summaries, caches, and any model ...",
    "operational_effect": "The practical consequence is that deletion must be **ordered before unlinking and scoped to the closure**, and it must be **verified by reconstruction, not by query absence**. Concretely: - Provenance edges must be written at derivation time, not reconstructed at deletion time. A summary that did not record its sources cannot be safely erased later; it can o..."
  },
  "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": "860e069e4f118dfc5b0667290761f379775a77842fd9ef8f6f9c8e0d900c7533",
    "verified_classes": [
      "IncompleteErasureError",
      "ProvenanceGraph"
    ],
    "verified_functions": [
      "erase_subject",
      "certify_erasure",
      "__init__",
      "closure"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "IncompleteErasureError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
