Chapter 14
MICAH
We sit in silence for a moment, the weight of Sarah's messages hanging between us. Everything's broken, everything I can't fix. But the investigation won't wait for us to process two years of grief and anger.
Sarah accesses the new images, scanning through overhead surveillance of Reeve's movements. "This is from yesterday. Kalispell again, different location."
The image shows Reeve outside a storage facility, meeting someone in the parking lot. The second figure is partially obscured by a vehicle, but the body language screams familiar interaction rather than first contact.
"Can you get a better angle?" I lean closer, trying to identify the person through limited visual information.
Sarah adjusts the satellite imagery, calling up a second pass from different orbital positioning. The new angle reveals the man's face clearly, and recognition hits like a physical impact.
"That's Davis." My voice goes flat. Implications reshape our entire investigation. He's the logistics coordinator we'd already cleared—financial pressure but no evidence of intelligence sharing. "Why the hell is Reeve meeting with him?"
Sarah runs facial recognition confirmation, but I don't need biometric analysis. I spent two years studying Committee personnel files, memorizing every face and detail of everyone involved in their operations. Davis's face is as familiar as my own from Kane's surveillance files.
"Davis is on the audit list." Sarah's fingers move rapidly across her keyboard, opening Davis's file and recent activity. "Reeve is checking his security, verifying he hasn't been compromised."
"Or Reeve already knows Davis has been compromised and is running cleanup protocols." The alternative explanation is darker—the Committee has penetrated our investigation deeper than we realized.
"Except Davis doesn't know anything about Echo Base.
" Sarah's analytical mind works the problem, testing theories against available evidence.
"We've been watching his communications for weeks.
He handles warehouse logistics, nothing more.
He's never mentioned Echo Ridge operations or base location. "
"But someone he knows might." I zoom in on the image, studying the interaction between Reeve and Davis. "Davis's logistics work connects him to other Committee assets. One of those connections could have knowledge about Echo Base."
We're looking at new threat vectors, ones we missed. Davis himself might be clean, but his network of contacts could include someone with dangerous information. Someone Reeve will interview during his security audit, someone who will reveal details about operations in northwestern Montana.
"We need to identify everyone Davis has contacted over the past several months." Sarah's already accessing communication records, building a network map of Davis's professional connections. "When Reeve audits Davis's network, we need to know who else gets interviewed."
Davis isn't the problem anymore. His entire network is the problem now. Each contact Davis has made, each colleague he's worked with, each contractor he's coordinated with represents a possible thread Reeve could follow toward Echo Base.
"This is going to take hours." I boot up my own workstation, preparing to help analyze the massive data set Sarah's compiling. "Maybe days if the network is complex."
"Then we'd better get started." Sarah's voice carries the determined focus I remember from DC, the stubborn refusal to quit that made her exceptional at intelligence work. "Because when Reeve finds someone in Davis's network who knows more than they should, we're out of time."
We continue working to build network maps and analyze connection patterns.
Davis's professional contacts spread across the Pacific Northwest, dozens of logistics coordinators and warehouse supervisors and transportation contractors.
Each one gets profiled, assessed for potential knowledge about Committee operations in Montana.
Most are clean. Standard contractors doing legitimate work without knowledge of the Committee's broader activities. But a few names trigger alerts in our databases, matching individuals with previous intelligence connections or operational experience.
"Here." Sarah highlights a name on the network map. "Daniel Williams. He worked with Davis on supply chain coordination for the Committee's Montana operations a few years back. He's since moved to independent contracting, but his client list includes several Committee front companies."
I examine Williams's file, scanning his background.
He's a former Army logistics specialist with decades of experience in supply chain management, currently running a small consulting firm based in Missoula.
His financial records show regular payments from companies we've identified as Committee fronts.
"Williams would know about Committee logistics infrastructure in Montana.
" I trace his recent movements, noting he's stayed close to Missoula.
"When Reeve interviews him about security protocols, Williams will mention supply routes or storage facilities that could narrow the Committee's search grid. "
"We need to know if Reeve has contacted him yet." Sarah reviews surveillance data, checking for any interaction between Williams and known Committee assets. "If Williams's already been audited, we have a problem. If not, we have a chance to get ahead of it."
The surveillance data shows Williams maintaining normal business operations. No unusual travel, no meetings that indicate Committee involvement. But just because we haven't seen it doesn't mean it hasn't happened. Reeve operates carefully, using tradecraft that avoids obvious surveillance markers.
"We should flag Williams as a priority concern." I add his profile to our threat assessment. "Reeve hasn't reached him yet, but he will. Williams's too valuable a source to skip during a comprehensive audit."
Sarah nods, adding Williams to our watch list. Then she displays another profile, this one triggering recognition from my time in Committee networks.
"What about this one?" She pulls up a woman's file. "Amanda Hartley. She handled secure communications for the Committee's regional network a couple years ago, before moving to private sector work. Based in Whitefish now, running a cybersecurity consulting firm."
Hartley worked communications infrastructure while I was deep cover.
I remember her name from operational briefings, remember that the Committee trusted her with sensitive network architecture.
She handled their Montana communications—she knows details about their regional operations that could be valuable to Reeve's investigation.
"She could be a problem." I study her current business operations, noting clients that include several Montana corporations with Committee connections. "When Reeve interviews her about communications security, she'll provide information we don't want the Committee piecing together."
"Should we warn her?" Sarah's already analyzing Hartley's digital footprint. "Give her a heads up about the audit before Reeve reaches her?"
"Risky." I consider the angles. "If she's still loyal to the Committee, warning her exposes us. If not, she takes precautions that make Reeve suspicious."
"But when Reeve gets to her first and asks the right questions..." Sarah lets the implication hang.
"Then we monitor her." I load surveillance protocols. "Watch for Committee contact, track her communications. When Reeve reaches out, we'll know immediately and can assess the damage."
Sarah adds Hartley to our monitoring list, flagging her communications for real-time analysis. Then she leans back, rubbing her eyes. "This is expanding faster than we can track. Davis's network connects to dozens of people, any of whom could have information Reeve can use."
"We prioritize." I bring up the network map, highlighting the most dangerous connections. "Williams and Hartley are top tier because of their operational knowledge. The rest we monitor passively unless something changes."
"Agreed." Sarah checks the time. "We should update Kane. He needs to know about Reeve's meeting with Davis and the potential exposure through Davis's network."
We head toward Kane's office in silence, the old rhythm returning despite everything broken between us. Working investigations together feels natural in ways that personal conversation doesn't, the mission overriding emotional complexity.
Outside Kane's office, Sarah pauses. "Thank you for explaining. About the blackout, the messages, everything. It doesn't fix what happened, but understanding helps."
"I should have found a way to let you know I was alive." The guilt runs deeper than operational necessity can justify. "Should have broken protocol to send some signal, some indication that I wasn't dead or indifferent."
"You couldn't. I accept that now." She looks at me directly, and the tight line of her mouth softens slightly. It's not forgiveness, but the possibility of it. "But that doesn't erase the months I spent hating you. That's going to take time to work through."
"I'll take time over permanent silence." The admission feels dangerous, revealing hope I shouldn't allow myself. "If you don't hate me anymore, maybe eventually you can forgive me."
"That's not how it works." Her voice carries grief tangled with longing. "Hate takes as much energy as love. Both mean I'm still burning fuel on you. What I'm afraid of is the day when I look at you and there's just... nothing. No heat. No anger. Just emptiness."
The words hit hard. Indifference would be the real ending, the final death of what we had. As long as she hates me, as long as she's angry, there are pieces left to rebuild from. But once she stops caring entirely, we're done.
"Then I'll take your anger over indifference," I say quietly. "At least anger means you still care enough to feel it."