Chapter 12 - THE PEOPLE ABOVE THE CLOCK

Vale was angry about the maintenance report.
At himself, maybe.
He had worked in that standardization office two years earlier.
Not on systems.
On evaluation policy.
Still close enough to recognize names.
The clock fault first appeared at another training center.
Software vendor recommended a patch.
The Air Force delayed deployment because it could disrupt older recorder hardware.
Reasonable technical concern.
The interim guidance said evaluators should use independent timing when local clocks desynchronized.
Also reasonable.
Our unit did not have the independent timing tool configured correctly.
Less reasonable.
Mason's group improvised.
Then improvised again.
Vale said:
“Colonel Reed had a proper route. Send the event up.”
“He thought it would take three weeks.”
“It might have.”
“Would it?”
Vale looked at the backlog report.
“Yes.”
There.
Mason had not invented that pressure either.
The higher system made correct process slow.
The local commander made incorrect process fast.
Everyone then acted surprised when people chose fast.
I asked:
“Did you know reconstruction examples were being used in evaluator training?”
“No.”
“Who made the example Ortiz had?”
Vale did not know.
Metadata:
Created four years earlier.
Author field:
STD-EVAL
Shared office account.
Of course.
The old orientation deck had been revised eight times.
Nobody remembered who added it.
Then a retired evaluator came forward.
Colonel Susan Park.
She recognized the example.
“I built the first version.”
Vale put her on speaker.
“Did you intend people to use replay clips as official evidence?”
“No.”
“Then why was the example unlabeled?”
Park sighed.
“Because the slide was about layout, not evidentiary annotation.”
One screenshot pulled from a training draft.
Someone later reused the screenshot to teach media reconstruction.
Context disappeared.
Then someone else turned that training habit into practice.
No conspiracy.
Just organizational sediment.
Vale hated that answer.
I was starting to recognize why.
A villain is easier to remove than a sediment layer.
Then Colonel Park added:
“There was guidance before mine.”
“What guidance?”
“Standardization memo. Reconstruction after capture failure.”
Vale frowned.
“Year?”
“2021.”
Vale looked at me.
I saw his face change.
Small.
“What?”
I asked.
He closed his eyes.
“I wrote part of that memo.”
There.
Not the August violation.
Not Mason's decision.
But Vale himself had helped author the rule that allowed reconstructed media in limited circumstances.
I almost laughed.
“You came through the glass to investigate your own wording.”
“No.”
He looked irritated.
Then corrected himself.
“Not intentionally.”
Fair.
The memo said reconstruction was allowed only if:
Scoring derived from validated contemporaneous data.
Reconstruction clearly marked.
Mason violated both safeguards.
Still, the existence of the shortcut began in policy Vale helped write.
I asked:
“Did you know the local example dropped the labels?”
“No.”
“Would you have checked if August hadn't happened?”
“Probably not.”
Another honest answer.
Then Vale did something I respected.
He added his own role to the standardization review.
No one had accused him of misconduct.
He requested that another office examine whether the policy language had encouraged misuse.
Not because he wanted to confess.
Because the question now existed.
Then the evaluation center received a temporary rule:
No reconstructed media in gate-event scoring until policy review completed.
Good.
Also inconvenient.
Three classes had to reschedule capture-heavy events.
People complained.
Vale accepted the complaints.
May you like
Mason had been wrong to turn inconvenience into permission.
The answer could not be pretending inconvenience did not exist.