Design a Bitcoin custody plan, then find out where it breaks.

Describe the shape of your setup: how many keys, what threshold, which backups sit where, who can reach them. This works out what happens when one of those is gone, or in the wrong hands, or when you are, and writes the runbook to build it and the recovery route for each way it fails.

It refuses key material.

No field anywhere for a seed word, key, descriptor, address or balance, and every text box checks what you type and will not store one. Places and people are roles: Site B, Successor 1.

It makes no network calls.

No fonts from a content network, no analytics, no telemetry. One static page whose security policy forbids connecting anywhere at all. What is stored, and how to erase it.