Chapter 7 - I Had Also Crossed Lines

I had recorded Celeste in the kitchen from a doorway.
Was that legal?
Video:
yes, generally, in that context.
Audio:
my phone captured little, mostly room noise.
But I had done more than that in the months before.
That was the part I preferred not to tell.
I had searched foundation vendor records looking for Celeste-connected entities.
Authorized for my role?
Partly.
I had also searched:
family-office corporate registrations,
property records,
litigation databases.
Public.
Fine.
Then I used my father’s assistant’s calendar access.
That was not fine.
I had old delegated permission from when I helped with foundation scheduling.
The access had never been revoked.
I used it to see:
which lawyers Celeste met,
when,
where.
No hacking.
Still outside purpose.
Then I asked Maria and two other employees to tell me if Celeste entered:
medication room,
records office,
foundation floor.
They agreed.
But they were hourly employees.
I was founder’s daughter and governance director.
Could they really say no?
That bothered me only after Dana said:
“You built your own informal surveillance network.”
I snapped:
“That is not the same as drugging someone.”
“No.”
Then:
“Different wrong can still be wrong.”
I hated her.
Then IT review.
My old calendar access was revoked.
Documented policy violation.
The foundation board issued me written reprimand for:
using administrative access outside authorized business purpose,
and asking foundation/household employees for information related to a personal family concern without defined investigative authority.
No termination because:
no data exfiltration beyond calendar metadata,
no malicious use,
self-disclosure,
and my evidence on Celeste came independently from direct observation.
Still.
It went in file.
Then Maria.
I apologized.
She said:
“You already did.”
“Not for the calendar stuff.”
“I don’t care about your father’s calendar.”
“I care that I used staff.”
Maria looked at me.
Then:
“You asked me because you trusted me.”
“That’s the flattering version.”
“And because you knew I saw things.”
“Yes.”
Then:
“Next time ask whether it’s my job.”
Good.
Then another employee, Jasmine, had told me Celeste met a man from Vaughn Strategic in library.
I had later included that in notes.
Jasmine thought she was “helping the family.”
She worried her name would enter court.
It did not become material.
But stress was real.
I apologized.
Then foundation job.
Could I remain governance director after using access badly?
Board chair Helena Brooks said:
“Yes, with corrective plan.”
I said:
“I think I should resign.”
She asked:
“Because you did something unforgivable?”
“No.”
“Because you’re embarrassed?”
Maybe.
Then:
“Don’t turn accountability into dramatic self-punishment.”
That sounded like Dana.
I stayed six months.
Completed:
access-control remediation,
conflict training,
clear family-vs-foundation protocols.
Then left voluntarily for a job at an independent nonprofit governance consultancy? Maybe too neat.
I wanted distance from family.
I joined a mid-sized healthcare foundation as deputy general counsel? My background corporate fraud attorney. Perhaps I had returned to family foundation after law. Better future:
I became general counsel at a regional university foundation, unrelated to Ashford.
But not immediately.
I took three months off.
Then joined a national nonprofit compliance organization.
No father influence.
Interview question:
“Why leave Ashford Foundation?”
I answered:
“Family governance and organizational governance had become too entangled, including in my own role.”
True.
Then background.
The public poisoning case meant everyone knew.
Interviewer asked:
“You recorded the cake incident?”
“Yes.”
“Did that make your departure necessary?”
“No. My own boundary violations did.”
That surprised them.
I got the job.
Then my father.
He felt abandoned.
“You’re leaving because of her.”
“No.”
“Because of me?”
“Partly.”
That hurt.
Then I explained:
I could be his daughter or foundation governance officer, but doing both had made every disagreement unstable.
He said:
“You’re good at the job.”
“Other people can be good.”
That was harder for both.
Then foundation replaced me through search.
Not cousin.
Not family friend.
A woman named Nisha Patel with museum/nonprofit audit experience.
My father disliked her first meeting because she corrected him on agenda.
Excellent sign.
Then I became ordinary employee somewhere else.
My father could not call my boss.
He technically could, but I told him not to.
He obeyed.
Mostly.
Then my fraud-attorney instincts.
At new job, I over-investigated a procurement concern.
A staff member approved a vendor where spouse worked.
I immediately suspected concealment.
Records showed:
spouse relationship disclosed in HR form,
but not copied to procurement system.
Process gap.
Vendor pricing competitive.
No kickback.
The employee had made disclosure somewhere, not nowhere.
I learned:
patterns require context.
Then another case:
executive submitted fake receipts.
Real fraud.
Terminated after investigation.
I liked evidence better than intuition.
Then revenge.
The opening line in my head had been:
that was only beginning of my revenge.
In reality, revenge made a bad project plan.
What did I actually do?
Preserved evidence.
Reported.
Separated conflicts.
Corrected records.
Testified.
I did not:
destroy Celeste socially,
seize her assets,
ruin Andrew,
take over foundation.
That would have been another form of control.
Then my father asked years later:
“Do you regret filming?”
“No.”
“Do you regret not confronting her in kitchen?”
I thought.
If I had:
she might have dumped bottle.
No toxicology.
Maybe denied.
Maybe no cake served.
Safety argument says:
stop contamination immediately.
I had allowed twenty minutes to pass until Maria warned ballroom.
That was risky.
Why did I wait?
I wanted evidence.
There.
My fraud instincts overrode immediate safety.
I had filmed, then gone back to ballroom hoping to preserve act and maybe see what she did next.
That was not optimal.
A food-safety professional later said:
“You should have stopped service immediately.”
Yes.
I had failed there.
Maria’s scream corrected me.
That was uncomfortable.
Then I included it in testimony.
Defense counsel asked:
“You believed the cake was poisoned and still allowed it toward service?”
I answered:
“I suspected contamination. I should have alerted staff immediately. I did not.”
That did not erase Celeste.
It made me credible.
Then workplace protocol used incident:
any suspected tampering -> immediate stop, preserve evidence, report.
Do not prioritize documentation over exposure prevention.
Good.
Then I told Maria:
“You saved us from my cleverness.”
She laughed.
“Finally you admit.”
Then one day at new job, an employee came to me saying:
“I think the CFO is stealing.”
Old me:
secretly build case.
New me:
“Tell me what you observed.”
Then:
route to audit committee.
preserve records.
no personal investigation beyond role.
Growth is often less dramatic than the mistake.
It looks like boring process.
I had spent months believing silence was my weapon against Celeste.
In truth, silence had helped me see.
Then it nearly kept me from speaking when safety required.
No trait stays virtuous in every context.
That was one of the hardest lessons the cake taught me.
The foundation board’s reprimand embarrassed me more than Celeste’s lawyers attacking me.
Because it came from people I respected.
The letter said:
Ms. Ashford acted from a stated concern regarding potential family-related misconduct. That concern later proved partially well-founded. However, the legitimacy of a concern does not expand authorized access.
There.
Then:
Use of delegated calendar access outside intended purpose created privacy and governance risk.
I read that six times.
Partial vindication does not retroactively authorize method.
Then my father wanted board to remove reprimand from file.
I said no.
He looked surprised.
“It could follow you.”
“It should, where employment records properly go.”
Then:
“It is accurate.”
That was one of the first times I stopped him from protecting me.
Then a second issue.
I had kept personal notes about Celeste in a private cloud document.
Names:
Maria,
Jasmine,
Colin,
Samuel.
Some notes included:
rumors,
speculation,
medical observations.
Once litigation began, those notes became discoverable.
Defense counsel received through process.
Maria’s name appeared.
She was furious.
“You wrote that I thought Celeste was stealing pills?”
“You told me that.”
“I said I saw her in cabinet.”
Correct.
I had translated observation into suspicion in notes.
Dangerous.
I apologized.
Then discovery taught:
write facts as facts,
inference as inference.
At new job, I trained investigators:
Observed:
employee entered vendor office at 9:14.
Inference:
possible coordination.
Never merge.
I learned because I had.
Then my video.
Defense attacked chain:
I had paused recording.
Why?
Could edit.
Forensic metadata showed original file intact for recorded duration.
No edits.
But missing twenty seconds before/after mattered.
I could not say what Celeste did outside frame.
That was fair.
Then kitchen doorway.
Was I trespassing?
No.
Event area.
Family host.
Then privacy expectation?
The kitchen was workplace with staff.
Video did not record intimate conversation.
Still.
Then why record instead of intervene?
My answer remained:
I wanted proof.
Defense lawyer said:
“You wanted revenge.”
I said:
“I wanted evidence.”
“Those can coexist.”
He was right.
I was angry.
I wanted her caught.
Did that make evidence false?
No.
Did it affect choices?
Yes.
Then after case, I taught myself a rule:
Safety first.
Preservation second.
Investigation by authorized role.
Not:
collect everything.
Then at new nonprofit job, an employee came to me with screenshot of executive’s private text obtained by guessing phone passcode.
The text suggested procurement fraud.
Old me:
use it.
New me:
preserve minimal information, consult counsel about source, independently investigate transaction without exploiting illegally accessed phone.
Fraud substantiated through invoices.
We did not need stolen text.
That felt good.
Then relationship with my father.
I stopped asking:
“Who are you meeting?”
“Did you sign?”
“What did doctor say?”
Unless relevant.
He sometimes volunteered too much.
I said:
“You don’t have to tell me.”
He looked confused.
Then adapted.
Then when Eleanor entered his life, I refused to background-check her beyond what was publicly unavoidable.
But my job instincts screamed.
I asked Dad:
“Have you done your own due diligence?”
He said:
“Yes.”
“Through counsel?”
“Yes.”
Done.
No secret check.
Then I met Eleanor.
She asked:
“Did you investigate me?”
“No.”
“Why not?”
“Personal growth.”
She laughed.
Then:
“I investigated you.”
I stared.
She had Googled me.
Fair.
Then my own romantic life.
I dated a journalist for eight months.
Bad idea? Not inherently.
We set boundary:
he did not cover Ashford.
I did not use him for information.
It ended for ordinary reasons:
travel,
temperament.
No betrayal.
Then therapy asked:
What does trust mean if you cannot verify everything?
I said:
stupidity.
Later:
choice under uncertainty.
Harder.
Then revenge language.
I once wrote in draft journal:
I’ll destroy her with facts.
I found years later.
Embarrassing.
Facts are not weapons owned by the righteous.
They can clear people too:
Andrew.
Hawthorne.
foundation CFO.
IT team.
The investigation proved things I did not want:
Celeste did not cause every problem.
My father had enabled.
I had crossed lines.
Foundation money was safe.
If I only wanted revenge, those facts would be inconvenient.
If I wanted truth, they belonged.
Then one colleague asked:
“Would you do it differently?”
“Yes.”
“I’d stop service immediately.”
Then:
“I’d call counsel sooner.”
Then:
“I would not recruit employees into personal suspicion.”
Would I still record if I saw her pouring unknown substance?
Probably yes, if safe.
Then alert immediately.
May you like
That answer was less cinematic.
Better.