He moves off to coordinate with the rest of the team, leaving me alone with Sarah in the operations center. She's already building a database of external contacts and their interaction patterns with Echo Ridge, communication logs scrolling across her screens.
I cross to her workstation and settle against the desk beside her. Close enough to see her screens, far enough to give her working space—an old habit from when we used to do this regularly, before I left for deep cover and broke everything we'd built.
"Where do you want to start?" I ask.
Sarah displays a network diagram. "Identify critical nodes. Contacts we absolutely cannot afford to lose versus those we can potentially isolate or replace. Then we build new protocols around the critical nodes first."
"Makes sense. How many critical contacts are we talking about?"
"Maybe a dozen. Cross is one. The logistics network that supplies Echo Base is another. Intelligence contacts in federal law enforcement that warn us about Committee movements." She highlights nodes as she talks. "Lose any of these and we lose operational capability."
I study the diagram, running threat assessments on each node. "The logistics network is the most vulnerable. They know delivery schedules, equipment specifications, supply volumes. That's enough data for the Committee to build a profile of our operational capacity."
"Agreed." Sarah switches to a different view showing communication patterns. "They're also the most frequent contact point. Weekly deliveries, monthly supply requisitions. Every interaction is a potential compromise."
"So we compartmentalize within the logistics network itself," I say, thinking through the operational security implications."Instead of one contact who knows our full supply chain, we split it across multiple contractors. None of them sees the complete picture."
"That increases complexity but reduces exposure." Sarah starts building a new architecture on her secondary screen. "We'll need cover stories for why we're suddenly changing procurement patterns."
"Business expansion, new security protocols, corporate restructuring—the logistics contractors won't question it if we make it sound like normal business evolution."
"What about the intelligence contacts?"
"Different problem. They're providing us information, not receiving deliveries. We need them to keep feeding us Committee movement data without knowing why we need it or how we're using it." I access my tablet, opening notes from my time deep cover. "I've got contacts from my CIA days. People who owe me favors or who I can leverage for intelligence sharing. We bring them online as supplementary sources, reduce our dependence on any single contact."
Sarah glances at me. "You trust them?"
"I trust that they'll act in their own self-interest. Which means I can predict their behavior and plan accordingly." I meet her eyes. "Trust is complicated. But operational reliability? That I can work with."
Her expression shifts—understanding dawning, recognition that I'm not the person who left two years ago settling in. The work I did while deep cover changed me in ways I'm still processing.
"Okay," she says. "We layer your contacts into the network as redundancy. That gives us options if primary sources are compromised."
We work in silence for a while, building frameworks and testing protocols. Sarah handles the technical architecture whileI run security assessments on each proposed change. It's the same partnership we had before, the rhythm of working together settling back into place like muscle memory.
The operations center stays quiet around us with only the hum of servers, soft clicks of our keyboards and the occasional beep from Tommy's security feeds in the corner.
Except it's not the same—not exactly.
Because now I'm hyperaware of her presence in ways that have nothing to do with professional collaboration. The way she bites her lower lip when she's concentrating. How her hair falls forward when she hunches over her keyboard. The faint scent of her shampoo mixing with the coffee someone left on the desk.
The memory of what we did in the analysis room a few hours ago sits between us like heat shimmer—unacknowledged but impossible to ignore.
Sarah accesses a new set of intercepts. "Committee's SIGINT operation is sophisticated. They're using frequency-hopping spread spectrum to avoid detection. Military-grade encryption on their own communications while they're cracking ours."
"Which means they have serious technical capability backing this operation," I say. "Not just Reeve's field team. There's a whole infrastructure supporting the intelligence gathering."
"Cross's data includes equipment manifests." Sarah highlights specific entries. "Mobile SIGINT stations. Portable satellite uplinks. Advanced decryption hardware. They've invested significant resources in this operation."
"Because they're desperate to find Echo Ridge." I study the equipment list, mentally cataloging vulnerabilities. "Morrison's death left them exposed. Webb is still trying to consolidate power, but he needs to eliminate threats. We're at the top of that list."
"So taking down Reeve isn't just about protecting Echo Base's location," Sarah says. "It's about disrupting the Committee's entire intelligence operation against us."
"Exactly. We eliminate Reeve and destroy his SIGINT capability, the Committee loses months of collected intelligence and has to rebuild their entire approach to hunting us."
Sarah sits back in her chair. "That buys us time. Maybe enough to get ahead of them instead of constantly reacting to their moves."
"Which is why the network restructure matters so much." I gesture to her screens. "We close the leak, eliminate their current intelligence gathering, and force them to start over with no foundation to build on."
