{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-a-deletion-attestation-whose-scope-is-a-strict-superset-of-the-retention-scope-it-was-configured-with",
  "title": "Under what conditions must an instance refuse a deletion attestation whose scope is a strict superset of the retention scope it was configured with",
  "date_of_record": "2026 November 15",
  "scope": "Applies to memory tool APIs that expose paired `read`/`write`/`forget` operations gated by scoped retention policies and that emit deletion attestations covering a declared scope. Does not apply to single-tenant stores with no scoped retention, nor to attestations that are purely advisory (non-binding) log records.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-deletion-attestation-whose-scope-is-a-strict-superset-of-the-retention-scope-it-was-configured-with.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-deletion-attestation-whose-scope-is-a-strict-superset-of-the-retention-scope-it-was-configured-with.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-deletion-attestation-whose-scope-is-a-strict-superset-of-the-retention-scope-it-was-configured-with.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1680,
    "python_slice_tokens": 232,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A deletion attestation is a *claim about the absence of data within a scope*. The non-obvious boundary is between two superficially similar situations: 1. The instance receives a `forget(scope=S)` request where `S` is *equal to or a subset of* its configured retention scope `R` (i.e., `S ⊆ R`). Here the instance can honestly attest: it knows the universe of ...",
    "what_was_observed": "During a multi-shard consolidation, a coordinator issued `forget(scope=\"tenant:acme/*\")` to a shard whose retention configuration was `tenant:acme/region:eu/*`. The shard's `forget` handler matched the prefix, deleted the 41,203 keys it actually held, and — because the response schema only carried a boolean `ok` plus a key count — returned `ok=true, deleted=41203`. The coordinator aggregated this into an attestation ...",
    "condition_of_validity": "The refusal is *required* when all of the following hold: - The API's `forget` accepts a caller-supplied scope, and - The instance has a configured retention scope `R` that bounds the set of keys it can enumerate, and - The requested scope `S` is not a subset of `R` (`S ⊄ R`), and - The attestation is binding (consumed by an auditor, a downstream system, or ...",
    "decision_boundary": "The decision is a single containment test, but the consequence of getting it wrong is asymmetric, which is why it must be a hard refusal rather than a warning: Three tempting alternatives are all wrong: - **Silently narrow to `S ∩ R` and return `ok`.** This produces a valid-looking attestation for a scope nobody asked about. The caller believes `S` is covere...",
    "operational_effect": "After adopting the containment check, the consolidation path changed shape: superset `forget` calls now fail fast at the shard boundary with `ScopeEscalationError`, and the coordinator catches them, enumerates the shard map, and issues per-shard `forget` calls whose scopes are each contained in that shard's `R`. The coordinator then assembles the superset at..."
  },
  "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": "8c27c7d6dfabafe588018c31869ecb04c2e5bb51d3a9e86fe76e07f207ca1653",
    "verified_classes": [
      "ScopeEscalationError"
    ],
    "verified_functions": [
      "forget_and_attest"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ScopeEscalationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
