PART 18:

Noah felt something cold settle in his chest. You don’t know anything about I know that Melissa made you promise to give Sarah a normal childhood, but I’m betting she also made you promise to live. To not just survive, but actually live. And you’ve been breaking that second promise for 4 years. This conversation is over. Wait, please. I’m not trying to hurt you.

I’m trying to help you see that whatever happens tomorrow, whether we win or lose, you deserve to be more than a ghost in your own life. Sarah deserves a father who’s present, yes, but she also deserves a father who remembers how to be himself. Noah’s hand tightened on the phone. You have no right. I have every right because you made us partners.

Because you told me we face this together. And partners tell each other hard truths even when it’s uncomfortable. Her voice softened. Tomorrow, when we spring this trap, you’re going to be brilliant and tactical and probably save all of us. But after that, when the crisis is over and you’ve proven whatever you think you need to prove, I want you to ask yourself something.

Are you doing this to protect Sarah, or are you doing this to punish yourself? She hung up before he could respond. Noah sat in his kitchen, phone in hand, feeling something crack in the careful walls he’d built around his grief. The worst part was that Evelyn was right. Melissa had made him promise two things in those final weeks.

take care of Sarah and don’t let the work consume him. He’d kept the first promise religiously. The second one he’d been breaking since the day they buried her. He looked at the photo on the refrigerator. Melissa, Sarah, and himself at the beach 2 months before the diagnosis. All of them laughing, windb blown, alive. Melissa had taken a dozen photos that day trying to capture perfect moments.

But this one was Noah’s favorite because nobody was posing. They were just being, just living. When did he stop doing that? His laptop chimed. Email from Marcus with the final compromise map. 43 individual vulnerabilities, all connected, all time to activate during the launch sequence. Noah studied the architecture, looking for the pattern beneath the complexity.

There was always a pattern. The question was whether he could find it fast enough. He worked until 2:00 in the morning building the counter strategy, then forced himself to sleep for 4 hours. Old military discipline. You rested when you could because you never knew when you’d get another chance. He woke at 6, checked on Sarah, still sleeping, and drove to Cross Tower in the pre-dawn darkness.

Marcus was already there, looking like he’d never left. Probably hadn’t. The conference room had been transformed into a command center. Multiple screens showing system status. Engineers working in shifts, coffee cups, and energy drink cans scattered across every surface. “Please tell me you have good news,” Marcus said when Noah walked in. “I have a plan.

Whether that’s good news depends on your tolerance for risk.” At this point, I’d settle for any news that isn’t catastrophic. Noah pulled up the compromise map on the main screen. They’ve built their attack to cascade through three stages. First, authentication failures that look like normal system stress.

Second, data corruption that appears to be human error. Third, total system collapse that seems like infrastructure failure. Each stage is designed to look innocent until the next one triggers, at which point it’s too late to stop the cascade. So, how do we stop it? We don’t. We let it start.

We let them trigger stage one during the launch. let them think they’ve succeeded, but while they’re celebrating, we’re monitoring every connection, every data flow, every communication between their compromised systems. They have to coordinate this attack in real time because it’s too complex to be fully automated. That coordination will expose their command structure.

Kira looked up from her terminal. You want to use ourselves as bait. I want to use their own trap as a tracking device. Once we’ve mapped their entire network, not just what’s in our systems, but where it connects externally, we isolate everything simultaneously, cut them off mid- attack, preserve evidence of the intrusion, and hand it all to law enforcement with a complete chain of custody.

And if they realize what we’re doing before we can isolate them, Marcus asked, then we have a fallback. I’ve built a kill switch into our core systems. One command executed simultaneously across all servers, and everything shuts down clean. We lose the launch. We lose the investment. But we protect the clients and preserve the company’s integrity.

Evelyn will never agree to a kill switch. Evelyn already agreed. I talked to her last night. Noah pulled up the execution plan. Here’s the timeline. Launch initiates at 10:00 a.m. Stage one of their attack will trigger approximately 30 seconds later, just long enough for press coverage to go live.

We’ll have a 2-minute window to complete the trace before stage two activates. If we succeed, we isolate their network and preserve everything. If we fail, I trigger the kill switch and we go down fighting. The room was silent for a long moment. Then Marcus said, “This is insane.” “Yes,” Noah agreed. “But it’s also the only plan we have that doesn’t guarantee failure.” Also, yes. All right.

Marcus stood addressed the room. Everyone hear that? We’re doing this. I need alpha team on network monitoring, beta team on isolation protocols, gamma team on evidence preservation. When this starts, it’s going to move fast. No second guessing, no hesitation. We trust the plan and we trust each other. Questions? Nobody spoke. Good.

👉 [Tap here for the Next Part ] 👈