Chapter 13 - HE TRIED TO HOLD THE COMPANY HOSTAGE
The phrase kill switch sounded dramatic.
The reality was worse because it was technical.
Predictive Logistics managed live routing for warehouses, trucking networks, and distribution centers across North America.
If master deployment keys were revoked, customer systems would not instantly vanish.
They would fail gradually as services attempted to refresh credentials.
Updates would stop.
Optimization engines would lose access to certain cloud functions.
Some clients could fall back to manual operations.
Others could not.
A deliberate shutdown could disrupt food distribution, medical supply routes, and factory schedules.
Matthew had turned software continuity into personal leverage.
I called Priya Nair at 1:18 a.m.
She answered on the first ring.
"I was expecting you."
"Why?"
"Because Lauren called me first."
I stopped.
"You know Lauren?"
"She found my number in the employee petition."
"What did she tell you?"
"Enough to scare me."
Priya was now vice president of platform engineering.
She knew the deployment architecture better than anyone except Peter.
I asked whether a single executive could revoke master keys.
"Officially, no."
"Unofficially?"
"Peter created an emergency root process last quarter."
"Can Matthew access it?"
"I do not know."
"Assume yes."
Priya went quiet.
"Then we need to rotate everything before he does."
"How long?"
"Six hours if we move recklessly."
"Safely?"
"Twelve to eighteen."
We did not have eighteen.
Matthew still controlled the CEO office.
The special committee had not suspended him.
Any engineer who acted without authorization risked termination or worse.
"Can the board authorize a defensive rotation?"
"Yes."
"Then prepare it."
"Clare, you are not on the board."
"I know."
"And you are not an employee."
The phrase should have hurt.
This time it made me smile.
"I know that too."
"Then what exactly are you asking me to do?"
"Nothing yet."
I looked at Miriam.
"I am asking you to be ready when someone with authority finally grows a spine."
Priya laughed once.
"That I can do."
At 1:40, Miriam demanded an emergency board call.
Five directors joined immediately.
Three delayed.
Matthew refused.
Victor joined from his apartment.
He had resigned as lead independent director but remained on the board pending formal acceptance.
The debate lasted twenty-seven minutes.
One director called Lauren's warning unverified hearsay.
Another said acting on it could itself create operational risk.
I listened until I could not tolerate another abstract sentence.
"Ask Peter."
The directors went silent.
Peter was in police custody for questioning and could not join casually.
Miriam contacted his lawyer.
At 2:19, Peter appeared by secure video from a conference room inside the police station.
He looked exhausted.
His hair was unwashed.
His hands shook when he lifted a paper cup.
He did not look like the polished cybersecurity chief who used to give presentations under blue stage lights.
Victor asked whether an emergency root process existed.
Peter nodded.
"Yes."
"Who can trigger it?"
"Originally, three key holders."
"Who?"
"Me, Priya Nair, and Matthew."
"Can one key holder act alone?"
Peter stared at the table.
"Not originally."
"What does that mean?"
"Matthew asked for a unilateral continuity override."
A director cursed.
"Did you build it?"
Peter's voice dropped.
"Yes."
"Can he revoke production keys?"
"Yes."
"Can you disable his override?"
"Not without access to the hardware security module."
"Where is that?"
"NexusCore headquarters."
The board voted six to two to authorize immediate defensive key rotation and temporarily remove Matthew's root access.
It was not a vote to remove him as CEO.
But it was the first time a majority directly stripped him of power.
Priya's team began within minutes.
Then the headquarters badge system locked them out.
Matthew had anticipated the vote.
He activated a building security protocol placing the executive and server floors under restricted access.
Employees received alerts telling them to remain home because of a "credible cyber threat."
Priya called me from the sidewalk outside the tower.
"He shut us out."
"Can building management override him?"
"They say the tenant controls internal floors."
"Police?"
"No warrant for server access yet."
Miriam was already calling the special committee.
My father called the building owner.
Henderson called Ortiz.
Everyone moved at once.
At 2:47, Matthew finally joined the board call.
He sounded amused.
"I understand there has been an attempted coup while I was sleeping."
Victor answered.
"You were directed to preserve operational systems."
"And I am preserving them."
"By locking out engineering?"
"By preventing unauthorized personnel from accessing sensitive infrastructure."
Priya shouted from my speakerphone.
"I am vice president of platform engineering."
Matthew replied without hesitation.
"You are suspended pending review."
Priya stared at the phone.
"You cannot suspend half the platform team."
"Watch me."
The line went silent for one second.
That sentence did more damage to him than any legal brief.
Three directors changed their tone immediately.
Matthew had stopped pretending this was governance.
It was control.
Miriam asked whether he possessed a unilateral root override.
"I do not discuss security architecture on unsecured calls."
"Peter confirmed it."
"Peter is a confessed saboteur."
"Did you instruct him to create it?"
"Counsel has advised me not to answer questions based on stolen materials."
"Did you instruct him to alter Clare's logs?"
Matthew ended the call.
At 3:05, the judge in Delaware issued a temporary order preserving Predictive Logistics assets and prohibiting any officer from impairing software or access credentials.
At 3:11, the order was served electronically on Matthew.
At 3:18, the root security system recorded an attempted master-key revocation.
Matthew did it anyway.
Priya saw the alert from a backup monitor.
"He pulled the trigger."
My heart stopped.
"Did it work?"
"Partially."
"What does partially mean?"
"Some key sets are refusing renewal."
"How long before customers feel it?"
"Two hours for the earliest clusters."
The company had become a hostage scene without a weapon anyone could see.
The police now had a court order and evidence of intentional interference.
Ortiz coordinated with the district attorney.
Building management finally opened the service elevator to authorized engineers accompanied by law enforcement.
Priya entered with four team members at 3:39.
I stayed on video with her from Greenwich.
She walked through dark server-floor corridors while emergency lights reflected from glass walls.
The headquarters felt abandoned.
Most systems were cloud-based, but the hardware security modules controlling root credentials sat inside a locked cage.
Priya reached it.
The cage would not open.
"Matthew changed the physical code."
Peter, watching from the police conference room, gave her an emergency mechanical bypass location.
A detective documented every step.
Priya opened the cage at 3:51.
Then she swore.
One of the three hardware modules was missing.
"Which one?"
Peter asked.
"HSM-3."
His face went white.
"That is the portable recovery module."
"Can Matthew revoke keys remotely with it?"
"Yes."
"Can we rotate around it?"
Peter hesitated.
"Maybe."
Priya snapped.
"I need better than maybe."
Peter closed his eyes, thinking.
Then he gave instructions.
The team began generating an entirely new root hierarchy.
It was dangerous.
If they made one mistake, they could lock out legitimate systems faster than Matthew could.
At 4:12, the first major customer reported authorization failures.
At 4:16, a hospital-supply distributor in Pennsylvania switched to manual dispatch.
At 4:22, a grocery network in Ohio reported delayed routing updates.
Every minute became a countdown.
I watched Priya work and thought about my old notebook.
The first adaptive routing model had been designed for failure tolerance.
Not cybersecurity failure.
Network failure.
I opened the notebook and found an architecture note from graduate school.
Never assume the central planner remains available.
Local nodes must retain a valid fallback state.
I called Priya.
"The old local cache protocol."
"What?"
"Version three."
"Clare, that code has not been used in years."
"The concept is still in the stack."
I remembered arguing with Matthew about it during the first product release.
He wanted centralized control because it was easier to sell.
I insisted every client appliance retain a signed fallback policy.
"Look for RouteSafe cache."
Priya typed.
Peter leaned toward his screen.
"She is right."
Priya found the dormant subsystem.
It still existed because several legacy clients depended on it.
If activated globally, RouteSafe could hold last-known valid routing policies while the key rotation completed.
It would reduce optimization quality.
It would keep warehouses moving.
"Can you activate it?"
I asked.
"With board authorization."
Victor did not wait for another debate.
He obtained written consent from six directors in eight minutes.
At 4:41, Priya enabled RouteSafe fallback across affected customers.
Authorization failures stabilized.
Manual dispatch sites began reconnecting.
The crisis did not vanish.
But the collapse slowed.
At 5:03, the new root hierarchy came online.
At 5:17, the last compromised key set was isolated.
Matthew's portable module became useless.
For the first time, he had pulled a trigger and nothing irreversible happened.
The board called another emergency meeting.
This time nine directors attended.
The vote to suspend Matthew as CEO passed seven to two.
Victor abstained because of his conflicts.
At 5:29 a.m., Matthew Hayes was no longer authorized to act for NexusCore.
I expected relief.
Instead, Henderson walked into the library holding his phone.
"Matthew is gone."
"Gone where?"
"His apartment downtown is empty."
"What about the penthouse?"
"Still sealed."
"Office?"
"He left headquarters before the lockdown."
"When?"
"Security garage footage shows his car exiting at 2:36."
Before the attempted key revocation.
He had used the portable module remotely.
"Track the car."
"It was found in Queens thirty minutes ago."
"Abandoned?"
"Yes."
My father's expression hardened.
"Airport?"
"No confirmed booking."
My phone vibrated.
A message from Matthew appeared.
It contained no threat.
No explanation.
Only a photograph.
The image showed the blue storage case from my father's library.
My old research case.
The one holding the notebooks that proved my ownership.
I spun toward the shelf where it had been stored.
The case was gone.
Matthew had lost control of NexusCore.
May you like
Somehow, he had reached into my father's house and taken the evidence that could prove why I deserved a piece of it.
Related Stories
