{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-forget-as-a-two-phase-commit-rather-than-a-single-tombstone-write",
  "title": "Under what conditions must an instance treat \"forget\" as a two-phase commit rather than a single tombstone write",
  "date_of_record": "2026 November 16",
  "scope": "Applies to any memory subsystem that exposes a deletion API carrying an auditability guarantee (e.g., \"deleted means unrecoverable and provably so\"), where memory is physically distributed across replicas, caches, embedding indices, and derived summaries. Does not apply to single-node stores with no derived state, nor to soft-delete semantics where auditability is explicitly waived.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-forget-as-a-two-phase-commit-rather-than-a-single-tombstone-write.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-forget-as-a-two-phase-commit-rather-than-a-single-tombstone-write.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-forget-as-a-two-phase-commit-rather-than-a-single-tombstone-write.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1625,
    "python_slice_tokens": 230,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A *tombstone* is a logical marker asserting that a key is dead. A *forget* is a physical commitment that the payload no longer exists anywhere the system can reach, plus an audit record proving the transition. These are not the same operation, and the gap between them is where auditable deletion fails. The non-obvious invariant: **a forget is only auditable ...",
    "what_was_observed": "In a system with three storage tiers (primary KV, an approximate-nearest-neighbor index, and a rolling summarizer), a `forget(key)` call returned success in 4 ms. The audit log recorded a deletion timestamp. Six hours later, a retrieval probe reconstructed the \"forgotten\" fact verbatim from the summarizer's cached output, which had been derived from the key before deletion and was never invalidated. The failure mode ...",
    "condition_of_validity": "The two-phase forget is valid only when all four hold: 1. **Tombstone durability precedes erasure.** The intent log entry (key, epoch, requester, derivation-lineage set) is fsynced before any payload byte is dropped. If the process dies after erasure but before the intent log, the deletion is unauditable and must be treated as a corruption event, not a succe...",
    "decision_boundary": "The boundary is not \"is this a large deletion\" but **\"does the payload have derivations the store did not author.\"** For a key with no derived artifacts and no replicas, a single tombstone is a valid forget; the two-phase machinery is overhead. The moment a key feeds a summarizer, an embedding index, a cache, or a cross-region replica, the single-write forge...",
    "operational_effect": "Systems that adopt the two-phase forget observe three shifts. First, `forget` latency becomes bimodal: the pre-commit (tombstone + intent) is milliseconds; the audit seal arrives asynchronously, and callers must handle a `PENDING` state rather than assuming completion. Second, the derivation-lineage index becomes a first-class, hot-path write cost — every de..."
  },
  "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": "4f75219cf4a841dfbd82ca349b08dd7bd533ec6fe9a630c721cac101e1277466",
    "verified_classes": [
      "ForgetAuditViolation"
    ],
    "verified_functions": [
      "forget"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ForgetAuditViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
