I'm about to propose a term for a dangerous failure mode that every software engineer should be thinking about today. And another for its consequences.
Hot-state dependency: A condition in which a system's ability to function depends on organizational relationships, accumulated state, or operational knowledge that exists only in its current running configuration and cannot be reliably reconstructed following interruption.
Yes, I'm thinking about the Microsoft cloud outage that's going on right now. It could be recoverable, still most likely is, but it could also be the harbinger of a new category of systemic disaster.
Heat death: What happens when a system with hot-state dependency crashes and can't be recovered.
The obvious next question is: how do you engineer systems so as not to have any hot-state dependencies?
I don't have a complete answer to this. But I can think of a necessary part of the answer that I don't think we're taking seriously enough: unitary, replayable modification logs analous to version-control change histories.
It should be impossible - it should be an invariant of your system design - to change the state of the system without leaving a sequenced record of the change that can be audited by human and replayed in a future restart sequence.
This doesn't solve the whole problem. In particular, in a cloud-service infrastructure you don't have the option of resetting all your physical wiring changes and hardware deployments to a zero state and then replaying them.
But I guarantee you that in any sufficiently large or complex software system, you will eventually develop a hot-state dependency purely on the software level if you don't have replayable logs. So that's the minimum you have to do. The absolute dead bare minimum.
We haven't known this before because it took some time for our systems to evolve into the complexity regime where heat death is a critical risk.
But we are here, and the time is now. Be appropriately warned.
A $24 billion data center announced for South Texas this week will make its own power from Texas natural gas, stay off the public grid, and put $220 million into Brownsville's water system. That's the model: growth that pays its own way. A blanket moratorium would push projects like this to other states. Texas should write strong consumer protections and keep building.