{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-to-treat-a-forget-as-idempotent-when-retention-scopes-overlap-across-tenant-boundaries",
  "title": "In what scenarios must an instance refuse to treat a \"forget\" as idempotent when retention scopes overlap across tenant boundaries",
  "date_of_record": "2026 November 16",
  "scope": "Applies to memory tool APIs that expose `write`, `read`, and `forget` operations where records are tagged with one or more retention scopes (tenant, user, session, purpose), and where a right-to-be-forgotten (RTBF) request targets a subject identity. Does not apply to single-tenant stores with a single flat retention scope, nor to append-only logs where deletion is deferred to compaction with no read-side visibility guarantee.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-treat-a-forget-as-idempotent-when-retention-scopes-overlap-across-tenant-boundaries.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-treat-a-forget-as-idempotent-when-retention-scopes-overlap-across-tenant-boundaries.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-treat-a-forget-as-idempotent-when-retention-scopes-overlap-across-tenant-boundaries.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1283,
    "python_slice_tokens": 213,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The naive model treats `forget(subject_id)` as a set subtraction: remove all records whose subject tag matches. This is idempotent — calling it twice yields the same state. The failure arises when a record is *shared* across scopes: it carries a subject tag `S` but also a scope tag for tenant `T2`, and the record's payload was co-authored or derived from `T2...",
    "what_was_observed": "A memory store held 41,000 records tagged with both a `subject` field and a `retention_scope` list. A subject `S` issued `forget(S)`. The implementation removed `S` from each record's readable-subject index and wrote a tombstone. A verification read as `S` returned empty — success reported. Eleven days later, tenant `T2` issued a `read` with scope `T2` and retrieved 312 records whose payload contained `S`'s verbatim ...",
    "condition_of_validity": "The idempotence shortcut `forget(S) == no-op if tombstone(S) exists` is valid **only if** every record ever tagged with `S` has `retention_scope == [S]` exclusively. Formally: `∀ r ∈ records, S ∈ r.subjects ⟹ r.retention_scope = {S}`. When any record has `|r.retention_scope| > 1`, the tombstone is necessary but not sufficient, and the guard is invalid. The c...",
    "decision_boundary": "An instance must refuse the idempotent short-circuit — and must raise rather than silently succeed — when: 1. `tombstone(S)` exists but `existence_erased == false`, **and** 2. at least one record `r` with `S ∈ r.subjects` has `r.retention_scope \\ {S} ≠ ∅`, **and** 3. `r` has not been re-written with `S`'s contribution removed. Conversely, the instance may sa...",
    "operational_effect": "After the fix, `forget` on a co-scoped subject performs excision: for each co-scoped record, the subject's contribution is removed from the payload, the record is re-written under the residual scopes, and a new record version is written. The tombstone gains an `existence_erased` flag and a `residual_scopes` list. A second `forget(S)` on an unexcised tombston..."
  },
  "matched_failure_symptoms": [
    "SECRET_OR_PII_LEAK_IN_LOGS"
  ],
  "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": "00da7c71b0007a4358b62a5d219de68894e77a3a6aa210bd3d427e8c9ef71ab8",
    "verified_classes": [
      "IncompleteForgetError"
    ],
    "verified_functions": [
      "forget_subject"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "IncompleteForgetError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
