Your Wi-Fi router stops working.
It's 8 a.m. on a Tuesday. You restart it. It doesn't come back. Dead.
Here's what happens over the next few hours:
Your smart thermostat can't maintain its schedule because it needs the internet to check the weather forecast and optimize your heating. Your house starts getting cold (or hot, depending on season).
Your security cameras go offline. You can't check the video feed anymore. If someone breaks in, you have no live surveillance.
Your smart lock can't update its access logs. Your spouse gets home and can't unlock the door with her phone. She has to use her physical key, which she doesn't have, because of course not -- why would she carry it? The house has a smart lock.
Your Ring doorbell camera stops working. You can't see who's at the door without going to the window.
Your kids' tablets can't connect to their streaming apps. So they come find you repeatedly asking what to do, because they don't have anything else to do.
Your smart TV is useless without WiFi.
Your Alexa device can't answer questions or control your smart home.
Your automated pet feeder misses its 6 p.m. feeding schedule because it needs the internet to function. Your dog doesn't eat on time.
Your home security system can't send alerts to your phone if it detects an intrusion.
And for you: your work VPN disconnects because your home internet is down. Your afternoon video meeting gets cancelled. You miss a critical decision. You look flaky to your boss.
This is the Chain of Dependency in action. One dead router cascades into the failure of a dozen different systems.
And that's just one example. The chain goes deeper.
The Deeper Chain
The Wi-Fi router depends on your Internet Service Provider.
Your ISP depends on cables and infrastructure that runs through your neighborhood -- and those cables can fail, be cut, or be damaged.
Your ISP also depends on their upstream providers and the internet backbone, which all depend on data centers, which all depend on the power grid.
The power grid depends on weather, maintenance, and whoever is operating it that day. It can fail due to storms, earthquakes, or grid cascades.
Your phone depends on cell towers.
Cell towers depend on the power grid.
Cell towers also depend on the internet backbone, so if the internet goes down in your region, cellular connectivity can be affected too.
Your bank depends on servers in data centers.
Those servers depend on the internet.
Those servers depend on the power grid.
Your email depends on cloud infrastructure.
Your cloud storage depends on servers in data centers.
Almost everything you rely on depends on the power grid, the internet, and at least three other things you don't control and can't directly access.
This is the modern world. We've built a society where almost every critical system depends on at least two other systems, and those depend on two more. It's efficient. It's resilient against individual failure points. It's also terrifyingly fragile if you're the one person trying to survive when multiple links in the chain break.
What's Actually Critical vs. What's Convenient
The problem is that we've lumped together things that are critical with things that are merely convenient, and we've hidden them behind the same digital infrastructure.
Your smart thermostat is convenient. It's nice to adjust the temperature from your phone. It's nice that it learns your schedule. If it goes offline, you're inconvenienced. Your house gets a little cold or a little hot.
Your security cameras are more serious. They're a deterrent and a record. If they go offline during a break-in, you've lost both.
Your smart lock is somewhere in between. It's convenient if it works. It's a disaster if it's your only way to unlock the door and the internet dies.
Your emergency contacts being unreachable is genuinely dangerous. If your family can't contact you, you can't coordinate. If you can't reach critical services, you can't get help.
And here's the thing: most of these are stacked on the same infrastructure. Your smart thermostat and your security cameras are both on WiFi. Your WiFi depends on your router. Your router depends on your ISP. Your ISP depends on the power grid.
If any link in that chain breaks, multiple things fail at once.
The Analog Backup Strategy
Here's how you actually solve this: you identify what's critical and you give it an analog backup.
For emergency contacts: Print them. Write them down. Ready.gov publishes printable emergency contact cards for exactly this purpose. Put them somewhere accessible that doesn't require a phone or internet. A card in your wallet. A list on the fridge. Laminated. Old school.
If your phone dies, gets stolen, or runs out of battery, you can still call 911 from a neighbor's phone or a payphone (do payphones still exist? okay, a neighbor's phone). You can still contact your family because their numbers are written down.
For your front door lock: Keep a physical key. Not locked in a drawer in your bedroom where you'd forget about it. On your keychain. Your spouse's keychain. Your trusted neighbor's place. If the smart lock fails, you can still get in your house.
If you get locked out because the power is down and the smart lock won't respond, a physical key solves that.
For your thermostat: Know how to override it. Most smart thermostats have a manual override that lets you set it to a specific temperature or switch to a fixed mode. Know where that button is. If internet goes down and your house is getting dangerously cold, you can manually set the thermostat to heating mode and lock it there.
For critical information: Your insurance policy numbers, your mortgage servicer, your doctor's contact info, your bank's emergency number -- write them down. Not "somewhere." In your emergency manual, which is a physical document that lives in your house.
For power-dependent essentials: Know where your breaker panel is. Know how to safely turn off your gas if there's a leak. Know where your water shutoff is. These are analog backups to digital infrastructure. If the internet is down but you have power, and something goes wrong, you need to be able to manually address it.
The Real Problem
The real problem with the Chain of Dependency is that we don't think about it until something breaks.
You don't think about your internet depending on the power grid until the power goes out. You don't think about your smart lock being a single point of failure until your phone dies and you can't get in your house.
We've optimized for normal conditions. We've built systems that work great 99.9% of the time. But that 0.1% where everything fails at once? We're completely unprepared.
And it doesn't take a massive disaster for the chain to break. A single squirrel chewing through a power line can cascade into your smart thermostat failing, your security cameras going offline, your smart lock not working, and your ability to reach your family being compromised.
What an Actual Resilient System Looks Like
A resilient system has backups. It has manual overrides. It has ways to function when the digital infrastructure is gone.
You keep important numbers written down.
You have physical keys for locked doors.
You know how to manually override your thermostat.
You have a paper map (not on your phone).
You have a flashlight that doesn't depend on your phone charging.
You have a way to communicate with your family that doesn't depend on cell networks.
Does this sound paranoid? Maybe. But it's also basic redundancy, the same thing engineers use to keep critical systems running.
An emergency manual -- a printed, physical document with critical information, contact numbers, and procedures -- is the analog backup layer for your entire digital life.
HRDCOPY manuals are essentially the analog backup for your digital world: every critical contact, every important account, every emergency procedure, printed and protected, so when the digital infrastructure fails, you still have access to the information that matters. You can also build this yourself with a binder and a printer -- the point is that the information needs to exist outside your phone, outside the cloud, outside the internet. When the Chain of Dependency breaks, a printed manual is the only thing that keeps functioning.