Three months after Richard Cole walked out of Horizon, the factory had settled into a different rhythm.
There were fewer closed-door meetings. Engineers no longer waited for Richard's approval before making ordinary decisions. People spoke more freely on the production floor, and the constant tension that had once followed every maintenance problem seemed to have disappeared.
My company, Parker Precision Services, had grown faster than I expected.
The five-year agreement with Horizon had given me enough stability to hire two controls engineers and one field technician. I still handled the difficult diagnostics myself, partly because I enjoyed the work and partly because I had learned the hard way that important details could disappear when too many people assumed someone else was watching.
Eleanor never treated me like a former employee.
She treated me like a business partner.
That distinction mattered.
On a Tuesday morning, I was reviewing Meridian's production data when my phone rang.
It was Walter.
“Bay Three,” he said.
“What happened?”
“Machine stopped.”
“Alarm?”
A pause.
“That’s the strange part.”
I stood immediately.
“What do you mean?”
“No alarm.”
I grabbed my laptop.
“I’m coming.”
When I reached Horizon, Walter was waiting beside Meridian with his arms folded.
The spindle was motionless.
The production operator stood beside the control cabinet.
“Nothing on the screen,” he said.
I checked the controller.
No active fault.
No emergency stop.
No overload.
No communication error.
The machine simply wasn't moving.
I ran the startup sequence.
Nothing.
I checked the incoming power.
Normal.
Control voltage.
Normal.
Servo amplifiers.
Normal.
The machine still refused to respond.
Walter leaned against the cabinet.
“You ever seen that?”
“Once.”
“When?”
“Before Meridian passed qualification.”
His expression changed.
I connected the diagnostic laptop.
The first thing I checked was the event history.
There was an entry.
Not an alarm.
A configuration access.
The timestamp was 6:14 that morning.
I stared at it.
“Who was here?”
Walter pointed toward the security desk.
“Night shift.”
I checked the user ID.
User 3.
Richard's old administrative account.
My stomach tightened.
“That's impossible.”
Walter looked at me.
“Account wasn't supposed to be disabled?”
“Yes.”
I called Horizon's IT manager.
“Can you check whether Richard Cole's administrative credentials are still active?”
“I'll look.”
“Immediately.”
Thirty seconds later, he called back.
“User 3 is disabled.”
I looked at the screen.
“Then how did it access Meridian?”
Silence.
“I don't know.”
Neither did I.
I copied the event log before touching anything else.
Then I checked the machine's configuration.
The protected values were correct.
No altered gains.
No modified acceleration limits.
Nothing obvious.
But one setting had changed.
The automatic production authorization had been disabled.
Someone hadn't tried to destroy Meridian this time.
Someone had tried to stop it from running.
That was more deliberate.
Eleanor arrived while I was still examining the controller.
“What happened?”
I showed her the log.
She read the timestamp.
Then the user ID.
Her face hardened.
“Richard.”
“Maybe.”
“You don't believe that.”
“No.”
“Why?”
“Because his account is disabled.”
She looked at the IT manager.
“Find out how this happened.”
He nodded and left.
I checked the network logs.
Nothing.
Then I noticed something unusual.
The controller had communicated with an external address at 6:13.
One minute before the unauthorized access.
I wrote down the address.
Eleanor watched me.
“Can you trace it?”
“Probably.”
“Do it.”
I spent the next hour reconstructing the connection.
It had not come through the company's main network.
It had come through a maintenance gateway.
An old one.
A gateway Horizon hadn't used in months.
Walter scratched his chin.
“I thought that thing was removed.”
“It wasn't.”
“Who installed it?”
I looked at Eleanor.
She didn't answer immediately.
“Richard.”
The word sat between us.
I checked the gateway's configuration.
There was a remote-access account still active.
The username was simple.
RCOLE.
Eleanor closed her eyes for a moment.
“Call legal.”
I nodded.
Before I could make the call, another message appeared on my laptop.
Remote session initiated.
Someone was connecting again.
I immediately disconnected the gateway.
The session died.
Walter stared at the screen.
“Whoever that was knows we're watching.”
I saved the logs.
Eleanor looked at me.
“Can you find out where the connection came from?”
“Yes.”
“How long?”
“Give me an hour.”
She nodded.
“Take two.”
That afternoon, I traced the connection to a commercial network outside the city.
The address itself didn't identify Richard.
But the pattern did.
The same gateway had been accessed three times in the previous month.
Every access occurred shortly before a production delay.
Not catastrophic failures.
Small interruptions.
Five minutes here.
Ten minutes there.
Enough to disrupt schedules without attracting immediate attention.
Someone had been testing the system.
And Meridian wasn't the target.
Horizon was.
I called Eleanor.
“We need to talk.”
She arrived at my office twenty minutes later.
I placed the reports in front of her.
“This isn't random.”
She read them slowly.
“What's the objective?”
“I don't know yet.”
She looked up.
“Then find out.”
I nodded.
She gathered the documents.
At the door, she stopped.
“Ethan.”
“Yes?”
“If this is Richard, don't underestimate him.”
“I won't.”
She left.
I stared at the old access logs.
Richard had failed once.
He had lost his job, his consulting scheme, and his position inside Horizon.
But people like him didn't always stop when they lost.
Sometimes losing simply changed what they were willing to risk.
And somewhere outside the city, someone had just connected to Horizon's machines again.
Click here to continue reading: PART 6: Someone Was Testing Horizon From the Outside, and the First Person to Discover the Pattern Was the One Everyone Had Stopped Watching
At 11:07 My Eleven-Year Career Ended, but Five Minutes Later the Machine They Blamed Me For Suddenly Became Their Biggest Problem
Part 5 of 20
