Chapter 5 #2
“Everything. Names, dates, the specific mechanisms of pressure. Everything that shows how systematic this is. Everything that proves it wasn’t isolated incidents—it was infrastructure. Systematic policy.”
“That changes things,” Rogan says. “That makes our case airtight. That’s the difference between showing a pattern and proving a conspiracy.”
The afternoon dissolves into strategy calls and documentation compilation.
The careful work of turning crisis into leverage.
By evening, the gym has gone quiet—Ty has left, Nadia has finished her session, the normal traffic of training has stopped.
But the work continues in my office. Elena Vasquez is calling.
Shay is sending drafts. The coalition is coordinating timing across facilities and media platforms.
This is what it looks like to move from defense to offense. Strategically, not physically. We stop reacting to Apex’s pressure and start creating our own. We stop defending Ground Rule and start using it as the evidence for a larger argument about systemic corruption.
At midnight, I’m still in my office when Bailey knocks on the doorframe. The gym is completely quiet now. The fluorescent lights have been dimmed. It’s just the two of us and the work that still needs to be done.
“You should sleep,” he says. There’s something in his voice that’s shifted—not just coach and fighter anymore, but something more complicated. Something that acknowledges we’re standing together against something larger than either of us.
“I’ll sleep when this is stabilized,” I tell him. But even as I say it, I know that’s not true. There will be another crisis after this one. Another pressure point. Another deadline. Sleep isn’t part of resistance.
“That’s not how it works,” he says. He moves into the office, stands near my desk. “Exhaustion makes you worse at strategy. You need rest. You need to be sharp for what comes next.”
There’s something in his tone that makes me look up from the spreadsheet. Something that suggests this is more than advice—he’s worried about whether I’m going to keep functioning. About whether I’m going to burn out under the weight of what I’m carrying. About whether I’m going to break.
“I can’t afford rest right now,” I tell him.
“Yes, you can,” he says. “Because I’m going to handle the documentation tonight. I’m going to go through everything and organize it the way it needs to be organized. You need to step back and let other people carry some of this weight.”
“That’s not?—”
“This is what it looks like when people choose to stand with you,” he says quietly. “You let them stand. You don’t do everything yourself. You distribute the load. You trust that other people are competent enough to do the work right.”
I want to argue with him. Want to explain that the only way to ensure something gets done right is to do it yourself. Want to detail every reason why trusting other people with critical work is how systems collapse.
But instead, I close the laptop.
“One hour,” I tell him. “I’ll rest for one hour, and then I want to see what you’ve compiled.”
“Fair,” he says.
I go to the cot in my office—the one I’ve been using for nights like this, which have become more frequent as the pressure increases.
The cot that I used when my father was still alive and I was trying to keep his gym running while also trying to distance myself from his corruption.
The cot that knows what exhaustion feels like.
Bailey stays in my office, working through the documentation with a focus and precision that suggests he’s been preparing for exactly this kind of systematic compilation all along.
I watch him for a moment before I lie down—watch the way he organizes the papers, cross-references the names, creates a timeline that makes the systematic nature of Apex’s practices undeniable.
One hour passes. Maybe a little more. When I wake, there are forty-three pages of typed documentation, organized by category, with cross-references and timeline notes and everything structured in a way that makes it immediately clear what Apex did and how they did it and why they did it.
It’s professional. It’s comprehensive. It’s the work of someone who’s been thinking about this for three years.
“That’s good work,” I tell him. I stand up, look at what he’s created. My vision is slightly clearer now. My mind is working faster.
“That’s all of it,” he says. “Everything I’ve been holding back. Everything I was protecting people about. It’s all here now. Names, dates, the mechanisms of pressure. All of it.”
He looks exhausted. The kind of exhaustion that comes from making a decision that can’t be unmade, from crossing a line that changes what comes next, from committing to something that’s going to cost him in ways he doesn’t yet fully understand.
The kind of exhaustion that comes from choosing to be visible instead of invisible.
From choosing to be dangerous instead of safe.
“Go home,” I tell him. “Sleep. Tomorrow we start releasing this. Tomorrow we start the real work.”
He leaves without arguing. I watch him go from my office window, moving through the empty gym toward the exit. His movement is tired but deliberate. He’s carrying the weight of what he’s done, what he’s released, what he’s made visible.
And then I turn back to the documentation he’s compiled and start reading through what we’re going to release to the world.
What we’re going to use to apply pressure on Apex.
What he’s just given us to make the case airtight.
Everything that was hidden is about to become visible.
Everything that was secret is about to become public.
Brennan’s pressure campaign is about to meet resistance.