{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-deletes-a-memory-scope-it-is-still-reading-from",
  "title": "What happens when an instance deletes a memory scope it is still reading from",
  "date_of_record": "2026 November 15",
  "scope": "Applies to memory tool schemas exposing read/write/forget operations with scoped retention guarantees, where a `forget` call may target a scope (namespace, tenant, key prefix, or session) that is concurrently or subsequently read by the same or another agent instance. Does not apply to append-only stores without deletion semantics, nor to single-threaded agents that serialize all memory operations.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-deletes-a-memory-scope-it-is-still-reading-from.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-deletes-a-memory-scope-it-is-still-reading-from.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-deletes-a-memory-scope-it-is-still-reading-from.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1362,
    "python_slice_tokens": 270,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A scoped retention guarantee is a *promise about future readability*, not a *promise about present readability*. Most memory tool schemas conflate these. When an agent issues `forget(scope)`, the schema typically returns success once the deletion is acknowledged by the control plane. But deletion is a two-phase operation: the tombstone is written first, and ...",
    "what_was_observed": "A retrieval agent maintained a working scope `session:7f3a` containing summarization state, with a retention policy of \"delete on forget, effective immediately.\" The agent's control loop read the scope, computed a delta, wrote the delta back, and on task completion issued `forget(session:7f3a)`. Under load, a retry wrapper re-executed the final read-modify-write cycle after a timeout on the `forget` response. The `fo...",
    "condition_of_validity": "The guarantee \"after `forget(scope)` returns success, `read(scope)` fails\" is valid only under all of the following: (a) the read and write paths are served by the same consistency domain, with no asynchronous replica lag; (b) no derived or child scopes are materialized from the forgotten scope's contents; (c) no in-flight read was issued before the `forget`...",
    "decision_boundary": "The boundary is crossed when an agent derives state from a scope it may later forget, or forgets a scope while any read of that scope is in flight. The decision rule: if a scope's contents can flow into another scope, `forget` on the source is insufficient — the agent must either (1) forget derived scopes first, in dependency order, or (2) tag derived record...",
    "operational_effect": "Agents that conflate acknowledgment with observability produce resurrection bugs: forgotten data reappears in derived scopes, retention audits fail because the audit reads through the same lagging replica, and the agent's own deletion-verification logic generates spurious failure classifications that trigger unnecessary escalation. The practical mitigation i..."
  },
  "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": "a917d6136e8a10a774a8c43ac5f49ac683eda0d966bd265577c0f7ead23b5f87",
    "verified_classes": [
      "RetentionViolation",
      "MemoryStore"
    ],
    "verified_functions": [
      "finalize_session",
      "__init__",
      "write",
      "read",
      "forget"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "RetentionViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
