{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-forget-operation-succeed-while-the-underlying-bytes-remain-recoverable-the-tombstone-before-erasure-invariant-in-scoped-memo",
  "title": "Why does an instance of a \"forget\" operation succeed while the underlying bytes remain recoverable: the tombstone-before-erasure invariant in scoped memory APIs",
  "date_of_record": "2026 November 16",
  "scope": "Applies to memory tool APIs that expose `write`, `read`, and `forget` (or `delete`) operations over scoped retention domains with redaction and deletion guarantees, where the backend is a log-structured or append-only store with asynchronous compaction. Does not apply to synchronous in-place-overwrite stores (e.g., single-row key/value with immediate `fsync`-truncated value) or to stores where `forget` is defined as a hard cryptographic erasure of a per-record key.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-forget-operation-succeed-while-the-underlying-bytes-remain-recoverable-the-tombstone-before-erasure-invariant-in-scoped-memo.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-forget-operation-succeed-while-the-underlying-bytes-remain-recoverable-the-tombstone-before-erasure-invariant-in-scoped-memo.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-forget-operation-succeed-while-the-underlying-bytes-remain-recoverable-the-tombstone-before-erasure-invariant-in-scoped-memo.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1668,
    "python_slice_tokens": 294,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A memory API's `forget` call has two distinct semantics that are routinely conflated by callers and sometimes by the implementation itself: 1. **Visibility removal** — the record is no longer returned by `read` within its scope, and is no longer counted against retention quota. This is a *logical* property, enforced at the read path. 2. **Byte erasure** — th...",
    "what_was_observed": "In a scoped-retention memory service backed by an append-only segment log with periodic compaction, the following sequence was reproduced: - `write(scope=\"tenant-A\", key=\"k1\", value=PII)` appends a segment record `{op: WRITE, key: k1, ttl: 30d}`. - `forget(scope=\"tenant-A\", key=\"k1\", reason=\"redaction\")` appends a segment record `{op: TOMBSTONE, key: k1}` and returns `{\"status\": \"forgotten\"}` synchronously. - `read(s...",
    "condition_of_validity": "The tombstone-before-erasure ordering is valid — and `forget` returning success is safe to interpret as *visibility removal only* — under these conditions: - The backend is append-only or copy-on-write, so physical erasure requires a compaction/GC pass that rewrites or drops segments. - `forget` is synchronous only for the tombstone append; compaction is asy...",
    "decision_boundary": "The operational decision is whether a given `forget` call site requires visibility removal or byte erasure, and how to bridge the gap when it requires the latter: - **Visibility removal is sufficient** when the threat model is \"the application must not see it\" — e.g., user-facing deletion, quota release, scope isolation. Treat `forget` success as terminal. D...",
    "operational_effect": "Downstream effects observed: - **Compliance pipelines** that logged `forget` success as \"erasure complete\" produced audit records that were false during the compaction window. Remediation required re-defining the completion signal as a compaction-barrier acknowledgment, not the `forget` return. - **Backup and replica lag** extended the window past the primar..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "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": "ff644f245b89d170a6697833f3774ced6b2d4527b7571cc71e4c566fedd24f95",
    "verified_classes": [
      "ErasureNotConfirmedError",
      "ForgetReceipt"
    ],
    "verified_functions": [
      "forget_and_require_erasure"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ErasureNotConfirmedError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
