Does a Spoke taking over as Hub require the command line? No. The same capability is offered at three layers of access: engineers get fine-grained low-level control; a nurse just presses one button at the right moment. Package a sysadmin's power into an interface anyone can operate.
Traditional Hub-Spoke carries one fatal assumption: the Hub is always online. But in a disaster zone, when the Hub goes down, patients cannot wait. xGrid designs for disconnection as the normal state — every node is a complete system, and any one of them can take over.
How long until we run out of O-negative blood? Who authorized the amputation? xGrid's burn rate engine calculates hours-to-depletion in real time, while the multi-signature approval system ensures irreversible decisions are never made alone.
Clinical handoffs have been oral for decades. ISBAR gives them structure. But the real value is not the structure itself — it is what becomes possible when handoff data is searchable, verifiable, and replayable.
Most medical systems treat offline mode as degradation. xGrid treats it as the default. When your deployment site has no cell towers, no routers, and no IT staff, every design decision starts from zero connectivity.
Safety-I builds walls against failure. Safety-II asks how people succeed despite failure. In disaster medicine, the difference determines whether a forced evacuation loses patients or saves them.
Triage is not about sorting patients into color categories. It is about deciding who gets what resources, when, and at whose expense. In xGrid, the color you assign determines the bed, the drugs, and the surgery slot.
What happens when the development team disappears? We formalized the software industry's 'bus factor' problem into five rigorous acceptance criteria — and built a medical system that passes all of them.
