Chapter 3 - THE NINETY-DAY PLAN THAT LASTED FIVE YEARS
Avery kept the first ninety-day security plan.
I saw it later.
Simple.
Temporary.
That word appeared three times.
Temporary driver support.
Temporary residential camera expansion.
Temporary location coordination during the active threat.
Temporary review of school pickup lists.
Every measure had a review date.
Then review dates became renewals.
The extortionist’s arrest reduced the risk.
Nolan produced a residual-risk assessment.
Public association with Lawson family remained.
Fine.
Another six months.
Then a man photographed the twins at a charity 5K.
Probably harmless.
Nolan classified it as surveillance concern.
Another review.
Then somebody attempted to access Avery’s home Wi-Fi remotely.
Likely automated.
Nolan classified it as hostile reconnaissance until IT disproved that.
By year two, the original threat had stopped being the reason.
The reason became:
There had once been a threat.
Avery removed the driver first.
Nolan objected.
She insisted.
Good.
Then she wanted the exterior camera system returned to local control rather than mirrored into Lawson Ridge’s security operations center.
Nolan delayed.
“Transition risk.”
Then:
“Firmware migration.”
Then:
“We need redundancy.”
Avery called me.
I missed it.
She emailed.
My executive assistant tagged it:
FAMILY SECURITY.
Our office routing rules automatically forwarded family-security matters to Nolan’s team.
He replied.
Not pretending to be me.
Worse in a quieter way.
Everett has asked Executive Protection to manage technical security questions. Happy to discuss.
Factually true.
I had.
Avery replied:
I am asking Everett whether I still have to use Executive Protection.
That email never reached me.
Why?
The routing rule.
No conspiracy required.
Bad architecture.
The complaint about the system entered the system.
The system assigned it to itself.
Nolan responded:
There are active risk factors that make immediate withdrawal inadvisable.
Avery stopped emailing me.
She later said:
“I thought you had chosen.”
I answered:
“I never saw it.”
She looked at me.
“That is still a choice if you built the route.”
There.
Hard.
Correct.
Over the next two years, Nolan’s team retained administrative access to:
The exterior cameras at Avery’s house.
Her alarm panel.
A vehicle telematics portal installed during the threat period.
The school emergency-pickup liaison.
Travel-monitoring alerts attached to the twins’ names.
Nothing like a secret government network.
Ordinary commercial security systems.
That made it worse in a different way.
Control can be built from normal products if one person keeps permissions everybody else assumes expired.
Avery began noticing.
She changed her alarm code.
Nolan’s team reset an administrator credential after a false alarm because they still held master access.
She asked why.
“Emergency redundancy.”
She removed vehicle tracking.
Nolan had another fleet-security integration enabled through the insurer-affiliated platform.
She complained.
He said:
“It only activates for incident response.”
Then she drove to Milwaukee for a weekend with the boys.
Nolan texted:
Road conditions deteriorating north of Racine. Consider delaying return.
Avery stared at the message.
“How did you know where I was?”
His answer:
“Family protection monitoring.”
She called me.
Again.
I answered that time.
“Everett, I want your people out of my car.”
I remember laughing slightly because I thought she was being figurative.
“They’re not in your car.”
“You know what I mean.”
“I’ll tell Nolan.”
“No.”
There.
“Tell me.”
I became irritated.
“Avery, I do not know the telematics architecture.”
“Then why did you create it?”
“I didn’t.”
“Your company did.”
“For safety.”
There.
The word that ended conversations.
She said:
“I did not ask for permanent safety.”
I answered badly.
“No one asks for kidnapping either.”
Silence.
Then:
“Do you hear yourself?”
I did not.
Not then.
Avery disconnected the system through her own mechanic.
Nolan filed an internal incident note:
Principal-associated household has disabled protective telematics contrary to recommendation.
Principal-associated household.
My brother’s widow and children reduced to a risk category attached to me.
Noah found the first hidden tracking device when he was six.
Not a spy device taped beneath a shoe.
A small commercial asset tag inside the lining of his school backpack.
Nolan’s team had placed it after the school temporarily lost track of a bag containing medication and emergency information.
Avery had initially agreed to tagging the bag.
She thought it was inventory.
Then learned the tag could report broader location information.
She removed it.
Called Nolan.
“Do not put another one in their belongings.”
He said:
“This one was in a bag, not on the child.”
A sentence legally narrower than the trust it violated.
She replied:
“No.”
Clear.
Another tag appeared months later in a travel case.
Nolan said a junior analyst had followed an old protocol.
Maybe true.
The analyst was disciplined.
Avery told me none of this.
That became her flaw.
Not because she owed me every complaint.
Because she eventually decided I had already chosen Nolan and built an entire counter-process around that assumption.
She hired Leah Park.
Privacy and employment lawyer.
Documented access.
Sent revocation notices.
Changed vendors.
Requested data.
No children involved.
Good.
Leah discovered something strange in Lawson Ridge building logs.
Nolan had accessed the executive floor using Everett-level authentication during periods when I was overseas.
Not his named badge.
An override credential.
Why would Avery’s lawyer care about tower access?
Because one set of home-security admin requests contained an approval reference:
EL-BLACK AUTH
Leah asked what that meant.
Avery remembered Nathan.
Years earlier, when Lawson Ridge moved into the tower, Nathan had toured my office.
He came home and joked:
“Everett has a Batman card.”
Avery asked:
“What?”
“Black credential. Opens everything. Security hates that he carries it.”
Nathan had exaggerated.
Slightly.
The credential was an executive emergency-access token created after a major building-system failure during construction.
It bypassed certain internal zones.
Not bank vaults.
Not police doors.
Still powerful.
The original access design had two emergency tokens.
One assigned to me.
One sealed in a controlled security cabinet requiring dual authorization to release.
Every other credential was named and logged normally.
At least that was what I believed.
Then one afternoon Nolan came to Avery’s house after she revoked the remaining remote camera access.
They argued.
He left.
Twenty minutes later Noah found a black card beneath the dining table.
“Mom?”
Avery picked it up.
Matte black.
Silver edge.
No printed name.
She knew.
Not proof of every allegation.
Enough to ask a question.
Why did Nolan Price have Everett’s private emergency credential in my house?
She did not call me.
Why?
Pride.
Fear.
And because every attempt to reach me about security had taught her the same lesson.
Nolan would hear first.
Leah told her:
“We can go through General Counsel.”
Avery said:
“He owns the company.”
“He doesn’t own privilege.”
Good lawyer.
They prepared a direct package for Simone Grant.
Before they sent it, Avery decided she wanted to confront me once.
Face-to-face.
No email.
No route.
That decision led to the morning in my office.
Leah advised:
“Do not bring the boys.”
Avery said:
“I don’t have anyone I trust at five in the morning.”
“Then change the time.”
“I know Everett’s schedule. He’ll be there before seven.”
“Make an appointment.”
“Through who?”
There.
The gatekeeper problem.
She still should not have brought them.
She knew that later.
But at the time she believed the tower itself was safe.
My office.
My floor.
My building.
The one place Nolan could not control completely because it belonged to me.
May you like
That belief turned out to be almost exactly backward.
The person I trusted to control access had become the reason every normal route felt unsafe.
