Chapter 9 - AARON HAD BEEN WRITING A VERSION OF ME THAT DIDN’T EXIST
There were four incident summaries.
Not filed with police.
Not sent to doctors.
Internal notes Aaron kept in a private company folder.
Each described an interaction involving me.
April 12:
Claire raises voice at Celeste over unauthorized home entry; physically corners her in hallway.
May 7:
Claire becomes hostile during budget discussion; accuses finance team of hiding information.
June 2:
Claire threatens to bypass CFO and contact outside accountant directly.
July 19:
Claire becomes emotional when Celeste questions work-life boundaries.
Every event had happened.
Every description bent it.
I did raise my voice over Celeste entering our townhouse unannounced.
I did challenge finance over records.
I did say I would contact Denise directly.
I did tell Celeste my work-life boundaries were none of her business.
Missing:
Context.
What happened before.
What happened after.
What Aaron did.
The file turned ordinary conflict into a progression.
Concern.
Escalation.
Instability.
Then Rebecca noticed the creation dates.
The April incident summary had been created in June.
The May summary too.
Aaron had reconstructed months of history all at once.
Why June?
That was when he signed the lender certification involving related-party transactions.
He had begun building my instability file at the same time his own disclosure problem became more dangerous.
That connected the narratives.
Still not enough for the full answer.
Then Denise found an email from Aaron.
Subject:
If Claire challenges Palisade.
It was sent to Celeste before I discovered the ownership link.
Before.
That was impossible unless Aaron already knew I was approaching the issue.
He had seen my preliminary vendor-review notes on a shared company dashboard.
Fine.
Nothing wrong with that.
The email said:
If she pushes this, we need to be clear that she's been increasingly volatile and may be misreading routine finance decisions.
There it was.
Before I accused anyone of misconduct, Aaron had prepared to frame disagreement as instability.
Then:
Board won't want a public executive dispute if they think this is personal.
Personal.
Make the professional concern look marital.
Then nobody has to examine the substance.
It was clever.
Not genius.
Just familiar.
Families do it every day.
She's upset because of the marriage.
He's angry because of his mother.
They're fighting.
Ignore the documents.
The six dinner guests mattered because they crossed both worlds.
Family.
Board.
Accountant.
Banker.
Counsel.
If those people saw me “break down” during dinner, every later challenge could be remembered through that image.
My bandaged cheek.
My raised voice.
Broken glass upstairs.
Perhaps wine downstairs.
Celeste's calm concern.
Aaron's exhausted husband routine.
The story almost wrote itself.
Then Lauren found one more file.
A draft statement Aaron had prepared for the lender.
It said:
Recent internal allegations appear to originate from a senior executive currently experiencing significant personal instability unrelated to company operations.
No name.
But obvious.
Me.
The document was dated two days before dinner.
He had not yet sent it.
That mattered.
The plan was still becoming something.
The dinner was supposed to give him permission to finish it.
The next question was:
Why would he go this far over a disclosure issue that might have been corrected with one board meeting?
May you like
The answer appeared in records from a different vendor.
Not Palisade.
Related Stories
