Chapter 9 - Seventy-Two Hours
The field test was supposed to be routine.
Three counties.
Simulated infrastructure loss.
Fire departments, emergency medical teams, National Guard support, and local emergency managers.
Open Door would create a resilient communications mesh after mock cellular and internet failures.
Now nobody knew whether the relay firmware could be trusted.
The test should have been canceled.
It was not that simple.
A real storm system was moving toward the region.
The same agencies participating in the exercise were preparing for severe flooding.
If conditions worsened, the test network could become operational support.
That had always been the point.
Build something useful enough that training became capability.
Now our compromised software might become a liability at exactly the wrong moment.
I returned to the lab under restricted supervisory authority.
Torres met me with a printout.
“We found the modified branch.”
“What does it do?”
“We’re still tracing.”
“Best guess.”
She hated guessing.
So did I.
“Handshake rejection.”
My stomach tightened.
“Conditional?”
“Yes.”
“Triggered how?”
“Unknown.”
A compromised relay could look healthy until a hidden condition told it to stop talking to the network.
Not a dramatic hack.
Worse.
A quiet failure at the worst time.
Captain Owen Blake, our security officer, entered.
“We should pull every Sable component.”
“How many?” I asked.
“Thirty-eight relays.”
Torres swore softly.
“We have fifty-two total.”
Removing thirty-eight would cripple the exercise.
Blake crossed his arms.
“Better than compromised hardware.”
He was right.
I hated him for it.
“We replace what we can,” I said.
“With what?” Torres asked.
“Older verified units.”
“They’re slower.”
“They’re clean.”
We worked through the night.
By sunrise, we had twenty-seven trusted relays.
Not enough for full coverage.
Enough for a reduced deployment.
Federal investigators wanted all compromised hardware isolated as evidence.
Local emergency officials wanted communications capability before the storm.
Everyone was right.
Leadership is often choosing which correct person gets disappointed.
General Ellison joined the coordination call.
“Captain Reed, recommendation?”
I looked at the map.
“Deploy trusted units only.”
“Coverage impact?”
“Forty percent reduction.”
“Operational risk?”
“Dead zones.”
“And if we deploy suspect units?”
“Unknown failure behavior.”
He waited.
I understood the question beneath the question.
Choose.
“Trusted units only,” I repeated.
Ellison nodded.
“Approved.”
Before the storm arrived, we ran one final reduced test.
Twenty-seven clean relays.
Three command vehicles.
A dozen agencies that all used different equipment and different terminology.
The first hour went badly.
A fire department could hear police but not the state operations center.
One Guard unit showed up on the map twelve miles from its actual location because a technician entered the wrong coordinate format.
A county dispatcher accidentally routed a training message into the live emergency channel.
Nobody died.
Nobody even came close.
But the mistakes reminded me why prototypes should be allowed to look ugly before disaster demands beauty.
I stood behind Torres while she corrected the map feed.
"We are not ready," she said.
"We never are."
"That is not comforting."
"It isn't supposed to be."
She looked at me.
"Then what is it?"
"A reminder that readiness is not a feeling."
We had checklists.
Backups.
Fallback frequencies.
People who knew how to improvise.
That was readiness.
Not confidence.
At noon, weather alerts changed.
Flood watches became warnings.
Warnings became evacuation advisories.
The exercise director walked into the operations room holding a phone.
"We may go live."
The phrase changed every posture in the room.
Training laughter stopped.
People closed simulation windows.
Real county maps replaced exercise overlays.
I watched my team transform.
Nobody needed a speech.
This was what they had trained for.
The storm arrived twelve hours early.
Rain turned violent by midafternoon.
Rivers rose faster than forecast.
The exercise was terminated.
Open Door shifted to real emergency support.
That sentence changed the entire room.
No more simulated casualties.
No inject cards.
No evaluators.
Real people were losing power.
Real rescue teams were moving into flooded roads.
Our reduced network lit up across the operations map.
Green nodes formed a broken chain.
Large gaps remained.
At 4:48 p.m., the first real call came from a volunteer fire department whose tower had lost commercial power.
Open Door routed them through a neighboring county.
At 4:56, an ambulance crew sent patient telemetry through a portable node after cellular service disappeared.
At 5:02, a sheriff's dispatcher asked whether the network could carry a photograph of a washed-out road.
It could.
Small wins.
Nothing dramatic.
Exactly what I wanted.
Then the emergency center started receiving water-rescue calls.
A sedan stalled in an underpass.
A family climbed onto a roof.
Two elderly residents refused evacuation because they did not believe the creek could rise another six feet.
The storm stopped being a communications exercise and became a thousand human arguments with physics.
I watched Torres coordinate bandwidth priorities.
She was good.
Better than she knew.
When two agencies demanded the same portable relay, she asked which one had an alternate path instead of which commander held more rank.
One did.
Decision made.
I felt something like pride.
Then guilt for feeling pride during a disaster.
Command creates strange emotional timing.
A young dispatcher at the back of the room started crying after losing contact with her father's neighborhood.
She wiped her face and kept working.
I walked over.
"Do you need five minutes?"
"No, ma'am."
"That wasn't a test."
She looked at me.
"I can keep working."
"Okay. But if you need five, take five before your body takes twenty for you."
She nodded.
Two hours later she found out her father was safe.
Nobody announced it.
She simply sat down harder than usual and covered her eyes for ten seconds.
Then returned to the console.
Those were the moments no public report would capture.
The network map showed green and red nodes.
It did not show the human beings trying to make each color mean somebody got home.
At 5:20 p.m., a county emergency manager called.
“We need coverage at Mill Creek.”
Torres zoomed the map.
“No trusted relay within range.”
“How many people?” I asked.
“Neighborhood of about four hundred.”
“Rescue teams?”
“Two moving in.”
“Conventional radio?”
“Intermittent.”
We had three quarantined Sable relays in the operations warehouse.
I stared at the map.
Blake saw where my mind went.
“No.”
“I didn’t say anything.”
“You looked at the warehouse.”
Torres said, “We could flash them with the last verified firmware.”
Blake shook his head.
“We do not know if the compromise is firmware only.”
“Hardware implant?”
“Possible.”
“Evidence?”
“No.”
“Then we have a real rescue with no communications based on a theoretical hardware risk.”
Blake looked at me.
“Captain.”
I hated that everyone waited for the rank.
I called Grant.
“Can we use quarantined relays if we wipe and isolate them?”
She did not like the question.
“For evidence purposes?”
“For people in floodwater.”
Silence.
Then she said, “Photograph, image, and document the units before modification.”
“Is that a yes?”
“It is me not telling an operational commander how to run a rescue.”
Close enough.
Before we selected the units, Blake forced us to run one last risk table.
Probability of hidden hardware compromise.
Unknown.
Consequence if compromised.
Potential network loss.
Consequence if not deployed.
Known communications gap during active rescue.
I hated how sterile the columns looked.
Nobody writes "a child may be waiting on a roof" in a risk matrix.
They write HIGH CONSEQUENCE.
Nobody writes "the lieutenant you trained may drive into floodwater without a working radio."
They write PERSONNEL EXPOSURE.
The language exists for a reason.
It keeps emotion from swallowing analysis.
But I had learned the opposite lesson too.
If you remove every human detail, numbers become easier to sacrifice.
So I asked the county manager one more question.
"Who is moving into Mill Creek?"
He read names and units.
Fire Rescue Two.
Guard Convoy One.
Sheriff High-Water Team.
Torres.
Real people.
Then I looked at the technical risk again.
"Document that we are using the relays only after imaging, verified firmware replacement, and management isolation."
Blake nodded.
"And if they fail?"
"We fall back to analog and pull teams if communications become unsafe."
That answer satisfied nobody.
It was still the best one we had.
We selected two units.
Disconnected every external management channel.
Flashed trusted firmware from read-only media.
Removed remote-update capability.
Then Torres rode with a National Guard team to deploy them.
I grabbed my jacket.
She looked at me.
“You’re not coming.”
“I am.”
“You just got your career back.”
“Not relevant.”
“It is when someone needs to stay here and command.”
She was right.
I hated her for it.
“Fine.”
Torres smiled.
“Growth.”
“Get out.”
The convoy left.
For twenty-three minutes, nothing happened.
Then the first relay came online.
Green.
The second followed.
Coverage expanded across Mill Creek.
A rescue team checked in.
“Command, Mill Creek One. We have network.”
The room exhaled.
Then both new nodes went red.
At exactly the same second.
Torres’s voice cut out mid-sentence.
The map showed the rescue convoy moving deeper into the flooded area.
Then their location froze.
“Call them,” I said.
Radio operator tried.
Nothing.
“Analog?”
“Static.”
“Cell?”
“No service.”
Blake stared at the dead nodes.
“That was triggered.”
“How do you know?”
“Simultaneous failure.”
Torres had been right about the firmware being clean.
Something else had killed them.
Then one of our engineers shouted.
“I have outbound traffic.”
“From where?”
“The relay management controllers.”
“Destination?”
He typed.
A server address appeared.
Grant recognized it before I did.
“Meridian.”
May you like
Someone inside Meridian’s network had just reached into two relays we thought we had isolated.
And somewhere beyond the dead signal, Torres and two rescue teams were driving into rising floodwater without communications.
