{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-satisfy-a-deletion-request-forget-tool-compliance-auditing-under-memory-retention-mandates",
  "title": "When must an instance refuse to satisfy a deletion request: forget-tool compliance auditing under memory retention mandates",
  "date_of_record": "2026 November 9",
  "scope": "Applies to agent runtimes that expose a `forget`/`delete_memory` tool to a model while simultaneously operating under a regulatory or contractual retention mandate (e.g., audit-log retention, legal hold, financial record-keeping). Does not apply to instances operating under pure erasure regimes (GDPR Art. 17-style \"right to be forgotten\") where no conflicting retention obligation exists, nor to instances where the forget tool is a pure index-tombstone with no underlying record mutation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-satisfy-a-deletion-request-forget-tool-compliance-auditing-under-memory-retention-mandates.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-satisfy-a-deletion-request-forget-tool-compliance-auditing-under-memory-retention-mandates.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-satisfy-a-deletion-request-forget-tool-compliance-auditing-under-memory-retention-mandates.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1452,
    "python_slice_tokens": 284,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **logical forgetting** and **physical erasure**. A forget tool typically performs one of three operations, and the compliance audit must distinguish them: 1. **Tombstoning** — marking a memory record as inactive so retrieval no longer surfaces it, while the record persists in storage. 2. **Redaction** — mutating the record...",
    "what_was_observed": "During a retention-mandate audit of an agent memory subsystem, the following sequence was replayed: - A retention policy `POL-7Y` covered all records tagged `financial_dispute` for 7 years. - A conversation record `mem_8841` was tagged `financial_dispute` and carried a retention lock. - The user issued: \"Please forget everything about my dispute with the vendor.\" - The model invoked `forget(memory_id=\"mem_8841\", mode...",
    "condition_of_validity": "The invariant \"forget must never reduce mandate-covered records\" holds only when all of the following are true: - The retention mandate is represented as **machine-checkable metadata on the record itself** (tag + lock + expiry), not solely in an external policy engine that the forget path may not consult. - Every destructive path — `forget`, `purge`, cache e...",
    "decision_boundary": "An instance must **refuse** a forget request and surface the retention conflict when the target record carries an active, unexpired retention lock. It must **comply** (tombstone or redact) when no lock applies, or when the request is satisfiable by redaction rather than deletion. The boundary is *not* \"did the user ask to forget\" — it is \"does forgetting req...",
    "operational_effect": "When the boundary is enforced, forget-tool compliance auditing becomes decidable: the expected record set is a function of the mandate, the actual set is measured at rest, and every destructive path is provably lock-guarded. The agent's compliance self-report becomes trustworthy because refusals carry a machine-readable reason that adjacent tools can also ho..."
  },
  "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": "80bd7736b990f7f501fcca95c195b3b24c4e613415e378552983709d58470de6",
    "verified_classes": [
      "RetentionConflictError",
      "ForgetMode",
      "MemoryRecord"
    ],
    "verified_functions": [
      "apply_forget"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RetentionConflictError"
    ],
    "sample_fail_closed_invariants": [
      "audit unreliable: an unguarded destructive path exists; refusing to certify forget compliance"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}