By following the dependency map to its cascade points. Every community has a few facilities where one failure becomes many, and those are the places where better rooms, trusted people and tested materials change the outcome for everything downstream.
Resilience plans often fail in the same way: the list of priorities is long, the budget is short, and the money spreads across projects that do not change what happens in a real event. The fix is not a better list. It is a map of dependencies that shows where failures cascade.
Cascades are the normal failure mode
The August 14, 2003 blackout is still the clearest example. The U.S.-Canada task force found that it cut 61,800 MW of load across parts of the Midwest, Northeast and Ontario, in an area with an estimated 50 million people. It began with local problems in one utility's territory, and the damage came from how the system was connected. Everything downstream of the grid, from water pumping to communications, depended on how quickly power came back.
Communities are built the same way. A water system depends on pumps, pumps depend on power and controls, controls depend on communications, and every one of them depends on a few buildings and the people who staff them.
Frameworks that help draw the map
FEMA's Community Lifelines give emergency managers a shared vocabulary for what has to keep working: safety and security; food, hydration and shelter; health and medical; energy; communications; transportation; hazardous materials; and water systems. CISA's National Critical Functions take a national view, with 55 functions grouped as connect, distribute, manage and supply.
NIST's Community Resilience Planning Guide for Buildings and Infrastructure Systems (SP 1190) supplies the process. It has six steps: form a collaborative planning team, understand the situation, determine goals and objectives, develop the plan, prepare and approve it, and implement and maintain it. Its central idea is that buildings and infrastructure should be planned against the performance a community needs after an event, not against the minimum a code requires.
Put the building on the map
Dependency maps usually trace power, water and data, and stop at the property line. They rarely record what protects the node itself: whether the emergency operations center's walls, the water plant's control room or the radio site's equipment shelter would survive the event the plan assumes. An attacker or a storm uses the weakest physical path to a critical function, and a map that leaves the envelope out misses the path most likely to be used first.
A useful map therefore adds three questions at each node. What room holds the function? What protects that room, and against what? Who can get in?
From map to capital plan
Resilience becomes fundable when it is written as specific construction: this room, this assembly, this generator and fuel store, this access control, inspected on completion and maintained. That is a shorter list than most plans contain, and it is easier to defend in a budget hearing because each item traces back to a cascade the map shows.
- Rank nodes by what fails downstream, not by what is easiest to fund.
- Harden the room that holds the function before adding capability around it.
- Specify tested assemblies and inspect the built condition.
- Budget for staffing and maintenance, because a protected room nobody can reach during an event is not a working node.
Resilience is a small number of places that must keep working. Find them on the map, then protect the rooms and people inside them first. How to size those rooms for a long outage is covered in Can a Community Be Ready for a Black Sky Event?
Sources
- U.S.-Canada Power System Outage Task Force, Final Report on the August 14, 2003 Blackout
- FEMA, Community Lifelines
- CISA, National Critical Functions
- CISA, National Critical Functions Status Update (2021)
- NIST SP 1190, Community Resilience Planning Guide for Buildings and Infrastructure Systems, Vol. I
Cite this article: Authentic Intelligence Research, “How Does a Community Find the Node That Must Not Fail?” Authentic Intelligence, September 30, 2026, https://authenticint.com/articles/the-community-node-that-must-not-fail.html.