Chapter 9 - WHAT VANESSA WAS AFRAID OF

Vanessa finally agreed to a family meeting.
Not at the house.
Neutral office.
Lawyers nearby.
No Rachel if Rachel did not want to attend.
Rachel attended.
She wanted answers more than distance that day.
Daniel asked one question first.
“Who created the broad POA?”
Vanessa answered:
“I don't know.”
Nobody believed her.
Then she produced an email.
Seven months earlier.
From Richard Carter's former estate attorney, Henry Walsh.
Subject:
Deployment Continuity / Daniel Authority
Attachment:
The broad POA.
Henry wrote:
Vanessa — found this in Richard's continuity archive. May solve the Westbridge consent issue if still effective. Verify with current counsel.
Vanessa had not invented the file from nothing.
Daniel stared.
“My father died three years ago.”
“Yes.”
“How does Dad have a POA I supposedly signed this year?”
Vanessa looked embarrassed.
“I thought Richard had kept a template.”
“A template with my real signature?”
“That part I did not understand.”
“Did you ask?”
“Eventually.”
“When?”
“After the bank raised it.”
Months later.
There.
Henry Walsh was interviewed.
He was seventy.
Semi-retired.
He had searched Richard Carter's old digital archive after Vanessa asked for “anything Daniel signed about deployment authority.”
The archive contained dozens of scanned family documents because Richard had managed Daniel's affairs during Daniel's earlier assignments.
Henry found a folder labeled:
DANIEL / DEPLOYMENT CONTINUITY
Inside:
Daniel's current signature page.
How did it get into Richard's archive three years after Richard died?
It didn't.
The archive itself had been migrated into Carter Ridge's current document vault.
Someone added files later.
The folder name was old.
The contents were not all old.
Henry assumed they were.
Bad assumption.
He sent the file.
Then warned:
Verify with current counsel.
Vanessa skipped that part until closing.
Specific responsibility.
Then the document-vault audit found the uploader.
User account:
VCARTER-EXEC
Vanessa's executive-office account.
Vanessa stared.
“I did not upload it.”
Her assistant could use the account.
So could CFO Lucas in emergencies.
Three executive administrators knew the password because Carter Ridge had never completed individual access migration after Richard died.
Terrible controls.
Convenient ambiguity.
Then the metadata.
The broad Schedule B had been created from a Word document originally authored by:
RCarter
Daniel's late father.
Created eleven years earlier.
Modified seven months ago.
That changed everything.
The broad language was old.
Richard Carter had drafted a sweeping deployment authority form for Daniel years ago.
Maybe Daniel signed an earlier version.
Maybe not.
Someone had taken that old Schedule B—
and attached Daniel's current signature page.
Daniel looked at Vanessa.
“You recognized Dad's language.”
She did not answer immediately.
“Yes.”
Rachel stared.
“When?”
“When Henry sent it.”
“So you knew it wasn't Daniel's current schedule.”
Vanessa's eyes hardened.
“I knew Richard used similar language.”
“That's not the same.”
“No.”
There.
Vanessa had not created the Frankenstein document.
But she had recognized its family origin and chosen not to look too closely.
Why?
Because it gave her the authority she needed.
Then she said the thing Daniel did not expect.
“Your father used that authority before.”
Daniel frowned.
“When?”
“Your first Afghanistan rotation.”
He was twenty-six.
Not married.
His father had handled everything.
“What did he sign?”
Vanessa looked toward the window.
“A loan.”
Daniel stared.
“For Carter Ridge?”
“Yes.”
“With my authority?”
“Yes.”
“Did I approve it?”
Vanessa answered:
May you like
“I don't know.”
That was the first moment Daniel realized the current POA might not be the beginning of the family pattern.