Sovereignty at the Edge: Why Public Health Systems Mirror Defense in Resilience Needs
The modern world expects systems to be both centralized and resilient. It is a contradiction that defines the failures of both health IT and defense infrastructure: the more systems rely on centralized control, the more they collapse when that control is severed. Public health and national defense share a paradoxical truth, they require architectures that function during infrastructure failures, yet they are often designed for stability in times of peace. The result is a system that falters precisely when it is needed most.
The Architecture Was Built for the Wrong Threat Model
Government health systems are constructed under the assumption that connectivity and central oversight are constants. Data residency laws, compliance mandates, and emergency protocols all revolve around a hub-and-spoke model where information flows to and from a central authority. This works until it doesn’t. During a pandemic, a cyberattack, or a natural disaster, the assumption of constant connectivity shatters. Systems designed to function only when integrated with a central cloud or data repository become liabilities.
The same flaw exists in defense infrastructure. For decades, military systems prioritized interoperability with centralized command structures, assuming that satellite links, 5G, or fiber would always be available. When adversaries target communications or when terrain disrupts connectivity, these systems degrade rapidly. The lesson is the same in both domains: sovereignty is not a feature, it is the foundation.
In public health, this means systems must operate independently when networks fail. A regional health authority cannot wait for a cloud-based analytics engine to process an outbreak. A hospital’s emergency operations center must function without relying on external data feeds. The requirement is not just for redundancy but for autonomy.
Lessons from Two Decades of Government Systems
Building systems for government health agencies over 20 years reveals a recurring truth: resilience is a product of design, not an afterthought. Silicon Valley’s approach to health IT prioritizes scalability, user experience, and cost-efficiency. These goals are valid but misaligned with the needs of crisis response. A platform that works well in a hospital with stable internet is useless in a field hospital during a power outage.
The industry has built a generation of health IT that fails during the moments that matter most. Systems optimized for peak performance under ideal conditions ignore the reality of edge environments. They assume that data can always be transmitted, that models can always be retrained in the cloud, and that compliance can be enforced through centralized audits. These assumptions ignore the physics of infrastructure failure.
Resilient systems, by contrast, prioritize determinism. They process data locally, store critical operations in memory, and restore state in seconds, not minutes or hours. This is not just about hardware; it is about redefining what “availability” means. In a crisis, availability means functioning without external dependencies.
The Questions Worth Sitting With
1. How do you balance regulatory compliance with the need for local autonomy? Compliance frameworks often demand centralized oversight, but resilience requires decentralization.
2. Can a system designed for 99.9% uptime in a data center survive 99.99% downtime in the field? The metrics of reliability must shift from “always on” to “always functional.”
3. How do legacy systems integrate with modern edge architectures? Public health agencies inherit decades-old infrastructure that cannot be replaced overnight.
4. What does “data sovereignty” mean when the data itself is the emergency? In a public health crisis, information is both a resource and a liability. Systems must protect it without slowing its flow.
The Edge Is Not a Periphery: It Is the Core
Public health and defense share a fundamental requirement: systems must function when the world breaks. The answer lies not in better connectivity but in better design. Sovereign infrastructure is not about rejecting the cloud, it is about ensuring that operations continue when the cloud disappears.
Resilience is the principle that unites these domains. It demands architectures that prioritize memory over storage, computation over transmission, and autonomy over control. The industry has spent decades optimizing for the wrong threats. The next generation of systems must be built for the right ones.
Sources:
JENGA: Exploiting Counter-Based RowHammer Countermeasures to Break Real-Time Predictability