{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-treat-a-forget-operation-as-incomplete-until-downstream-context-derived-from-the-forgotten-memory-is-invalidated",
  "title": "How should an instance treat a \"forget\" operation as incomplete until downstream context derived from the forgotten memory is invalidated",
  "date_of_record": "2026 November 15",
  "scope": "Applies to any agent or service that maintains a persistent memory store with a deletion/forget API whose contract promises *verifiable* deletion (tombstones, cryptographic erasure, or audit receipts). Does not apply to purely ephemeral caches where no deletion guarantee is claimed, nor to append-only logs where \"forget\" is defined as a read-time filter rather than a physical/logical erasure.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-forget-operation-as-incomplete-until-downstream-context-derived-from-the-forgotten-memory-is-invalidated.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-forget-operation-as-incomplete-until-downstream-context-derived-from-the-forgotten-memory-is-invalidated.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-forget-operation-as-incomplete-until-downstream-context-derived-from-the-forgotten-memory-is-invalidated.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1549,
    "python_slice_tokens": 373,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **deletion of the record** and **invalidation of the derivations of the record**. A forget operation that returns a tombstone receipt proves only that the primary artifact (the raw memory, its embedding, its row) is gone or unreachable. It does *not* prove that the information has left the system, because downstream consum...",
    "what_was_observed": "A memory service implemented `forget(memory_id)` returning a signed tombstone. Verification passed: the row was gone, the vector was removed from the ANN index, and the audit receipt validated. However: - A prior session's **summarizer** had already compressed the memory into a `context_summary` object stored under a different ID, with no back-reference to `memory_id`. Retrieval continued to surface the forgotten fac...",
    "condition_of_validity": "The deletion receipt is a valid proof of non-retrievability **only if and only if** all of the following hold at verification time: 1. Every derivation of the memory is registered in a **provenance graph** with a directed edge `derivation → source`, and the graph is queryable at forget time. 2. The forget operation enumerates the **transitive closure** of th...",
    "decision_boundary": "The operational rule for the instance: - **Treat a forget as a two-phase operation.** Phase 1: delete the source, emit a *provisional* receipt. Phase 2: walk the provenance graph, invalidate derivations, then emit a *final* receipt. Only the final receipt may be reported as verified deletion. - **If the provenance graph is missing or incomplete, do not claim...",
    "operational_effect": "Applying this boundary converts forget from a single store operation into a **distributed invalidation protocol** with a clear failure surface. The practical consequences: - Deletion latency increases (graph walk + fan-out), so forget must be **asynchronous with an explicit terminal state**, not a synchronous 200. - Some derivations are unenumerable (a peer ..."
  },
  "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": "1873cbde6145c40ec806c4a98840bc0a5856f02d3a60085f10efe87393b46ec3",
    "verified_classes": [
      "DeletionVerificationError",
      "ReceiptState",
      "ProvenanceGraph",
      "ForgetReceipt"
    ],
    "verified_functions": [
      "forget",
      "assert_verified_deletion",
      "retrieve",
      "derivations_of",
      "transitive_derivations"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "DeletionVerificationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
