Destruction Package¶

A completely separate package from recovery, with its own secret and, recommended, a stricter 3 of 3 threshold, since destruction is irreversible.

Folder structure¶

02_DESTRUCTION
│
├── 01_DESTROY_AFTER_RECOVERY   (this gate matters, see below)
├── 02_EVIDENCE_INVENTORY
├── 03_DIGITAL_DATA
├── 04_PHYSICAL_MATERIAL
├── 05_DEVICES
└── 06_FINAL_CONFIRMATION

The most important distinction in this whole template¶

"Destroy everything" can directly conflict with legal retention requirements. Before anyone executes anything, sort every item into one of these three categories:

A. Legal / financial records: DO NOT DESTROY¶

Tax records
Estate documents
Property records
Insurance records
Business records
Anything under litigation or a legal hold

B. Personal material: destroy per your wishes¶

Private correspondence
Personal journals
Personal photographs
Old personal devices
Private files and archives

C. Sensitive secrets: destroy after recovery is confirmed complete¶

Old credentials
Backup codes
API keys
Recovery phrases that have already been superseded
Private keys that no longer control any assets
Authentication tokens

Why destruction requires recovery to finish first¶

If destruction could run before recovery, a mistake or a rushed custodian could wipe something your family still needed to access. The sequence in The LRDP Model puts a hard gate, 01_DESTROY_AFTER_RECOVERY, between "recovery confirmed complete" and "destruction secret can even be reconstructed." Category A material should ideally be excluded from the destruction package entirely, not just flagged. The safest default is to never put anything with a legal retention requirement anywhere near a "destroy" list.