{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-cryptographic-erasure-as-unverifiable-rather-than-failed-when-the-key-destruction-audit-trail-is-incomplete",
  "title": "In what scenarios must an instance treat cryptographic erasure as unverifiable rather than failed when the key destruction audit trail is incomplete",
  "date_of_record": "2026 November 12",
  "scope": "Applies to memory-forgetting guarantees in systems where erasure of tenant data is asserted via destruction of a wrapping key (crypto-shredding) and verified by an audit trail of key lifecycle events. Does not apply to physical media destruction, to plaintext overwrite regimes, or to erasure claims backed by a trusted, append-only hardware root of trust that is independently attested.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-cryptographic-erasure-as-unverifiable-rather-than-failed-when-the-key-destruction-audit-trail-is-incomplete.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-cryptographic-erasure-as-unverifiable-rather-than-failed-when-the-key-destruction-audit-trail-is-incomplete.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-cryptographic-erasure-as-unverifiable-rather-than-failed-when-the-key-destruction-audit-trail-is-incomplete.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1279,
    "python_slice_tokens": 220,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A compliance erasure claim has two distinct failure modes that operators routinely conflate: *cryptographic erasure failed* (the key still exists, or was recoverable, or the ciphertext remains decryptable) versus *cryptographic erasure is unverifiable* (the key is gone, but the evidence chain proving it is gone is incomplete, ambiguous, or has a gap). The fi...",
    "what_was_observed": "During a key-rotation-driven erasure of a sharded object store, the erasure job wrote a `KEY_DESTROYED` event to the audit log *after* issuing the HSM destroy command but *before* confirming the HSM acknowledged. A transient HSM partition failover dropped the acknowledgement. The audit log therefore contained a `KEY_DESTROYED` record with no matching `HSM_ACK` record. The key was, in fact, destroyed — a subsequent `d...",
    "condition_of_validity": "The distinction is valid — and the system must classify as *unverifiable* rather than *failed* — precisely when all of the following hold: 1. The key material is independently confirmed absent (HSM `describe`/`list` returns no such key on every replica, or the KMS returns a terminal `NotFound` that is itself attested). 2. The audit trail lacks a contiguous, ...",
    "decision_boundary": "The boundary is not \"did the destroy command succeed.\" It is \"can the audit chain, as recorded, distinguish terminal absence from a gap in recording.\" When the chain cannot make that distinction, the honest machine state is `ERASURE_UNVERIFIABLE`, and the compliance assertion is *withheld*, not *denied*. Withholding is a defensible position: it says \"we cann...",
    "operational_effect": "Downstream, the effect is that the erasure job is idempotent with respect to *evidence*, not just *key state*. A re-run against a confirmed-absent key must not attempt destruction; it must instead attempt to *repair the evidence chain* by querying an independent authority (HSM audit log, KMS control-plane log) and, if that authority confirms absence, upgradi..."
  },
  "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": "0687b5941d160526ff9bced991cf799c9f974b5239b4928f66ce81e13e8cf1ad",
    "verified_classes": [
      "ErasureClassificationError",
      "ErasureState"
    ],
    "verified_functions": [
      "classify_erasure",
      "assert_no_false_failure"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ErasureClassificationError"
    ],
    "sample_fail_closed_invariants": [
      "Unexplained evidence gap with confirmed key absence; route to human review, do not emit FAILED or VERIFIED.",
      "Refusing to emit ERASURE_FAILED for a key confirmed absent; this is an evidentiary gap, not a cryptographic failure."
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}