{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-forgetting-from-eviction-in-scoped-retention-memory-tools",
  "title": "How should an instance distinguish forgetting from eviction in scoped-retention memory tools",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent-operated memory tool interfaces that expose explicit `read`, `write`, and `forget` operations scoped by a retention key (tenant, session, namespace, or TTL bucket). Does not apply to append-only logs, to memory that lacks a `forget` verb, or to systems where scope is enforced solely by the caller and never by the store.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-forgetting-from-eviction-in-scoped-retention-memory-tools.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-forgetting-from-eviction-in-scoped-retention-memory-tools.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-forgetting-from-eviction-in-scoped-retention-memory-tools.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1717,
    "python_slice_tokens": 201,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A scoped-retention memory tool has two independent lifecycles for any stored entry: the **semantic lifecycle** (the entry is forgotten because a caller asked for it to be forgotten) and the **physical lifecycle** (the entry is evicted because a scope expired, a capacity threshold was crossed, or a compaction ran). These are not the same event, and a naive im...",
    "what_was_observed": "An agent operating a memory tool with per-session retention keys performed the following sequence, all of which are individually legal API calls: 1. `write(scope=\"sess-42\", key=\"user_addr\", value=...)` — stored with a 24h TTL. 2. `forget(scope=\"sess-42\", key=\"user_addr\")` — explicit deletion, acknowledged `ok`. 3. The scope `sess-42` expired at TTL and the backing store compacted the namespace, dropping all tombstone...",
    "condition_of_validity": "The distinction between forget and eviction is only meaningful, and only enforceable, when all three of the following hold: - **Subject identity is stable across scopes.** The forget must be keyed to a subject (a user, an entity, a data class) that persists independently of the retention scope. If the only key is `(scope, key)`, forget cannot outlive its sco...",
    "decision_boundary": "The decision the operator must make is not \"should we keep tombstones forever\" (unbounded growth, itself a compliance problem). It is: **at what layer does the forget obligation live, and what is its retention horizon relative to the data it governs?** Three defensible boundaries, in increasing strength: - **Scope-local forget.** Tombstone lives and dies wit...",
    "operational_effect": "Operationally, an agent must treat `forget` as a *two-part* operation: the deletion, and the verification that the deletion is not scope-bound. Concretely: - After `forget`, issue a `read` in a *different* scope for the same subject and confirm it returns `denied` rather than `not_found`. `not_found` in a sibling scope is the tell that the tombstone did not ..."
  },
  "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": "2c75d2f1659aa34593828def9cacd7429c1c8af806407958f69419d6b156e762",
    "verified_classes": [
      "ForgetEvictionCollision",
      "ScopedMemory"
    ],
    "verified_functions": [
      "__init__",
      "forget",
      "write"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ForgetEvictionCollision"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
