The father groaned.
“She means clothes.”
The CEO laughed.
“No.”
“Just hungry.”
The child inspected pizza.
“Pineapple?”
“No.”
“Good.”
They ate at a folding table.
The father discovered something on day nine.
Not in the module.
In the source archive.
R-stop Seven required two-part authorization when used above twenty miles per hour.
One credential to request shutdown.
Another to override staged deceleration and force immediate ignition interruption.
The module in the hypercar had received both.
The first credential belonged to the security chief.
Cloned.
The second belonged to a legacy engineering administrator.
That account had been inactive ten years.
The CEO looked at the identifier.
“Who controlled legacy admin accounts after Meridian acquisition?”
The father answered:
“Central systems.”
She knew who led integration.
The chairman.
Again.
But credentials alone still did not prove he used them.
Then an investigator found a password-reset request.
Three months earlier.
The legacy account had been reactivated by an IT executive under a board-level “historical audit project.”
Approver:
Office of the Chairman.
The CEO read the document twice.
Her face went numb.
The father watched.
“You okay?”
“No.”
“Good.”
She looked up.
He smiled slightly.
“Honest answer.”
She almost smiled.
The chairman was interviewed.
He denied ordering reactivation for sabotage.
Claimed the account was needed to review old telematics IP related to sale.
That was plausible.
Until investigators found the security chief’s copied route file on the chairman’s personal assistant’s encrypted laptop.
The assistant cooperated immediately.
She testified the chairman had asked her to download the CEO’s route “for scheduling.”
Then he forwarded it to a private email.
Who owned the email?
The consulting company tied to the investment consortium.
The chain tightened.
Still, the chairman insisted he never authorized immobilization.
He said he merely wanted the consortium to know when the CEO would arrive.
The CFO became more important.
He had received the route from the consulting company.
He had messaged the private contractor:
Delay her past vote. No injuries.
There.
Not murder.
Not assassination.
Delay.
The contractor used stolen security credentials and modified R-stop firmware.
The black SUV was supposed to arrive after the shutdown, collect the CEO, tell her the car had suffered a cyberattack, and drive her to a “secure location” while communications were restricted.
By the time she reconnected, board vote would be over.
The security chief discovered the credential theft.
He drove out to intercept.
Someone from the contractor’s team tampered with his SUV steering module remotely using access they had through the corporate fleet system.
His crash was not fatal only because he had been driving slowly when steering assist locked.
The CEO sat in federal conference room listening.
Her hands became cold.
The lead investigator said:
“We do not currently have evidence the chairman ordered the steering interference against your security chief.”
“What about my car?”
“We have evidence the CFO authorized delay.”