Chapter 21 - FINDING THE TRUTH STARTED COSTING HER THE LIFE SHE HAD REBUILT.
For the first time since Christopher’s sentencing, Lucas’s mother considered stopping.
Not because the evidence weakened.
Because it kept getting stronger.
That was the problem.
Every new document created another meeting.
Every meeting required time off.
Every deposition created another article.
Every article found its way to school.
Her boss called her into the office on a Thursday.
She closed the door behind herself.
“Am I in trouble?”
“No.”
“Good opening.”
Her boss smiled.
Then became serious.
“You’ve missed eleven hours this month.”
“I used PTO.”
“I know.”
“And I worked late.”
“I know.”
“So?”
“So I’m asking whether this is going to become a long-term scheduling issue.”
There it was.
Not retaliation.
Not discrimination.
A reasonable workplace question.
She had spent years resenting people who reduced everything to systems.
Now she understood why systems cared about hours.
Patients still needed calls returned.
Claims still needed processing.
Coworkers covered when she left.
Her trauma did not erase their workload.
“I don’t know.”
Her boss nodded.
“Can we plan better?”
“Yes.”
“Then plan better.”
That was it.
No firing.
No cruelty.
Still, she walked back to her desk embarrassed.
Years earlier Christopher would have solved the problem with money.
Stay home.
Use family insurance.
Take the company car.
Let him handle it.
Now independence meant negotiating real limits with people who did not owe her special treatment.
Sometimes dignity looked like being held to the same attendance policy as everybody else.
She reorganized deposition schedules.
Asked the civil attorney to combine interviews.
Declined one media request after another.
The local station wanted an exclusive.
A national true-crime producer emailed.
A podcast offered to pay expenses.
She said no.
Her attorney asked why.
“Because Lucas has detention when he shoves somebody for repeating this story.”
Fair.
She wanted the truth on record.
She did not want their lives becoming content for strangers.
Christopher’s family company took a different approach.
Their attorneys filed motions to restrict confidential corporate records.
Some requests were reasonable.
Customer privacy.
Employee data.
Trade secrets.
Others felt broader.
One filing argued public dissemination of executive access architecture could damage business relationships.
Her attorney translated.
“They don’t want clients learning how loose the old system was.”
“Can they stop us?”
“They can stop us from publishing protected discovery. They can’t stop evidence being used properly in court.”
The company also sent a cease-and-desist letter to the former engineer who had warned about executive access years earlier.
He had spoken to investigators.
Now he was considering speaking publicly.
The letter cited confidentiality provisions.
Lucas’s mother heard about it during a strategy meeting.
“Are they threatening him?”
“They’re enforcing a contract.”
“Same thing.”
“Not legally.”
She sighed.
The lawyer continued.
“He’s scared about his pension benefits.”
“Can they take those?”
“Not automatically. But litigation is expensive.”
There it was again.
The cost of speaking.
Her civil claim had originally been about her privacy.
Now witnesses were calculating mortgages and retirement.
She did not want to repeat Christopher’s mistake.
Turn everybody else’s risk into a tool for her goal.
She asked the attorney:
“Can we get what we need without him going public?”
“Yes.”
“Then tell him not to go public for me.”
“You understand I don’t represent him.”
“I know. Just make sure he knows I’m not expecting it.”
The former engineer eventually agreed to a deposition under protective order.
No cameras.
No reporters.
No public spectacle.
He brought an old notebook.
He had kept technical notes throughout his career.
Most were incomprehensible.
Server IDs.
Firmware versions.
Ticket numbers.
Then he found the relevant page.
Executive Demo credential expansion.
Chairman wants unrestricted household QA.
Raised privacy objection.
Response: family accounts are internal trust environment.
Lucas’s mother stared at the phrase.
Internal trust environment.
“What does that mean?”
The engineer shrugged.
“It wasn’t a technical term.”
“What did it mean to you?”
“That leadership believed family members could consent for each other.”
“Could they?”
“I’m not a lawyer.”
Smart answer.
The engineer had pushed for separate user permissions.
Christopher’s father rejected the change as cumbersome.
The company sold security technology to clients while treating privacy inside the owner’s family as optional.
The attorney asked whether Christopher had access to the executive token.
“Not officially.”
“Could he get it?”
“Maybe.”
“How?”
“His father could give it to him. His mother could know the password. Somebody could forward an authentication code.”
“Did you ever see that happen?”
“No.”
Again, no magical proof.
Then the engineer mentioned a system function nobody had discussed before.
Session mirroring.
When an executive demonstration account opened a feed, another authorized employee could mirror the session for technical support.
“Would that create two viewer records?”
“Yes.”
Lucas’s mother leaned forward.
“Could the external session have been software mirroring Christopher’s mother?”
The engineer considered.
“Not with the log format you showed me.”
“Why?”
“A mirrored support connection would have a child-session ID. Your token looks primary.”
So the second viewer was independent.
Not automated.
Not a duplicate.
Someone authenticated separately.
That narrowed things.
The engineer examined the 7:34 session.
“The source device fingerprint might exist elsewhere.”
“Fingerprint?”
Browser type.
Operating system.
Hardware characteristics.
Not enough to identify a person alone.
But perhaps enough to connect sessions to other company systems.
The original security archive no longer held the fingerprint.
The company’s single-sign-on server might.
Did records from three years ago survive?
Probably not.
Then the engineer remembered something.
The company had undergone a cyber insurance review after the poisoning case.
As part of that review, it exported historical authentication data to an outside risk consultant.
That consultant was independent.
Not family controlled.
The civil attorney subpoenaed the archive.
The consultant responded that records were stored offline.
Retrieval took two weeks.
Meanwhile, Christopher’s father’s attorneys offered settlement discussions.
No admission of intentional surveillance.
No admission of concealment.
Payment.
Privacy reforms already implemented.
Mutual non-disparagement.
Lucas’s mother read the number.
It was more money than she had ever personally possessed.
Enough to pay off the car.
College savings.
Down payment.
Emergency fund.
Real security.
Her civil attorney did not tell her what to do.
“You need to understand what you’re buying and what you’re selling.”
“What am I selling?”
“Time. Risk. Public findings. Possibly discovery.”
There it was.
Money could create safety.
It could also close doors.
Christopher’s family had spent years teaching her that.
She took the offer home.
Did not show Lucas the number.
He was doing math homework.
Fractions.
He hated fractions with a personal intensity.
She sat at the table.
“Mom?”
“Yeah?”
“If I have six-tenths and Tyler has three-fifths, who has more?”
“Same.”
He stared at the worksheet.
“That is stupid.”
“Correct.”
“Why write it differently?”
“Because math enjoys conflict.”
He went back to work.
She looked at the settlement offer.
Enough money to make practical life easier.
In exchange, the second viewer might remain formally unresolved.
She imagined telling Lucas later:
I stopped asking because they paid us.
That was unfair.
Settlements were not inherently wrong.
Money could compensate for real harm.
But she knew herself.
She would keep opening the drawer.
Keep reading the token.
Keep wondering.
The next morning she declined.
Her lawyer raised an eyebrow.
“You’re sure?”
“No.”
“Good answer.”
“What happens now?”
“We keep going.”
The risk consultant’s archive arrived that afternoon.
The executive token sessions all shared the same device fingerprint.
Windows laptop.
Specific browser version.
Specific hardware signature.
Investigators compared the signature with other company authentication records.
One match.
Hundreds of logins over four years.
User:
Chairman Executive Laptop.
Assigned to Christopher’s father.
The device fingerprint did not prove he sat behind the keyboard every time.
But it destroyed one major explanation.
This was not an employee using some random demonstration credential.
The camera sessions came from the laptop Christopher’s father used every day.
Then the consultant found something else.
At 7:33 p.m. on the poisoning night, one minute before the kitchen camera opened, the same laptop logged into the family company email system.
Multifactor authentication completed through Christopher’s father’s phone.
An email was sent from his account.
To Christopher.
May you like
Only four words:
I’m looking now, son.
