Chapter 4 - Eight Hundred Dollars and a Threat
I stared at Richard Vale’s signature until the image blurred.
Rachel noticed immediately.
“Don’t assume anything.”
“It’s his signature.”
“It looks like his signature.”
“What’s the difference?”
“In litigation? Everything.”
We stepped outside Halcyon headquarters.
The morning air felt colder than when we entered.
Cars moved through downtown traffic.
People passed us carrying coffee, staring at phones, living completely ordinary lives.
Meanwhile, a company worth billions appeared to be unraveling behind forty-two floors of mirrored glass.
Rachel called Nora.
No answer.
She tried again.
Voicemail.
“Send nothing else,” Rachel texted. “Preserve what you have.”
Then she turned to me.
“We need to slow down.”
“Luis has already been fired.”
“I know.”
“Nora is on leave.”
“I know.”
“And Richard’s signature is on the change request.”
“Which is why we slow down.”
I hated when attorneys were right.
The document might mean Richard approved the entire deployment.
Or it might mean his approval was copied from a broader migration package.
Or forged.
Or attached automatically.
Technical systems create context.
Context creates truth.
A screenshot creates assumptions.
We needed the first two.
By noon, Rachel had filed a formal demand for payment.
Seven calendar days.
$800,000 plus applicable contractual fees.
The letter contained no mention of Atlas’s root cause.
That separation mattered.
We would not connect the debt to silence.
We would not give Martin even a weak argument that I was leveraging internal evidence for payment.
At 2:18, Halcyon replied.
Not Richard.
Not Martin.
Charles Denton.
The company disputed the amount and reserved all rights regarding “potential unauthorized possession of confidential materials.”
Rachel smiled when she read it.
“They’re scared.”
“How can you tell?”
“They’re threatening confidentiality before answering the contract.”
My phone rang twenty minutes later.
Martin.
Rachel shook her head.
“Don’t answer.”
It rang again.
Then again.
Then a voicemail appeared.
I played it on speaker.
Martin’s voice was low.
“Ethan, this is getting stupid. Call me before you turn a business disagreement into something you can’t undo.”
Rachel raised an eyebrow.
“He should really stop talking.”
At 4:07, another voicemail came.
This one was different.
“I can make this easy. You sign a revised settlement. We wire fifty thousand. Everybody moves on.”
Fifty thousand.
For an $800,000 contract.
I deleted nothing.
At 5:30, I drove home.
I lived alone in a modest house outside the city, the kind of place with too many books, too many hard drives, and a kitchen I rarely used properly.
My daughter, Sophie, was in college two states away.
Her mother and I had divorced years earlier, peacefully enough that we could still sit through graduation dinners without pretending.
Sophie called while I was reheating soup.
“How’d the rich people do?”
I laughed.
“You’ve been talking to your mother.”
“She said you were fighting a giant corporation.”
“I’m not fighting anyone.”
“Dad.”
“What?”
“You archive grocery receipts.”
“That is responsible.”
“You archive takeout menus.”
“Menus change.”
She laughed.
Then her voice softened.
“You okay?”
“I’m fine.”
“Actually?”
I looked toward my home office.
Three encrypted backup drives sat inside a fireproof cabinet.
“Actually.”
That night, at 11:42, my home internet went down.
I noticed because one of my monitoring screens lost connection.
At first I assumed the provider was doing maintenance.
Then my backup cellular router activated.
Thirty seconds later, someone attempted to log into my cloud archive.
Invalid credential.
Another attempt.
Then another.
Different addresses.
Same target.
I stood slowly.
This wasn’t random.
The cloud account wasn’t publicly associated with my consulting work.
Only a handful of people knew it existed.
I disconnected the system.
Pulled the network cable.
Then called Rachel.
She answered sleepily.
“What happened?”
“Someone’s trying to access my archive.”
She was awake instantly.
“Can you prove it?”
“I have logs.”
“Do not touch anything else. Call your cybersecurity contact.”
I had one.
Maya Chen.
Former incident-response lead.
The kind of person who could look at a packet capture and tell you whether the attacker drank coffee.
She arrived remotely within twenty minutes.
By 1:10 a.m., we knew three things.
First, the attempts were deliberate.
Second, whoever was doing it knew the account identifier.
Third, the attacker had old credential information that had never been made public.
“How old?” I asked.
“Maybe six months.”
I thought.
Then remembered.
During Halcyon onboarding, I had submitted a vendor-security questionnaire.
It included my backup provider.
Not passwords.
But account architecture.
Maya went quiet.
“Who had access to that questionnaire?”
“Halcyon vendor management.”
“And finance?”
“Probably.”
She sighed.
“Don’t accuse anyone yet.”
Everyone kept telling me that.
At 1:36, my phone lit up.
A text from Martin.
You should have taken the fifty.
I felt something cold move through me.
I screenshotted it.
Forwarded it to Rachel.
She called immediately.
“Police report.”
“For a text?”
“For the intrusion attempts and the text together. You do not need to accuse Martin. You document the timeline.”
By sunrise, everything had changed.
This was no longer simply a contract dispute.
Someone had attempted to access evidence.
At 8:02, Richard Vale called.
I answered because Rachel was already on the line.
Richard sounded exhausted.
“I need to ask you something.”
“Go ahead.”
“Did Martin contact you last night?”
“Yes.”
“What did he say?”
Rachel interrupted.
“Mr. Vale, if you’re calling in your capacity as Halcyon’s CEO, this conversation needs counsel.”
“I’m calling because Martin was suspended this morning.”
I stopped.
Richard continued.
“Our audit committee reviewed preliminary records overnight.”
“What did they find?”
“I can’t discuss that.”
“Then why call?”
“Because Martin’s office computer was remotely wiped at 3:11 a.m.”
Nobody spoke.
Richard said, “And before it was wiped, someone transferred a large archive from Halcyon’s legal hold server.”
Rachel asked, “Whose credentials?”
Richard hesitated.
Then answered.
“Mine.”
There it was again.
Richard Vale’s name.
First on the deployment approval.
Now on a stolen archive transfer.
Either the CEO of Halcyon was far more involved than he claimed—
or somebody had spent months making sure every road eventually pointed toward him.
And if that was true, the Atlas crash might not have been reckless incompetence.
May you like
It might have been something much worse.
---
