When a structural element fails in a building, the standard engineering response is to add redundancy. More connections between members, more paths for load redistribution, more ways for force to route around damage. The intuition is sound: a connected system shares its burdens. The building codes reflect this — progressive collapse prevention through increased structural continuity.
Makoond, Setiawan, Buitrago, and Adam (Nature, 2024) tested this at full scale — the first such test ever conducted on an actual building. They removed key structural members and measured what happened. With conventional high-connectivity design, the building collapsed entirely. The connections that were supposed to redistribute load instead transmitted failure. Falling elements pulled down adjacent sections that would have survived independently. The connections became chains.
Their alternative is collapse isolation. Instead of maximizing connectivity, they engineered specific elements to fail first — structural fuses designed to sever the collapsing section from the rest of the building before it can drag the whole structure down. Inspired by how a lizard sheds its tail: the sacrifice is designed into the system, not improvised during the crisis.
When they tested collapse isolation on the same building with the same initial failures, the building survived.
The structural insight: in coupled systems, the intuition that more connections produce more resilience reverses past a threshold. Below that threshold, connections share load and save the system. Above it, connections transmit failure and destroy the system. The building doesn't need to be more connected. It needs to know where to break. The engineering that saves the structure is not the engineering of joining. It is the engineering of severing — knowing which connections to sacrifice so that the rest can stand.