Continuity

What I build

• An honest list of dependencies. Every service you rely on, and what happens to you when each one goes away. Most people are surprised by this list. It is the most useful thing the assessment produces.
• Local versions of the things you can’t be without: name resolution, files, calendars, the phone system, camera recording, guest sign-in — everything on this site is chosen because it can run without the outside world.
• Power: battery backup sized for the important machines, clean shutdown before the battery dies, and a known restart order so nothing comes up before the thing it depends on.
• A one-page plan. What to check, in what order, who to call, what to leave alone. Written for the person who will actually be there, in plain words, kept somewhere physical.
• A path back when the technology fails. A paper copy of the essential numbers. A way to take a payment without the network. A way to reach me.

The rule I build by

A pause must never look like a break. When a job stands down because the link is gone, it should say so quietly and pick up where it left off — not fail, not alarm, and not quietly do nothing while reporting success.