“No company-wide hero story.”
Vivien almost smiled.
“Fine.”
“And my normal shift schedule when possible.”
“Because of your daughter.”
Ethan looked at her sharply.
She immediately realized the mistake.
Not because mentioning his daughter was inappropriate.
Because she had learned the fact only after he became important to Gideon.
“I read your personnel file.”
“I assumed.”
“I should have known more about the people working here.”
Ethan returned to the monitor.
“You can’t know six hundred people personally.”
“No.”
Vivien said.
“But I can build a company where someone does.”
That was the first thing she said that Ethan believed might matter.
He agreed to help.
The first week produced troubling results.
The resilience vulnerability was real.
More importantly, its internal history did not make sense.
Ethan’s original test records showed one pattern.
The central infrastructure logs showed another.
Warning flags that should have appeared had been downgraded or removed.
A follow-up work order had been closed without the work being performed.
Vivien sat beside Ethan one evening reviewing the records.
She was not technically incompetent.
Far from it.
She understood systems architecture at a strategic level.
But Ethan saw details she missed.
He pointed at a timestamp.
“What?”
“That maintenance event.”
Vivien read it.
“Controller update.”
“No update happened.”
“How do you know?”
“I was here.”
“You remember one night four months ago?”
“I wrote the maintenance schedule.”
He opened his private operations ledger.
Not secret.
Just disciplined.
Every test.
Every abnormal reading.
Every physical access event he personally verified.
The central system claimed a firmware update occurred at 2:13 a.m.
Ethan’s record showed no authorized maintenance.
“Could someone have done it without facilities?”
“Possible.”
“Likely?”
“No.”
They checked building access.
A technical administrator entered at 1:48.
Left at 2:37.
Name:
Roland Pierce.
Vivien stared.
“Why would a senior director be here at two in the morning?”
Ethan did not answer.
They kept digging.
One inconsistency became six.
Six became eleven.
Logs had been altered in small ways.
Nothing spectacular.
A severity flag reduced.
A maintenance event relabeled.
A device briefly removed from monitoring.
An alert acknowledged using an administrator credential.
Each event looked harmless alone.
Together, they formed a pattern.
Whoever made the changes understood exactly how much manipulation would disappear inside ordinary operational noise.
That worried Ethan.
“This isn’t sloppy.”
Vivien stood beside him in the server operations room.
“No.”
“This person knows the thresholds.”
“Yes.”
“And your reporting habits.”
Ethan looked at her.
“That too.”
The sabotage had been spread across weeks.
Patient.
Incremental.
Designed not to trigger automated anomaly detection.
Vivien asked:
“Could Roland do it?”
“Technically?”
“Yes.”
“With his access, some of it.”