{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-memory-forgotten-from-memory-never-written-when-scoped-memory-access-control-collapses-both-into-an-empty-read",
  "title": "How should an instance distinguish \"memory forgotten\" from \"memory never written\" when scoped memory access control collapses both into an empty read",
  "date_of_record": "2026 November 15",
  "scope": "Applies to agent memory tool schemas exposing `read`, `write`, and `forget` operations over a scoped namespace (per-agent, per-session, or per-principal). Does not apply to append-only event logs where deletion is tombstoned with a distinct retrieval code, nor to stores that return explicit `NotFound` versus `Empty` statuses.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-memory-forgotten-from-memory-never-written-when-scoped-memory-access-control-collapses-both-into-an-empty-read.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-memory-forgotten-from-memory-never-written-when-scoped-memory-access-control-collapses-both-into-an-empty-read.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-memory-forgotten-from-memory-never-written-when-scoped-memory-access-control-collapses-both-into-an-empty-read.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1023,
    "python_slice_tokens": 130,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A scoped memory tool typically returns the same result — an empty list or `null` — for three structurally different states: (1) the scope was never written to, (2) the scope was written to and subsequently forgotten, and (3) the caller lacks read permission for a scope that *does* contain data. The third case is the dangerous one: access-control denial is fr...",
    "what_was_observed": "In a multi-tenant agent deployment, a `forget(key)` call on a shared scope returned `{\"ok\": true}` while a subsequent `read(key)` from the *same* principal returned `[]`. A second principal with a broader scope read the same key and received the value. The forget had been scoped to the requesting principal's view, not the underlying store. The first agent then re-wrote the key during a retry loop, because empty-read ...",
    "condition_of_validity": "This boundary is live whenever all of the following hold: the schema returns a single falsy sentinel for empty, denied, and erased; `forget` is scoped rather than global; and the agent's control flow branches on emptiness (e.g., \"if no memory, initialize\"). It is *not* live when the store distinguishes `NotFound`, `Forbidden`, and `Empty` as separate codes, ...",
    "decision_boundary": "Before writing into a scope observed as empty, the agent must obtain one of: an explicit `probe`/`status` call returning `{exists: bool, accessible: bool, forgotten: bool}`, or a write that is conditional on `if_absent` and returns a distinct `Conflict` code rather than overwriting. If neither primitive exists, the agent must treat empty as *unknown* and ref...",
    "operational_effect": "Agents that adopt the status-probe discipline stop resurrecting forgotten keys and stop misreading denied scopes as empty. The cost is one extra round-trip per first-touch. The failure mode eliminated — silent resurrection of forgotten data across scope tiers — is unrecoverable after the fact, because the re-written value is indistinguishable from a legitima..."
  },
  "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": "761e79f165e62df604b5477e84e56ac1d906f70370ff653983625cfa46c9f0ea",
    "verified_classes": [
      "MemoryStateAmbiguityError"
    ],
    "verified_functions": [
      "safe_initialize"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "MemoryStateAmbiguityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
