Chapter 3 - PATRICK

Patrick Reeve was not a spy.
At least not in the cinematic sense.
He was a businessman with debt.
Three tow trucks.
Two failed contracts.
A gambling problem.
Then someone offered money for information.
Vehicle registrations.
Warehouse access patterns.
Delivery schedules.
He told himself none of it was dangerous.
No troop movements.
No weapon specifications.
Just logistics.
That distinction collapsed quickly.
The unknown contact paid through gift cards, cash deposits, and fake consulting invoices.
Patrick used Carl’s database access because he did not have his own.
Did Carl know why?
At first, no.
Then later?
Maybe.
Investigators found texts.
Patrick:
Need another plate. Same warehouse.
Carl:
You’re wearing me out.
Patrick:
Dinner on me.
Carl:
Make it steak.
That looked stupid, not criminal.
Then a later exchange.
Carl:
Why are these all federal contractor vehicles?
Patrick:
Government auction stuff.
Carl:
Better not be anything stupid.
Patrick:
Relax.
There.
Carl suspected.
Then kept helping.
That mattered.
Then the unknown contact.
Name eventually traced through burner accounts:
Victor Hale.
Senior compliance manager at Meridian Strategic Logistics.
Defense subcontractor.
He had access to non-public routing schedules.
Not top secret.
Still sensitive.
Victor sold slices of information to organized cargo thieves.
Not foreign intelligence.
That surprised everyone.
The breach was about theft.
High-value electronics.
Specialized components.
Medical supplies.
Then the network stumbled into military shipments.
Victor kept selling.
That escalated.
Then my name.
Why “general”?
Because one shipment review bore my command approval.
Victor knew my rank.
Patrick did not.
Carl did not.
Then the phrase:
Mercer route still clean.
They were discussing a convoy oversight plan my office had changed.
That meant someone had access to current routing.
Victor.
Probably.
Then why was I on a secure call at Mom’s house?
Because the logistics anomaly had triggered an emergency review while I was visiting.
Nothing dramatic.
Work followed me home.
Then Carl entered.
Why?
He had heard my name on Patrick’s voicemail earlier that week.
Mercer.
Then heard me discussing route changes.
He connected nothing accurately.
But enough paranoia formed.
He thought I was investigating him.
So he confronted me.
There.
The assault came from fear.
Not random anger alone.
Then one deleted text from Carl:
If Claire is mixed up in this, I’m handling it myself.
Patrick:
Leave her alone.
Carl:
She’s family.
That sentence turned my stomach.
Family as jurisdiction.
Then my mother learned.
She cried.
“Why didn’t he tell me?”
I almost said:
Because men like Carl think information becomes theirs if it enters the house.
Then stopped.
Too easy.
Carl was not a type.
He was responsible for himself.
Then local prosecutors filed charges related to assault, unlawful restraint, firearm misuse, and database abuse.
Federal investigation continued separately.
No treason charge.
No espionage charge.
Good.
Facts.
Then Carl asked to speak to me.
I refused.
Not yet.
Then Mom asked:
“Do you want me to leave him?”
I said:
“That is your decision.”
She stared.
Maybe she wanted permission.
Maybe instruction.
I would not give either.
Then another surprise.
Patrick had once tried to warn Carl away from the network.
A message:
Vic’s dirty. Stop helping me pull plates.
Carl replied:
Too late now.
That meant Carl knew more than he claimed.
The question became:
How much?
Patrick’s cooperation revealed how ordinary the network looked before it became serious. Nobody began by saying, “Let’s compromise military logistics.” It began with one plate lookup for a vehicle outside a warehouse.
Then another.
Then a delivery schedule.
Then a gate code.
Each request felt only slightly worse than the last.
By the time Victor realized the information could affect protected shipments, he was already making enough money to rationalize continuing.
That incremental pattern became central to later training. Catastrophic breaches often grow from permissions nobody reevaluates.
Victor’s payment structure also exposed how easy it is to hide wrongdoing inside normal contractor relationships. Some invoices were legitimate. Some covered stolen information. The same vendor name appeared in both categories.
That ambiguity protected him for months.
May you like
Auditors later told me the hardest part was not finding suspicious transactions. It was proving which ordinary-looking transaction represented an extraordinary breach.
That became another lesson I carried into command: systems fail when familiarity turns scrutiny off.