Captain Shaw didn’t touch the keyboard again.
She simply stared at the evaluator’s name.
MAJOR DANIEL MERCER.
Then she looked at Major Kane.
“When was the last time Mercer worked here?”
Kane answered too quickly.
“Six years ago.”
Shaw’s eyes narrowed.
“I didn’t ask when he left.”
Silence.
I looked between them.
“What happened to him?”
Shaw answered.
“Major Mercer disappeared during a training transfer six years ago.”
Kane immediately added:
“He was presumed dead.”
Shaw corrected him.
“Missing. Not dead.”
That distinction mattered.
Mercer’s personnel status had never been formally changed to deceased.
But his evaluator credentials should still have been disabled the moment he disappeared.
Instead, someone had used them yesterday.
On my score.
Shaw preserved both evaluation records before anyone could alter them.
My candidate number was C-417.
At 14:32, two evaluations had entered the system simultaneously.
The first gave me:
91.6
The second:
96.8
Major Kane had destroyed the paper scorecard and accused me of manipulating the system to increase my result.
But there was a problem.
Before the official results were released, Kane had shouted:
“You really thought nobody would notice you changed a ninety-one-six into a ninety-six-eight?”
I had never seen 96.8.
Neither had the other candidates.
That was Kane’s first contradiction.
Now Shaw asked:
“How did you know both scores?”
Kane folded his arms.
“I received an anomaly alert.”
“Show me.”
He couldn’t.
There was no alert.
Then Shaw scanned the sealed range-control card I’d found clipped behind my candidate packet.
The system identified it as:
C-417 — CONTROL COPY B
Kane had called it “the duplicate” before I told him another copy existed.
That was his second contradiction.
Shaw retrieved Control Copy A.
Same candidate number.
Same exercise.
Different evaluator codes.
Copy A:
EVALUATOR — KANE, M.
Copy B:
EVALUATOR — MERCER, D.
I stared at Kane.
“You evaluated me twice?”
“No.”
“Then who did?”
“I told you. Computer error.”
Shaw shook her head.
“Computers don’t independently sign evaluation cards with missing officers’ credentials.”
She requested the authentication logs.
Mercer’s account had been accessed at 13:48 the previous afternoon.
The login came from Range Control Terminal Four.
Kane immediately said:
“That terminal hasn’t worked in years.”
Shaw slowly turned toward him.
“Interesting.”
Kane frowned.
“What?”
“I didn’t tell you which terminal.”
For the third time, he’d known something before anyone told him.
Range Control Four was inspected.
It wasn’t dead.
It had simply been removed from the current network map.
Physically, the terminal was still installed inside an old observation room.
And someone had powered it on yesterday.
The local access log showed three entries.
13:41.
13:48.
14:29.
At 14:32, Mercer’s evaluation appeared under my candidate number.
But Shaw refused to jump from that fact to a conclusion.
A credential is not a person.
Daniel Mercer’s login being used did not mean Daniel Mercer had returned.
Someone could possess his credentials.
An old account could have been restored accidentally.
A system migration could have duplicated permissions.
So she ordered a full review.
The first answer came from the IT section.
Mercer’s account had been disabled six years earlier.
But four months ago, the training facility migrated its legacy evaluation database.
During that migration, dozens of historical evaluator profiles were temporarily restored so old scorecards could be converted.
Most were disabled again afterward.
Mercer’s wasn’t.
That explained how his credentials could technically function.
It did not explain who used them.
Then Shaw found another detail.
Mercer’s old evaluator code had a physical authentication token.
That token had supposedly disappeared with him.
Except an inventory entry from six years earlier said:
TOKEN RECOVERED — RANGE CONTROL STORAGE.
Signed by:
MAJOR KANE.
Everyone looked at him.
Kane finally stopped denying that he knew about Mercer’s credentials.
“Yes,” he said. “I recovered the token.”
“Where is it?”
“Destroyed.”
“When?”
“Six years ago.”
Shaw requested the destruction certificate.
There wasn’t one.
Then Sergeant Ellis, the range technician, spoke from the doorway.
“Ma’am?”
Shaw turned.
Ellis held a small evidence bag.
Inside was an old authentication token.
“I found this behind the access panel at Terminal Four.”
The serial matched Daniel Mercer.
Kane sat down.
I thought that was the answer.
It wasn’t.
The token explained how someone could authenticate as Mercer.
It still didn’t tell us who had done it.
Security footage outside the old observation room showed three people entering the corridor that afternoon.
A technician.
Captain Shaw.
And Major Kane.
Kane entered at 13:39.
He left at 13:52.
Mercer’s credential was used at 13:48.
That looked devastating.
But Shaw didn’t call it proof.
The camera couldn’t see inside the room.
And the terminal allowed scheduled synchronization.
Kane admitted entering.
He said he’d been checking old range equipment before an inspection.
Then Shaw asked:
“Did you use Mercer’s token?”
“No.”
“Did you know it was there?”
“No.”
That answer didn’t survive long.
His fingerprints were on the token casing.
Kane said that was because he’d handled it six years earlier.
Possible.
So the review continued.
Then they examined the two evaluations themselves.
The 91.6 score wasn’t simply lower.
Several individual marks had been entered incorrectly.
My navigation segment was recorded as 82.
The range sensor data showed 94.
My response-time score was recorded as 88.
The automated timing system showed 96.
My safety evaluation had been reduced by six points for a violation that wasn’t present in the observer log.
When the raw results were recalculated independently, my score was:
96.8.
The duplicate evaluation under Mercer’s credentials was mathematically correct.
That made the situation stranger.
Someone hadn’t used a missing officer’s identity to inflate my score.
Someone had used it to correct my score.
Shaw looked at Kane.
“Why was the original wrong?”
Kane answered:
“Evaluator judgment.”
“Sensor measurements aren’t judgment.”
No response.
Then Shaw compared my record with other candidates.
Seven scorecards had discrepancies.
Five candidates had been scored lower than their raw performance supported.
Two had been scored higher.
Every disputed score had passed through Kane’s evaluation group.
That triggered a broader review.
But the pattern wasn’t enough to prove deliberate favoritism.
Some errors came from an outdated scoring formula.
Others came from manual transcription.
Only three couldn’t immediately be explained.
Mine was one of them.
Then Ellis discovered something inside Terminal Four.
A scheduled correction package.
Created six years earlier.
Author:
D. MERCER.
It contained a validation routine designed to compare manually entered scores against range sensor data.
The facility had stopped using it after Mercer disappeared.
During the recent database migration, the old routine had become active again.
Yesterday, it detected the mismatch in my score.
It automatically generated a corrected evaluation.
That explained why Mercer’s name appeared.
The system wasn’t being operated by a missing man.
It was executing an old process he had created.
But what about the physical token?
The migration technician had discovered it weeks earlier and plugged it into Terminal Four while testing legacy authentication.
He forgot to remove it.
And because Mercer’s restored profile remained active, the correction routine authenticated under his identity.
No ghost officer.
No secret return.
No evidence Daniel Mercer had logged in yesterday.
Just an old credential, a forgotten token and a six-year-old correction process waking up inside a modernized system.
Kane visibly relaxed.
Too soon.
Because that explained Mercer’s evaluation.
It did not explain Kane.
He still knew my final corrected score before publication.
He still knew about the duplicate card.
He still knew which terminal had generated it.
Shaw asked him one final time:
“How?”
Kane admitted he’d seen the duplicate evaluation shortly after it appeared.
The system sent it to the command review queue.
Instead of reporting the legacy-account problem, he opened both scorecards.
He saw that the second score was higher.
And because I’d previously challenged one of his instructors over an incorrect safety deduction, he assumed I’d somehow manipulated the evaluation.
He never checked the raw sensor data.
He never checked how Mercer’s account had been activated.
He simply decided I had cheated.
Then he destroyed my paper scorecard during the confrontation because, in his words, he believed it had been “compromised.”
Shaw stared at him.
“You destroyed the record before investigating the discrepancy.”
Kane said nothing.
That became a separate issue.
The technical review eventually confirmed my correct score as 96.8.
Every candidate’s result was recalculated using the same validated data.
Some scores rose.
Some fell.
Several stayed unchanged.
Nobody was allowed to keep an advantage or disadvantage created by the broken process.
Mercer’s account was disabled again.
His authentication token was preserved.
Terminal Four was removed from operational access.
And the six-year-old validation routine was rebuilt under a current system account so corrections would no longer appear to come from a missing officer.
But Daniel Mercer himself remained a mystery.
His personnel file still said:
MISSING — STATUS UNRESOLVED.
Before the investigation closed, Shaw found one final document attached to Mercer’s old validation program.
It was a note he’d written for whoever maintained the system after him.
A SCORE IS NOT THE PERSON WHO ENTERED IT.
CHECK THE SOURCE DATA.
I read it twice.
Shaw smiled faintly.
“Apparently Mercer expected people to argue with his program.”
I asked:
“Do you think he’s still alive?”
Her expression became serious again.
“We don’t have evidence for that.”
And she was right.
A credential wasn’t a person.
A signature wasn’t proof someone had returned.
A six-year-old program could keep doing exactly what its creator told it to do long after the creator disappeared.
My score had started the mystery.
But by the end, 96.8 was almost the least important number in the room.
Major Kane hadn’t discovered me cheating.
Daniel Mercer hadn’t secretly logged into the system.
The duplicate evaluation had exposed something simpler:
an old process had caught a current mistake.
And my commander had been so certain I was guilty that he destroyed the very record that could have shown him he was wrong.
