The Chariot Protocol Excerpt: Mike Sanders

The following is an excerpt from The Chariot Protocol by William C. James.

A SHADOW AT DAWN—5:30 AM

The day started, as it always did, with the memory. In the gray stillness of his northern Virginia home, Mike Sanders’s eyes opened five minutes before the alarm, his thoughts already drifting to a cold headstone in Alexandria National Cemetery.

Why didn’t you call me, Nathan?

He’d been swallowing that question for years.

His only ritual against the heavier memories was a compulsive glance at the VA’s network health on his tablet—order imposed before the chaos could settle in. He found the status lights green and moved through the dark house in the wordless sequence that had become his armor: shower, coffee, keys. As the garage door rolled open to the cold air, he sealed the morning’s grief into his breast pocket and was, at least outwardly, ready to face the day.

On the day before a federal holiday, the traffic was light enough for Mike to loop around the southern edge of Arlington National Cemetery. It was a little longer, but he liked the view. As he followed a string of taillights headed toward the Pentagon, the soaring spires of the Air Force Memorial pierced the dark gray sky. The sight never got old. It was a daily reminder of the promise he was still trying to keep. He crossed into the city as dawn bled over the horizon, the monuments dark silhouettes caught between night and morning.

By the time he reached VA Central Office (VACO), the morning flow of personnel was already filing into the V-shaped behemoth of limestone. Inside the echoing foyer, he walked past the guards at the stairs, his ID badge held plainly in view. One of the guards, a man named Charles whose face was as familiar as the morning commute, glanced at his badge and gave a small nod. Mike returned it and took the shallow marble stairs two at a time, his footsteps joining the morning current of the building as he headed for the elevators and the seventh floor.

THE MORNING RITUAL—WASHINGTON, DC—7:00 AM

The smell of fresh black coffee cut through the air as Mike reached his office—a sure sign his executive assistant, Pat King, had already taken command of the day. Mike credited her unshakable demeanor to her time at the Disney Institute. She called it “customer relationship training.” He called it the reason she was the only person in the building who could handle a furious Deputy Secretary without breaking a sweat.

He sat down, clicked open the first of the overnight what-broke-last-night reports, and scanned the cascade of dry, automated alerts. Minor latency spikes in Phoenix. A 2.1 percent packet loss in Miami. All explainable, all background noise in a sprawling infrastructure that protected nine million veterans across 3,000 locations. Something was always breaking somewhere.

Then a new flag caught his eye:

MODULE ERROR - NCR - DC VAMC - ORTHO SCHED.

A software error in the appointment scheduling routine for the Orthopedics clinic at the DC VA Medical Center. His stomach tightened. Peggy had mentioned it at dinner—their neighbor, Phill Dawson, had his orthopedic consult there today. “Six weeks he’s been waiting for this one, Mike,” she’d said. He could hear her voice, the gentle insistence in it. A veteran who had waited six weeks, and now the system that was supposed to keep that promise was throwing errors on the morning of his appointment.

He pulled up the error detail. Attached to the flag was a device ID he didn’t recognize:

SYS-ASIC-4417

He scrolled the overnight reports again. The same board identifier appeared three more times: once in Pittsburgh, once in Phoenix, and once in a biomedical device registry he didn’t recognize. He ran a quick lookup for the alphanumeric string in the hardware asset catalog. Nothing. A device ID that didn’t exist in VA’s registry wasn’t unusual. Inventory policy was one thing; inventory reality was another. He noted the string in his morning log, flagged it for Ann Deering’s queue, and moved on.

A text waited on his VA-issued phone, sent at 5:30 a.m., from Dee, his best network admin in the field:

Dee: The machine is humming the wrong tune in Philly.

Mike frowned and looked back at the official, green-lit dashboard for the Philadelphia data center. All systems nominal. But Dee had an ear for the network’s rhythms that no monitoring software could replicate. A wrong tune. A scheduling error in DC. A phantom hum in Philadelphia. He opened a private log file on his desktop. The first entry.

THE FIRST TREMORS—10:00 AM

For the next two hours, the building settled into its Monday rhythm, and Mike tried to do the same. He turned from the alerts to the routine: maintenance schedules, employee performance appraisals, data to pull for the CIO’s congressional testimony that afternoon.

From his window, he could see the weathered statue of General Kościuszko standing perpetual watch on the corner of Lafayette Park. A foreign volunteer. A brilliant military engineer who fought in the Revolutionary War, still standing guard outside a building full of people bound by the same oath. Beyond the park sat the White House, where the poetry was written. His office was where that poetry met the hard prose of federal budgets and aging infrastructure, where promises were kept or broken, one line of code at a time.

Mike turned from the view and faced his unremarkable government-issue desk, its steel frame scarred by the labor of a hundred other civil servants. It was cluttered in an organized way only he understood. In one corner sat a stack of worn, cardboard-bound notebooks, their pages filled with his cramped, block-lettered handwriting. Next to his keyboard, an old Air Force challenge coin rested on a small felt square. He’d carried it for thirty years, but here at VA, the tradition had evolved. A coin was a symbol of shared success, a token given by a team leader to celebrate the launch of a hard-won project. Its surface was worn down by years of absent-minded rubbing through tense conference calls. His thumb found it now, a reflex.

From the wall vent, the building’s ancient heating system let out its rhythmic hiss-clank-thump, a metallic pulse that recalled his father and the plants back home. It was a lesson learned young, walking the catwalks of the Houston refineries, his hand swallowed in his father’s calloused grip. “See that, Mike?” he’d said, his voice barely audible above the roar of the machinery. “That’s a heart. Pressure comes in, pressure goes out. If one valve sticks, the whole body gets sick. You gotta listen to it. It’ll tell you when it’s hurting long before it breaks.”

The VA’s network was no different, a body vast and sprawling, its history written in forgotten code and the hurried repairs of men and women long since retired. He sometimes thought of the building’s own history, originally built to house the Bureau of War Risk Insurance. A century later, he was still managing the risks of war, but the scars were no longer on paper. They were in the code.

And today, something in it was hurting. He couldn’t name it yet. The dashboard was green. But Dee heard a wrong tune, and Mike had learned long ago to trust the people who listened to the machine as much as the people who built it.

At 10:00 a.m., the green broke. An alert flickered in the bottom corner of his diagnostic screen:

ELEVATOR 3 - OFFLINE

The fault came from the DC VA Medical Center, three miles away. Buildings, Mike thought. Everyone assumed they just worked. Nobody looked inside them until they stopped. He logged the incident and sent a ticket to VA facilities.

Ten minutes later, the next tremor arrived. Error flags from the patient scheduling module at the VA Medical Center in Martinsburg—the same software that had thrown the DC Ortho error that morning.

Mike leaned back. DC. Martinsburg. Philadelphia. Three locations, three different systems, one morning.

He stabbed the intercom button. “Pat, please spin up a Teams videoconference—just the project managers for scheduling and pharmacy software and the DC facilities team, and pull in someone from Biomed. Let’s look at the whole board.”

His office filled with disembodied voices.

“Facilities here,” a gruff voice from the DC Medical Center cut in first. “Mike, I don’t know why we were pulled onto this Teams call. The elevator drop is a localized fault. We’ve dispatched a building engineer to reset the controller. This isn’t an IT issue.”

“Keith here.” His voice was tight and stressed. “The pharmacy software feed is lagging by ninety seconds. A pharmacist just screamed at my field tech that ninety seconds is an eternity when you have fifty scripts to fill. We’re chasing it.”

Then a third voice chimed in, crisp and audibly impatient. “Biomed here. Mike, respectfully, why were we invited to this? We are green across the board.”

The facilities rep cut back in. “Quick update. The engineer reset the controller. Elevators are back up.” A pause, then, “Check that. Down again. We’ll keep at it.”

“I want us all looking at the enterprise,” Mike said. “We’re seeing distributed anomalies across many facilities and systems. I want to know if the medical devices are seeing any secondary ripples.”

“They aren’t,” the director said. “Frankly, we don’t have time to sit on a call while you guys argue over routers and elevator cables. Our devices are solid. Let us know if you see something break.” Biomed’s tile went dark.

Mike took his hand off his mouse, listening to the remaining overlapping chatter. A mechanical fault. An IT delay. Biomed dismissing it entirely. Three separate fiefdoms, defending their own turf, isolated. Blind to the fact that they were all describing the ghost moving through the seams that divided them.

Mike sighed, picked up his pen, and wrote Convergence in his notebook. The calls kept coming. By 10:45, Mike had filled three pages with incident flags. The morning had become midday.

Then Pat appeared in his doorway. “Cass Reynolds wants you to join a Teams video call. She’s, uh ... not in a good mood.”

“We’re seeing distributed, asynchronous failures,” Mike said. “It almost feels intelligent. And it’s escalating.”

A pause. “Intelligent? Don’t give me poetry, Mike. Give me a plan. Can you contain it?”

“Not yet. We can’t contain what we can’t find.”

“Then find it.” The line went dead. Outside his window, the sky had gone flat and white. The hard, colorless light of a November noon.

…

To read the rest of The Chariot Protocol, you can find it on Amazon.

William C. James spent fifty years inside federal IT, from GS-1 file clerk to Senior Executive at the Department of Veterans Affairs. He knew the building. He knew the people holding it together. And he knew what was at stake if they ever stopped. William served in key roles at the Defense Mapping Agency, US Transportation Command, the Pentagon, and the VA. His memoir, The Accidental Executive, shines a light on true heroes: civil servants, nurses, and patient advocates. When not working on his next book, he consults for companies in the VA IT market. He lives in Vienna, Virginia.