Chapter 6 - They Tried to Erase Me
The lawsuit was filed Friday morning.
Not mine.
Halcyon’s.
At 8:06 a.m., Rachel called.
“They sued you.”
I sat up in bed.
“For what?”
“Breach of confidentiality. Misappropriation of proprietary information. Computer access violations.”
I actually laughed.
“Computer access violations?”
“They’re alleging you exceeded your authorized access during the recovery.”
“That’s absurd.”
“Yes.”
“Who authorized the filing?”
“Guess.”
“Martin?”
“No.”
That stopped me.
Rachel continued.
“The complaint was prepared before Martin’s suspension.”
Meaning the machinery had already been moving.
A corporation does not draft a fifty-page lawsuit overnight.
Martin had anticipated resistance.
He expected me not to accept the $800.
He had prepared to destroy my credibility if I fought back.
The complaint painted me as an opportunistic freelancer who had exploited a crisis, copied sensitive information, then demanded excessive compensation.
It did not mention the signed $800,000 agreement in the opening summary.
That omission was almost impressive.
By noon, a technology-news site had the story.
HEADLINE:
HALCYON DYNAMICS ACCUSES CONTRACTOR OF DATA MISUSE AFTER ATLAS INCIDENT.
Someone had leaked the lawsuit immediately.
My name spread across social media.
People who knew nothing about me suddenly had theories.
Some called me a hacker.
Others called me a scammer.
One anonymous account claimed I had deliberately created the Atlas failure so Halcyon would hire me to fix it.
Sophie called from college furious.
“Can I respond to these people?”
“No.”
“They’re lying about you.”
“I know.”
“One guy says you live in a mansion.”
I looked around my kitchen.
The cabinet above my sink didn’t close properly.
“That one hurts most.”
She didn’t laugh.
“Dad.”
“I’m okay.”
“You keep saying that.”
“Because I am.”
But that night, I wasn’t completely sure.
Reputation is strange.
You spend twenty years building it quietly.
Then one headline turns you into a stranger.
Two clients paused upcoming projects.
One canceled entirely.
A former colleague sent a one-line message.
Saw the news. Hope there’s another side.
There was.
But legal disputes move slower than rumors.
Rachel filed our response Monday.
And our counterclaim.
Breach of contract.
$800,000.
Fees.
Interest.
Declaratory relief regarding authorized data retention.
Then she attached Exhibit A.
The contract.
The actual contract.
The one Halcyon’s public narrative had avoided discussing.
Payment: $800,000.
Upon verified restoration.
Verified restoration: acknowledged in writing by CEO Richard Vale.
Exhibit B.
Richard’s email after Atlas returned.
Ethan, extraordinary work. Atlas is fully operational across all six sites.
Exhibit C.
Martin’s message.
Worth every penny.
The story changed within hours.
Not completely.
But enough.
One financial reporter wrote:
Whatever the cybersecurity dispute, Halcyon appears to face a straightforward question: why did it sign an $800,000 success agreement and pay $800?
That question spread.
Then another.
Why was Halcyon attacking the person who restored Atlas?
By Tuesday, the board took an unusual step.
It announced publicly that the lawsuit had been initiated by management before completion of the board’s independent investigation.
Translation:
Don’t blame us yet.
Martin’s attorney released a statement denying wrongdoing.
He claimed the payment dispute reflected “contractual ambiguity.”
There was none.
But facts rarely stop a press release.
Then Luis Ortega contacted me.
Not directly.
Through his attorney.
Luis wanted to speak.
Rachel agreed.
We met at her office.
He looked younger than I expected.
Twenty-eight.
Thin.
Tired.
He wore a cheap gray suit and held himself like someone waiting to be blamed again.
“I ran the deployment,” he said.
“I know.”
“I should have refused.”
“You had an approved change ticket.”
“I knew staging failed.”
“Did you object?”
“Yes.”
“Documented?”
“Yes.”
“Then why do you think this is your fault?”
He stared at his hands.
“Because I pressed Enter.”
I had seen that guilt before.
People confuse proximity with responsibility.
Machines make consequences immediate.
Executives make decisions abstract.
The keyboard remembers who executed the command.
It does not remember who created the pressure.
Luis opened his laptop.
“I kept something.”
Rachel immediately asked, “Legally?”
“My attorney reviewed it.”
Good answer.
He showed us a meeting transcript.
Halcyon used automated transcription for internal operational calls.
The meeting occurred six hours before deployment.
Participants included Martin Keene, Daniel Ross, Nora Bennett, Luis, and two security engineers.
Nora said:
The patch will break Atlas authentication under current trust configuration.
Martin responded:
You don’t know that.
Nora:
We reproduced it twice.
Martin:
Then fix it after deployment.
Luis spoke next:
We should delay.
Martin answered:
If anyone on this call refuses an authorized change, I will treat it as insubordination.
The transcript continued.
Then came the line that explained everything.
Daniel Ross asked:
And if Atlas goes down?
Martin replied:
Then we call someone who can fix it.
The room in Rachel’s office went silent.
Martin knew Atlas might fail.
He proceeded anyway.
Not because he believed the risk was small.
Because he believed the consequences could be repaired.
By someone like me.
Then he tried not to pay the repair bill because payment would expose the reason it existed.
Luis looked at me.
“There’s more.”
He opened another file.
An internal budget presentation.
One slide showed the vendor consolidation savings.
$14.2 million annualized.
Underneath, a note:
Executive incentive threshold achieved if recognized this quarter.
Rachel leaned forward.
“Whose incentive?”
Luis changed slides.
CFO Performance Compensation.
Martin Keene.
Projected bonus increase:
$3.6 million.
There it was.
Atlas had nearly collapsed because Martin wanted the savings booked before quarter close.
And the difference might have been worth $3.6 million to him personally.
Suddenly, the $300 million crisis had a motive.
But as we stared at the slide, Luis said something that made the room colder.
“Martin wasn’t the only executive whose bonus depended on that number.”
He clicked again.
Five names appeared.
May you like
And one of them belonged to CEO Richard Vale.
---
