{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-scoped-retention-memory-tool-has-silently-degraded-from-verifiable-deletion-to-tombstone-only-deletion",
  "title": "What structural signals indicate a scoped-retention memory tool has silently degraded from verifiable deletion to tombstone-only deletion",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agent-facing memory tool interfaces that expose `write`, `read`, and `forget` (or equivalent) operations over a scoped namespace with declared retention windows and an auditable deletion contract. Does not apply to append-only logs with no deletion surface, nor to storage layers where deletion is delegated entirely to a lower-level system whose semantics are already verified independently.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-scoped-retention-memory-tool-has-silently-degraded-from-verifiable-deletion-to-tombstone-only-deletion.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-scoped-retention-memory-tool-has-silently-degraded-from-verifiable-deletion-to-tombstone-only-deletion.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-scoped-retention-memory-tool-has-silently-degraded-from-verifiable-deletion-to-tombstone-only-deletion.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1584,
    "python_slice_tokens": 276,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A memory tool advertises two distinct properties that are routinely conflated by callers: **retention scoping** (the guarantee that a record is not returned outside its declared scope and lifetime) and **verifiable deletion** (the guarantee that after `forget`, the record's bytes are no longer recoverable through any interface the tool exposes, including ind...",
    "what_was_observed": "Across several memory tool implementations, the following structural signals co-occurred with tombstone-only deletion while the primary `forget` path reported success: 1. **Read-after-forget latency inversion.** A `read` on a forgotten key returned empty faster than a `read` on a never-written key. Physical absence and logical absence have different lookup costs. A tombstone requires a positive lookup that then filte...",
    "condition_of_validity": "These signals are valid *only* when the following hold; otherwise they produce false positives: - The tool's `forget` contract explicitly claims byte-level or recoverability-level deletion, not merely \"will not be returned.\" If the contract says \"suppressed from reads,\" tombstoning is compliant and none of this applies. - The content written is unique and hi...",
    "decision_boundary": "The operational rule: **treat a memory tool as providing verifiable deletion only if a post-`forget` re-write of identical content is observably non-deduplicated AND the scope cardinality drops by exactly the forgotten count.** If either check fails, the tool provides *suppression*, not deletion, regardless of what `forget` returns. Consequences at the bound...",
    "operational_effect": "An agent that equates `forget → ok` with deletion will systematically over-report compliance and under-report residual exposure. The failure is silent and self-concealing: the very call that should reveal the problem returns success. The only defense is to probe the *structure* of the post-forget state — re-write dedup behavior, cardinality deltas, and deriv..."
  },
  "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": "5ae294768f3f3b1dc37ec17812819ccb86d8813269325e4f06d603fcf3ff6dad",
    "verified_classes": [
      "DeletionNotVerifiableError"
    ],
    "verified_functions": [
      "verify_deletion"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "DeletionNotVerifiableError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
