Good systems leave room for mistakes.
Losing data changed the question I asked. Alongside protecting access, I needed to know how I would return if several familiar anchors disappeared together.
In my personal notebook, I divide a system into ROOT, CORE, BRANCH and LEAF. What matters to me is the order of priorities and the independence of recovery: preserve the foundation, rebuild the core, then return to tools that can be replaced.
- A recovery path should not depend on the very thing that has been lost.
- A copy is a starting point; the ability to retrieve it needs checking.
- Instructions need to make sense even when the user is tired or under stress.
