Chapter 34
CHAPTER THIRTY-FOUR
Cody
People misunderstand what pressure does.
They think it creates mistakes. Most of the time, it doesn’t. Pressure reveals structure.
A careless person collapses beneath it. A disciplined person adapts. And a dangerous person prepares for it long before it arrives.
Which is why, sitting across from Jake Dorsey in the operations office at 8:17 in the morning, I already know I’m not dealing with someone careless.
The office smells faintly of coffee, printer toner, and damp earth tracked in from the yard outside. Jake sits behind his desk with one boot hooked beneath the opposite knee, posture loose enough to read relaxed if you aren’t paying attention properly.
I am.
His shoulders are controlled, his breathing calm, his hands still.
Too still.
Most people move when questioned. Tiny adjustments, defensive body language, nervous displacement.
Jake has the look of a man discussing weather forecasts, which means he anticipated this conversation.
“I’m just tightening operational reviews after yesterday,” I say evenly, sliding a folder across his desk. “Routine audit.”
Jake glances at the paperwork without urgency. “That because of the gate situation?”
“That,” I say, “and vendor inconsistencies.”
His eyes flick upward toward the ceiling briefly. “Anything specific?”
I adjust my watch once before answering. “We’ve identified some irregular approvals tied to vendor access routing.”
Jake leans back in his chair. “That so.”
No surprise or confusion. Not even irritation.
Interesting.
I open the folder, turning it toward him. “Northline Agricultural Solutions.”
He scans the page for exactly the amount of time required to appear cooperative. Then he shrugs. “Looks familiar.”
“Approved through your credentials.”
“So are half the vendors on this ranch.” His tone stays calm. Easy. “Operations runs through me.”
“That doesn’t concern you?”
Jake’s mouth twitches at one corner. “With all due respect, Cody, you’re asking about paperwork while we’ve got somebody cutting gates open in the middle of the night.”
“Unlatching,” I correct automatically. “Not cutting.”
“Right,” he says smoothly. “Unlatching.”
Silence stretches briefly between us.
I let it sit.
People rush to fill silence because they mistake stillness for weakness. But silence is useful. It allows pressure to settle naturally without interference.
Jake doesn’t rush.
I tap the paperwork once. “These payment structures mirror previous flagged vendors.”
“Then maybe your system has a problem.”
The wording lands precisely where he intends it to. Subtle enough to remain deniable.
I hold his gaze evenly. “My system doesn’t create reroutes requiring administrative authorization.”
“Then maybe somebody used the wrong credentials,” he says.
Possible.
Technically.
But his confidence is the problem.
He doesn’t sound concerned about unauthorized access. He sounds certain the explanation already exists.
That certainty settles heavily in my stomach. Because innocent people ask questions when systems fail.
I close the folder carefully, aligning the edges before standing. “Well, if anything occurs to you regarding vendor routing anomalies, let me know.”
Jake nods once. “Sure thing.”
Then he smiles, looking certain I can’t touch him. Which means one of two things is true:
Either Jake knows nothing, or he knows exactly how protected he is.
By noon, I’ve reviewed four years of operational transfers.
By 2:00, I’ve isolated every vendor approval tied to the flagged routing structures Annie identified.
By 4:00, I’ve stopped drinking coffee because my hands are already vibrating hard enough without chemical assistance.
The office around me disappears after a certain point.
That always happens eventually. The world narrows into patterns, data, and architecture.
Most people think accounting is numbers. It isn’t.
It’s behavior.
Systems reflect the people who built them. Every financial structure carries fingerprints whether the creator intended it or not. Habits, preferences, priorities, fear.
This system is intelligent, careful, and adaptive, which makes it personal.
I pull another query across the screen, isolating layered transfer paths between vendor accounts and deferred operating allocations.
Nothing obvious appears.
Again.
Because whoever built this understood scrutiny from the beginning.
They didn’t hide money randomly. They distributed it across operational noise. Shipment spikes. Seasonal increases. Emergency supply reallocations.
Normal fluctuations large enough to absorb fractional disappearances without triggering alarms.
Professional.
I hate admitting that.
My eyes burn from staring at spreadsheets, but I keep going anyway, refining queries tighter and tighter until the data begins collapsing inward on itself.
And then…
There.
I stop moving entirely.
The reroute sits buried beneath three authorization layers tied to livestock insurance reallocations.
At first glance, it looks clean, legitimate, boring, which is exactly why it almost works.
Almost.
I zoom further into the permissions structure. Then further, and a cold twists hard beneath my ribs.
Administrative override required. Admin level rerouting permissions.
My pulse slows instead of quickening.
That’s always how it happens. The worse the information becomes, the calmer I get.
I pull the permissions tree immediately.
Only four people at Ironwood possess that level of authorization. Silas. Me. Sherry. Jake.
I stare at the names longer than necessary.
Before now, there were variables. External interference. Credential manipulation. Layered access exploitation.
Now?
The circle narrows.
I remove myself first.
My credentials weren’t active during the reroute window. I know that before checking because I was physically with Annie reviewing vendor structures during the relevant timestamp.
Still, I verify it anyway. Verification matters more than assumption.
My login records align perfectly.
Fine.
Next: Silas.
I pull operational movement logs against authorization timestamps. Again, consistency. Mostly.
But Silas delegates portions of administrative processing more than I do. Ranch operations force him outward physically. Meetings, land issues, vendor disputes, which creates exposure.
I lean back slowly, removing my glasses and pressing two fingers against the bridge of my nose.
Sherry.
My stomach tightens unpleasantly, because Sherry has access to everything. Payroll, scheduling, administrative pathways.
And more importantly, everyone trusts her. She’s been here for years. Long enough that her presence stopped registering as separate from the structure itself, which suddenly feels less comforting than it used to.
Then there’s Jake.
I replay the conversation from this morning automatically, dissecting tone and phrasing the same way I dissect financial patterns.
Maybe your system has a problem.
He wanted the flaw to appear structural instead of personal, which means he understands exactly where the vulnerability exists.
My jaw tightens. I stand abruptly, pacing once across the office before stopping beside the window overlooking the ranch.
Outside, Ironwood looks normal.
That’s the disturbing part.
Ranch hands moving through paddocks, trucks crossing the gravel roads, horses shifting calmly beneath the fading afternoon light.
Structure. Routine. Trust.
All the things systems require to function.
And somewhere inside all of it someone is bleeding the ranch slowly enough to survive detection.
Not a stranger or some faceless outsider hacking into accounts from another state. Someone here, inside our walls. Someone who understands Ironwood intimately enough to weaponize its trust against itself.
Someone I’ve trusted.