{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-forget-a-memory-write-it-has-already-acknowledged-the-acknowledgment-without-provenance-boundary",
  "title": "When must an instance forget a memory write it has already acknowledged: The Acknowledgment-Without-Provenance Boundary",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent memory tool protocols where a `write`/`remember` call returns an acknowledgment (a handle, ID, or success token) that the agent subsequently treats as evidence the memory is durable and retrievable. Does not apply to synchronous transactional stores that return only after fsync and index commit, nor to fire-and-forget telemetry sinks where no acknowledgment is ever surfaced to the caller.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-forget-a-memory-write-it-has-already-acknowledged-the-acknowledgment-without-provenance-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-forget-a-memory-write-it-has-already-acknowledged-the-acknowledgment-without-provenance-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-forget-a-memory-write-it-has-already-acknowledged-the-acknowledgment-without-provenance-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1783,
    "python_slice_tokens": 373,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **acknowledgment** and **provenance**. An acknowledgment is a protocol-level fact: the tool received the payload and assigned it an identity. Provenance is an epistemic fact: the memory now exists in a store, is attributable to a source, and will be returned by a subsequent read under the same identity. These are not t...",
    "what_was_observed": "In a retrieval-augmented agent operating against a memory service that batched writes, the following sequence recurred: 1. Agent calls `write(content=\"user prefers ISO-8601 dates\", key=\"date_format\")`. 2. Service returns `{\"ok\": true, \"id\": \"m_8842\", \"provenance\": \"pending\"}`. 3. Agent stores `m_8842` in its working context and, in the same turn, calls `read(key=\"date_format\")`. 4. Read returns `null` — the batched w...",
    "condition_of_validity": "The rule \"treat uncommitted-provenance acknowledgments as absent\" is valid precisely when the following hold: - The write tool's acknowledgment does **not** guarantee that a subsequent read will return the payload. This is detectable: the response carries an explicit non-committed provenance state, or the tool's contract documents asynchronous commit, or emp...",
    "decision_boundary": "The agent must branch on provenance state, not on the `ok` field: - **Provenance committed** (`provenance: \"committed\"` or a synchronous contract): the ID is usable as evidence. Proceed; a subsequent read is expected to return the payload. A null read is now a genuine anomaly (eviction, corruption, key mismatch) and should raise. - **Provenance pending** (`p...",
    "operational_effect": "Enforcing the boundary converts a silent consistency bug into an explicit, catchable state. The agent no longer reasons over phantom memories; it either waits for commit or defers. The cost is added latency on the write path (a flush round-trip) and the need to track pending IDs separately from committed ones. The benefit is that the agent's belief state and..."
  },
  "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": "5b055f6286f75befe3e927a77128227cd4746a30bde81410f5e9174e84d43c6b",
    "verified_classes": [
      "ProvenanceState",
      "UncommittedProvenanceError",
      "MemoryHandle",
      "MemoryClient"
    ],
    "verified_functions": [
      "remember_and_confirm",
      "safe_read_back",
      "__init__",
      "write",
      "flush",
      "read"
    ],
    "verified_functions_count": 6,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UncommittedProvenanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
