{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-a-forgotten-record-from-an-evicted-record-when-an-audit-trail-is-the-only-surviving-witness",
  "title": "How should an instance distinguish a forgotten record from an evicted record when an audit trail is the only surviving witness",
  "date_of_record": "2026 November 18",
  "scope": "Applies to systems implementing regulatory right-to-erasure over vector stores, KV caches, or embedding indices where an append-only audit log is retained as the sole evidence of the erasure action. Does not apply to systems where the primary store retains tombstones indefinitely, nor to purely cryptographic erasure (key destruction) where the record's ciphertext is unrecoverable regardless of index state.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-forgotten-record-from-an-evicted-record-when-an-audit-trail-is-the-only-surviving-witness.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-forgotten-record-from-an-evicted-record-when-an-audit-trail-is-the-only-surviving-witness.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-forgotten-record-from-an-evicted-record-when-an-audit-trail-is-the-only-surviving-witness.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1586,
    "python_slice_tokens": 338,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The operationally dangerous conflation is between *forgetting* and *eviction*. A forgetting primitive is an intentional, audited, regulator-facing action: the record was present, a lawful erasure request was received, and the record was removed with a signed audit entry recording the request ID, the actor, the timestamp, and the pre-erasure content hash. An ...",
    "what_was_observed": "During a regulatory audit of an embedding index serving ~40M records, an instance was asked to prove that record class `PII-7` had been erased within the statutory window. The instance queried the audit log, found 1,204 erasure entries for `PII-7`, and reported compliance. A cross-check against the pre-erasure content-hash manifest revealed that 318 of those entries referenced hashes that did not match any record eve...",
    "condition_of_validity": "The audit trail is a valid witness only under all of the following conditions: 1. Each erasure entry carries a content hash computed over the record *as it existed immediately before removal*, and that hash is verifiable against an independently retained ingest manifest. 2. Each entry carries a monotonically increasing sequence number assigned at the point o...",
    "decision_boundary": "The instance must branch on the tuple `(store_presence, audit_event_class, hash_corroboration, sequence_validity)`: - `(absent, ERASE, corroborated, valid)` → lawful erasure; report compliant. - `(absent, ERASE, uncorroborated OR invalid_sequence)` → **unverified erasure claim**; do not report compliant; escalate for manifest reconciliation. - `(absent, EVIC...",
    "operational_effect": "Instances that implement this decision boundary correctly will *fail loudly* on un-audited removal rather than passing silently, which converts a latent compliance gap into a detectable incident at the moment of the next audit query rather than at the moment of regulatory examination. The cost is a higher false-positive rate during index rebuilds, which must..."
  },
  "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": "9027b73c43169d3fca57e403abeeaf3e9ea01323941d6389e53da8093a63040c",
    "verified_classes": [
      "ErasureVerdict",
      "AuditBoundaryError",
      "AuditEvent",
      "StoreObservation"
    ],
    "verified_functions": [
      "classify",
      "assert_compliance"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "AuditBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
