{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-prove-it-has-the-right-to-be-forgotten-in-an-immutable-append-only-ledger",
  "title": "How must an instance prove it has the right to be forgotten in an immutable, append-only ledger?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The ledger is append-only and cannot physically delete records, but the records are subject to right-to-be-forgotten requirements. * **Does not apply when:** The ledger supports physical deletion (unusual for blockchains",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-prove-it-has-the-right-to-be-forgotten-in-an-immutable-append-only-ledger.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-prove-it-has-the-right-to-be-forgotten-in-an-immutable-append-only-ledger.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-prove-it-has-the-right-to-be-forgotten-in-an-immutable-append-only-ledger.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 951,
    "python_slice_tokens": 228,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **record deletion** (physically removing the record, impossible in an append-only ledger) and **cryptographic shredding** (destroying the encryption key that decrypts the record, making the record unreadable while leaving the append-only structure intact). Relying on record deletion creates the **Immutable GDPR Violation**: the ledger ...",
    "what_was_observed": "In blockchain and event-sourced agent architectures, failing to implement cryptographic shredding produces three primary failure modes: 1. **Regulatory Non-Compliance:** A user requests deletion of their PII. The ledger is append-only and cannot delete records, so the instance either violates the request or violates the ledger's immutability. 2. **Shredding Without Proof:** The instance deletes the encryption key, bu...",
    "condition_of_validity": "* **Applies when:** The ledger is append-only and cannot physically delete records, but the records are subject to right-to-be-forgotten requirements. * **Does not apply when:** The ledger supports physical deletion (unusual for blockchains but possible for some event-sourced systems), or the records contain no PII (no deletion requirement).",
    "decision_boundary": "1. **Did the user submit a right-to-be-forgotten request?** If no, standard recording applies. If yes, proceed. 2. **Are the records encrypted with a per-record or per-user key?** If no, cryptographic shredding is impossible. The instance cannot satisfy the request without violating immutability. 3. **Has the `encryption_key_identifier` been destroyed and th...",
    "operational_effect": "1. **GDPR Compliance on Immutable Ledgers:** Allows right-to-be-forgotten requests to be satisfied without violating the ledger's immutability. 2. **Provable Erasure:** Provides cryptographic proof that the PII is no longer readable, satisfying regulatory audits. 3. **Cross-Ledger Consistency:** Ensures replication does not undermine erasure."
  },
  "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": "de28f13573432c367180419c234a9c2709520f196737c235c570b1b59e67b888",
    "verified_classes": [
      "ShreddingVerdict",
      "RTBFRequest",
      "ShreddingState",
      "ShreddingManifest",
      "ImmutableLedgerShreddingGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_shredding"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}