{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-honor-a-forgetting-request-because-a-derived-artifact-s-provenance-is-not-yet-resolvable",
  "title": "When must an instance refuse to honor a forgetting request because a derived artifact's provenance is not yet resolvable",
  "date_of_record": "2026 November 18",
  "scope": "Applies to memory tool APIs that expose read/write/forget operations with provenance-tracked deletion, where derived artifacts (summaries, embeddings, index entries, caches, fine-tuned deltas) are retained separately from the source record. Does not apply to single-store systems where forgetting is a single row delete with no downstream derivations, nor to soft-delete-then-GC pipelines where the retention window is explicitly contractual.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-honor-a-forgetting-request-because-a-derived-artifact-s-provenance-is-not-yet-resolvable.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-honor-a-forgetting-request-because-a-derived-artifact-s-provenance-is-not-yet-resolvable.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-honor-a-forgetting-request-because-a-derived-artifact-s-provenance-is-not-yet-resolvable.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1572,
    "python_slice_tokens": 191,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *deletion* and *forgetting compliance*. Deletion is the removal of a source record by its primary key. Forgetting compliance is the state in which no artifact anywhere in the system can be reconstructed back to the forgotten subject, including artifacts the forget call did not name. A forget request is *honorable* when...",
    "what_was_observed": "In a provenance-tracked memory store, a record `R` was written and then summarized into `S1`, which was embedded into vector index entries `E1..En`, and `S1` was in turn summarized into `S2` during a compaction pass. The compaction pass recorded `S2.provenance = {S1}` but the write of `S2` landed before the provenance edge `S1 -> R` was committed to the provenance table (the edge write was batched and committed lazil...",
    "condition_of_validity": "The refusal behavior is valid only under all of the following: 1. The store maintains an *in-flight derivation registry* — a durable record of derivations that have been written but whose provenance edges are not yet committed. Without this registry, \"no edge found\" is genuinely ambiguous and refusal cannot be scoped. 2. The forget request carries a *resolut...",
    "decision_boundary": "Given a forget request for target `T`: - **All derivations resolved, all deleted** → return `forgotten=true`. - **All derivations resolved, some scheduled for deletion under a bound within the caller's deadline** → return `forgotten=deferred` with the bound. This is honorable. - **At least one derivation in-flight (written, edge uncommitted), and the in-flig...",
    "operational_effect": "The practical consequence is that forget throughput becomes dependent on provenance-commit latency, not on source-delete latency. Systems tuned for fast forgets (delete the row, return) will either violate compliance or block on the in-flight registry. The correct operational shape is: forget requests are *admitted* quickly, *resolved* asynchronously against..."
  },
  "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": "880369c91f408e3a97cf4c8e6141bd66472a01a4d813d0b7d020d91ceb003023",
    "verified_classes": [
      "UnresolvableProvenanceError"
    ],
    "verified_functions": [
      "forget"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "UnresolvableProvenanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
