once

Chapter 2 - EIGHTY-SEVEN SECONDS

I froze the exercise.

Mercer objected immediately.

“You don't have authority to suspend my certification event.”

That was when I finally showed him the badge.

Not dramatically.

I unclipped it and handed it to him.

Joint Command Readiness Assessment Team.

Lead Operational Resilience Evaluator.

My rank was major.

Same pay grade Mercer liked reminding people he had survived longer than.

Different authority for the day.

He read it.

Looked at me.

Then handed it back.

“So this was a setup.”

“No.”

“You came in here dressed like that so I'd show you how I treat people.”

“I came like this because I was evaluating command behavior without ceremony.”

“Same thing.”

“Not quite.”

His jaw tightened.

I had already seen enough of his behavior to make that argument later.

Right now the system mattered more.

Dana copied the local configuration to an isolated terminal.

The eighty-seven-second mismatch came from two separate layers.

The live radio position service was current.

The command-room map was not.

At 14:09, the automatic map update failed.

Instead of dropping the tactical overlay and forcing operators to rebuild from central data, the system automatically fell back to a locally cached copy.

That copy included Black Route.

The software should have stamped the entire map:

STALE.

It had not.

Why?

Because the compatibility package bypassed the current warning layer.

Compatibility package version:

22-K.

My waiver.

I remembered signing it.

October 2022.

A new command software update had been rolling across six installations.

Two older tactical-radio families could not reliably interface with it.

If we forced the transition on schedule, three units would lose common operating picture capability for weeks.

So my team created a temporary bridge.

Local map cache.

Legacy radios.

Manual position confirmation if central sync failed.

Ninety days.

Hard expiration was supposed to come later.

It never did.

I looked at Dana.

“Why is 22-K installed here?”

She glanced at Mercer.

I noticed.

“So?”

She answered.

“Current package failed compatibility testing with our mobile relay kits.”

“When?”

“Last year.”

“What did you do?”

“Opened a support ticket.”

“And?”

“Vendor patch was projected six months.”

“So you installed an expired bridge.”

“Yes.”

“Who approved?”

Dana looked at Mercer again.

He answered.

“I did.”

“Did you ask Training Command?”

“No.”

“Why?”

“Because I had an exercise in eleven days.”

There.

Not espionage.

Not sabotage.

Schedule.

I understood it too well.

“Did you know the Black Route layer was inside it?”

“No.”

“Did you know the package suppressed stale-map warnings?”

“No.”

Dana looked uncomfortable.

I turned.

“Did you?”

She hesitated.

“Partly.”

Mercer turned toward her.

“What does partly mean?”

“The old package handles sync-loss differently.”

“That is not what I asked.”

Dana swallowed.

“I knew the warning behavior was older.”

“Did you tell me?”

“Yes.”

There.

Mercer went still.

“When?”

“February.”

His face changed.

Not lying.

Remembering.

She had briefed him after a smaller communications drift during Exercise Sand Ledger.

Dana had recommended removing the package.

Mercer asked what replacement would do.

She told him the current system would blank the tactical board whenever sync confidence dropped below threshold.

For how long?

Unknown.

Could be thirty seconds.

Could be eight minutes.

Mercer said:

“We're not going blind because software gets nervous.”

There.

His exact phrase, according to Dana.

He kept the bridge.

“What happened in Sand Ledger?”

I asked.

Dana pulled the report.

No incident.

No injury.

No lost unit.

A seventy-two-second map divergence.

Corrected locally.

Final status:

Communications maintenance pause.

Not exercise failure.

I looked at Mercer.

“Who classified it maintenance?”

“Me.”

“Why?”

“Because nothing failed operationally.”

“The command picture was wrong for seventy-two seconds.”

“And we fixed it.”

“During certification?”

“Yes.”

“Before evaluator scoring resumed?”

He stared.

There.

“Was the evaluator told?”

“They saw the pause.”

“That isn't what I asked.”

“No.”

The room behind us had become very quiet.

Not because they were eavesdropping.

Because they worked there.

This was their system too.

I asked Dana:

“How many sync-loss events have you had since installing 22-K?”

She started searching.

Seven.

Three under one minute.

Four between one and three minutes.

Every one classified as maintenance or systems alignment.

Zero counted as command-and-control degradation during readiness scoring.

Mercer leaned toward the terminal.

“We did not hide failures.”

I looked at him.

“You decided they weren't failures.”

“Because operators maintained the mission.”

“On a board that sometimes wasn't current.”

“It was current enough.”

There.

Current enough.

The most dangerous phrase in any command room is rarely a lie.

Usually it's a threshold nobody bothered to define.

Then a lieutenant at the back spoke.

Lieutenant Jason Park.

The same one who had laughed when Mercer called me sweetheart.

He was not laughing now.

“Ma’am.”

I turned.

“Say it.”

He looked at Mercer.

Then back at me.

“Last month it was worse than three minutes.”

Dana frowned.

“What are you talking about?”

Park stood.

“Night Shift Eleven.”

Mercer's face changed.

“Lieutenant.”

Park stopped.

There.

Same hesitation I saw earlier when I asked the operator a simple question.

I said:

“Continue.”

Park swallowed.

“The board froze during a simulated casualty evacuation.”

“How long?”

“Six minutes.”

Dana stared.

“That isn't in the fault log.”

“No.”

“Why?”

Park looked at Mercer.

Mercer did not answer for him.

Good.

Park did.

“We restarted the command node.”

“During the event?”

“Yes.”

“Then?”

“Ran the segment again.”

I felt something tighten behind my ribs.

“How was it reported?”

Park looked at the floor.

“Successful.”

There.

The first run had disappeared.

Not from a conspiracy.

From a reset.

Mercer said:

“The exercise controller authorized the restart.”

“Who requested it?”

“I did.”

“Why?”

“Because a software lockup is not a test of command judgment.”

Maybe.

Then Park said quietly:

“The first run included a wrong medical route.”

Mercer turned.

“What?”

Park stared at him.

“The casualty vehicle was sent toward Gate Six before the restart.”

Dana looked at the tactical board.

Gate Six had been closed for seven months.

The room went silent.

Again.

I asked:

“Who caught it?”

Park answered.

“The vehicle commander.”

Not this room.

The field.

The same kind of people Mercer had just said I would get killed before lunch.

He looked at me.

I looked back at him.

Then Dana opened the Night Shift Eleven archive.

The first run still existed in raw telemetry.

Someone had renamed it.

SYSTEM TEST — NOT FOR SCORE.

Timestamp of the rename:

02:14 a.m.

User:

B. MERCER.

He had not deleted anything.

May you like

He had decided what counted.

And every metric above him had agreed because nobody knew enough to ask.

Related Stories

Other posts