New performance metrics showed lower digital ticket closure rate than department average.
That was in Marcus’s summary.
Victoria leaned back.
Something cold formed inside her.
She called Olivia Grant.
“Come upstairs.”
Olivia arrived ten minutes later.
Victoria placed two documents side by side.
“Explain.”
Olivia looked.
Her face changed.
“Where did you get the original?”
“His personnel file.”
Olivia became quiet.
Victoria continued.
“Why does the restructuring summary remove every favorable historical performance note?”
“I raised that concern.”
“With whom?”
“Marcus.”
“And?”
“He said the restructuring was based on current-state metrics.”
“Did you agree?”
“No.”
“Then why did HR process it?”
Olivia looked toward the window.
“Because the COO classified the affected positions as operational eliminations, not performance terminations.”
Victoria understood.
A procedural distinction.
Convenient.
“Was Ethan’s position actually eliminated?”
Olivia hesitated.
“That depends how you define it.”
“Try the ordinary definition.”
“No.”
Victoria stared.
“His functions were redistributed.”
“To whom?”
“Three people.”
“Then his position was not eliminated.”
“The title was.”
Victoria closed her eyes.
“Who approved that structure?”
“Marcus.”
Victoria stood.
“Get Daniel Brooks.”
Daniel arrived wearing a dark sweater and the expression of a man who already knew trouble was waiting.
Victoria pointed toward the chair.
“Tell me about Ethan Carter.”
Daniel looked at Olivia.
Then back.
“What happened?”
“Answer the question.”
Daniel sat.
“Best maintenance engineer I’ve supervised.”
“Why?”
“Because he doesn’t guess.”
“That simple?”
“No.”
Daniel leaned forward.
“He listens.”
“To people?”
“To machines.”
“To people too.”
“If a junior technician says something feels off, Ethan doesn’t dismiss them.”
“He checks.”
“If data says a machine is fine but the vibration feels wrong, he investigates.”
“He’s prevented more problems than most employees know happened.”
“Marcus’s report says he resisted innovation.”
Daniel laughed once.
“Marcus’s report is garbage.”
Olivia flinched.
Victoria did not.
“Explain.”
“Ethan resisted one rollout.”
“Why?”
“Because the predictive maintenance software was being used to extend inspection intervals before we had enough data.”
“Was he right?”
“Yes.”
“How do you know?”
“Two units flagged normal by the model developed faults within six weeks.”
“Ethan caught both manually.”
Victoria stared.
“Was that documented?”
“Yes.”
“Where?”
Daniel looked at Olivia.
“Engineering incident log.”
Victoria turned.
“Get it.”
They did.
Then more.
Ethan’s name appeared everywhere.
Not in headlines.
In footnotes.
Corrective actions.
Prevented failures.
Training sign-offs.
Emergency response records.
One incident from seven years earlier involved faulty electrical insulation near a solvent-processing area.
Ethan had ordered an immediate shutdown despite production pressure.
Inspection later found a condition that could have become catastrophic.
Marcus’s restructuring file described Ethan as overly conservative regarding operational risk.
Victoria read the phrase again.
Overly conservative.
The same caution that may have prevented a major fire had been reframed as a weakness.
“Who edited these reviews?” she asked.
Olivia’s face tightened.
“Marcus’s office.”
“I want version history.”
“Victoria—”
“Everything.”