The Chariot
Protocol

Veterans Day.
Midnight.
Already armed.

The weapon at the heart of The Chariot Protocol is already inside. It has been for years — embedded in the firmware of VA hospital hardware across three thousand facilities, invisible to every diagnostic tool in existence. It was built by Nathan Thorne, a dead man. An Air Force veteran who loved what the VA was supposed to be. Who spent years watching the gap between that promise and the reality widen — and finally built something that couldn’t be ignored.

Nathan was precise about everything. The hardware he chose. The access he requested. The thing he left behind when he was done. None of it was an accident.

Mike Sanders is the senior VA IT official who has to stop it. Not because he’s a hero. Because he’s the only one who knew Nathan well enough to understand what Nathan was actually asking. He has forty years of institutional knowledge, a team of people who trust him, and a box Nathan left him that he hasn’t been able to bring himself to open. Veterans Day. The clock is running.

When the hospital’s systems begin to fail, Peggy Sanders doesn’t wait for the screens to come back. She pulls out her phone and calls the lab on a direct line nobody else has — the one she kept because she knew one day she’d need it. She works by ballpoint pen and an analog watch. She finds the person still present underneath the damage and addresses that person directly, not the chart.

Peggy is a VA geriatrics nurse. She is also Mike’s wife of thirty years. While Mike is downtown wrestling with the spirits in the machine, Peggy is in the Community Living Center doing the same work with her hands.

Pat King, the executive assistant who knows every name in the building and follows the human thread to its end, is the one who saves lives when no database can.

Nine million veterans. Three thousand facilities. One dead man’s final act — already inside, already waiting, already armed.