Chapter 10 - THE DINNER WAS A TRAP
Thomas saw me looking at his shoes.
For the first time since I had known him, he looked away first.
That was not proof.
But it was enough to change the air between us.
He approached slowly.
“I came as soon as I heard.”
“Did you?”
His eyebrows lifted.
“Meaning?”
“Nothing.”
Miriam stepped beside me.
Thomas looked at her and smiled politely.
“Counsel.”
“Mr. Reed.”
The fire marshal asked everyone except essential staff to leave the hallway.
Thomas complied without argument.
That almost made him more frightening.
He never pushed when patience could get him farther.
I watched him walk away.
Charcoal trousers.
Black oxfords.
A silhouette that could match the figure inside my study closet.
At 4:30 p.m., the board convened again by phone.
Paul Greene called the fire “another indicator of operational instability.”
I wanted to reach through the speaker and shake him.
Instead, I asked the fire marshal to summarize what was known.
The origin was suspicious.
No electrical source had been found.
No employee had authorization to enter the room during the relevant period.
The access system showed one badge entry at 1:47 p.m.
The badge belonged to David Wells.
David had supposedly disappeared.
His badge had supposedly been deactivated that morning.
“How can a disabled badge open a door?” Thomas asked calmly.
Our security director answered.
“It cannot.”
“So either your system is wrong,” Thomas said, “or someone failed to disable it.”
Helen responded.
“Or someone cloned the credential.”
Thomas was silent.
I was not.
“Who had administrative access to the badge system?”
The security director listed three names.
His own.
Helen’s.
And Daniel’s.
A former COO retained emergency credentials for facilities access until his termination was fully processed.
The vote removing Daniel had occurred minutes before the suspicious login attempts.
The badge revocation had been queued but not completed until later.
Daniel had had a narrow window.
Another ten minutes.
The number kept returning.
After the meeting, I asked our cyber team to reconstruct Daniel’s actions from the evening of the dinner minute by minute.
They worked through device logs, home network traffic, cloud access attempts, building systems, and old credentials.
At 7:51 p.m., my home network registered a new device.
At 7:58, that device accessed an archived company credential package.
At 8:03, the false hotel reservation was confirmed.
At 8:09, an anonymous tip was submitted to police.
At 8:14, Daniel’s office laptop attempted to reach an old company server.
At 8:17, my home security camera showed Daniel entering the dining room with the soup.
At 8:18, according to my memory, he poured it over my head.
At 8:19, he gave me ten minutes to leave.
The sequence destroyed any remaining illusion that the dinner had become violent spontaneously.
The trap was already active before the bowl left his hands.
He needed me emotionally shocked.
He needed me to leave quickly.
He needed police to believe I was fleeing after destroying records.
And he needed access to my study.
“What was the new device on my network?” I asked.
The analyst enlarged a hardware signature.
“A small single-board computer.”
“Something hidden?”
“Likely.”
“Where?”
“We cannot tell from network logs.”
I called the officer who had accompanied me and asked whether police could return while I searched the house.
Two hours later, with consent documented and Miriam beside me, we went room by room.
The device was under the sideboard in the dining room.
A black box smaller than my palm had been taped beneath the wood.
It was connected to a power adapter running behind a cabinet.
The officer photographed it before removal.
I stared at the exact place.
Three feet from the chair where I had sat while Daniel poured soup on me.
“How long has it been there?” I asked.
The cyber technician examined dust and cable placement.
“Hard to know.”
“Days?”
“Possibly weeks.”
The dinner had not merely been a confrontation.
It had been staged beside equipment installed in advance.
I walked into the kitchen.
The clock above the doorway still showed the correct time.
I remembered checking it again and again.
Daniel had encouraged me to do that.
“Nine minutes.”
He had wanted the time remembered.
Why?
Miriam saw my expression.
“What?”
“He kept counting.”
“You told me.”
“No.”
“He wanted me to notice the countdown.”
“Why would that matter?”
I looked at the kitchen clock.
“To establish a timeline.”
Miriam frowned.
I continued.
“If police asked when I left, I would remember precisely.”
There was a brief lull in the dining room again, and the quiet made the hidden network device feel louder than any accusation.
I kept circling the same question: why Daniel insisted on exactly ten minutes.
One fact kept pulling me back: the forged upload landed at 8:29.
I opened a notebook and drew a line down the center of the page.
On the left I wrote what I knew.
On the right I wrote what I only suspected.
The second column was much longer.
That embarrassed me at first.
Then I realized the distinction was exactly what Daniel and Thomas never made when it benefited them.
They treated assumptions as truth when assumptions created leverage.
I could not fight that by becoming equally careless.
Helen added timestamps from the system logs.
Miriam added questions that would survive cross-examination.
Martin added money trails that did not care who felt offended by them.
Slowly, suspicion became a map instead of a fog.
The map pointed toward one lesson: the countdown had been part of the frame.
I underlined that sentence twice.
It was not inspirational.
It was operational.
And I needed operational truths more than comforting ones.
“If cameras showed me leaving at 8:29, then someone could claim anything happening after 8:29 was done remotely by me.”
“Or anything before 8:29 happened while you were still here.”
“Yes.”
We both turned toward the dining room.
The hidden device had been active before the confrontation.
Someone wanted digital activity tied to my house while I was physically present.
A perfect frame.
My phone rang.
Daniel.
This time I answered.
“Hello.”
His voice was rough.
“You went back to the house.”
“How do you know?”
Silence.
I smiled without humor.
“Thank you.”
“For what?”
“For answering the question.”
“Claire, stop playing games.”
“You installed a device under the dining room sideboard.”
“I don’t know what you’re talking about.”
“You made a hotel reservation before dinner.”
“No.”
“You filed an anonymous police tip.”
“No.”
“You stole my backup drive.”
“No.”
His denials became faster each time.
Then I asked the question I had been saving.
“Why did you need exactly ten minutes?”
He stopped breathing.
That silence was different from every other silence.
I knew I had touched the center of something.
“Daniel?”
“I was angry.”
“No.”
“You said the first number that came into your head.”
“No.”
“Stop saying no like that proves anything.”
“You needed ten minutes because something was scheduled.”
His voice dropped.
“You have no idea what you’re accusing me of.”
“Then tell me what happened at 8:29.”
The line went quiet.
At that exact moment, Helen called on my second line.
I put Daniel on hold and answered her.
“We found something in the server log,” she said.
“What time?”
“8:29 p.m. exactly.”
My skin prickled.
“What happened?”
“A package of files was uploaded using your credentials.”
“Which files?”
Helen hesitated.
“Documents showing that you authorized the Archer Ridge loan.”
I looked toward the clock.
At 8:29, my ten minutes had expired.
At 8:29, forged evidence appeared inside the company system.
Daniel had built the dinner around that minute.
He had wanted witnesses to remember I was home when the upload happened.
He had wanted me to walk out immediately afterward and look like I was fleeing.
I switched back to Daniel.
He was still there.
“8:29,” I said.
He said nothing.
“The files uploaded at 8:29.”
Still nothing.
“You did not throw me out because you lost your temper.”
My voice became very quiet.
“You threw me out because the frame was complete.”
Daniel whispered one sentence.
“You were never supposed to find Rebecca.”
May you like
Then he hung up.
