Steven stared at the message, thinking James was gone. terminated. His warnings documented but easy to dismiss as the paranoid ramblings of a disgruntled employee who'd been fired for sleeping on the job. The defensive perimeter James built temporary measures living in system memory not integrated into permanent configuration. If someone restarted the core services, those defenses would evaporate. The system would revert to its compromised state.

The trigger James thought he'd removed would reactivate because Steven had been careful. The trigger wasn't just in one place. It was redundant, distributed across multiple configuration files. James had found and removed the obvious instance, but the backup remained dormant, waiting. All it needed was a restart.

Steven replied to the encrypted message, proceeding as planned. Expect results by end of day. He deleted the message thread, wiped the USB drive, dropped it in his briefcase, then he walked down to the third floor operation center. 12:15 p. m. Steven moved through the space with the easy authority of someone who'd been VP for 6 years.

Engineers nodded as he passed. He stopped at Jason Morrison's console. Jason on duty supervisor, 31 years old, competent enough, eager to please leadership. How's the Monday load looking? Jason pulled up the performance dashboard.

Elevated latency in the payment processing queue. Nothing critical, but we're averaging 3.2 seconds per transaction when we should be under.5. Steven nodded, studying the metrics with practiced concern. Looks like memory accumulation standard Monday spike after the weekend batch processing. You'll probably want to clear that before the afternoon trading window opens.

Jason hesitated, glancing at the restart protocol documentation. Should I coordinate with the infrastructure team first? It's a standard optimization restart. You've done it dozens of times. Just make sure you're using the approved restart sequence.

Steven's tone was perfectly calibrated. Casual authority. No pressure. Just a VP offering operational guidance to a supervisor managing a routine issue. Jason pulled up the restart checklist.

Standard procedure approved by the infrastructure team 3 months ago. I'll schedule it for 12:45 right before the lunch hour ends. Sounds good. Let me know if you need anything. Steven walked away, stopped by two other consoles to ask unrelated questions, establishing that his visit to the operation center was routine, not focused on Jason or the restart.

Then he returned to his office, checked his watch 12:20. 25 minutes until the restart. 25 minutes until Patricia Harrison's first day became a catastrophic failure that would force the board's hand. Steven opened his calendar, started drafting an afternoon meeting request with Richard Harrison. Subject: Urgent operational concerns requiring board attention.

He'd wait until the system started failing. Then he'd be the one raising the alarm, demonstrating leadership during crisis, positioning himself as the steady hand who could guide the company through the transition to tech. Perfect timing, perfect execution, all because James Mitchell had been too exhausted to explain what he'd discovered before Patricia fired him. 12:30 p. m. East Austin James's apartment.

He'd made it home around 9:00, stripped off his work clothes, collapsed in bed properly this time. Slim claimed him before conscious thought finished processing the morning's disaster. His phone rang, vibrated on the nightstand, pulled him partially toward consciousness, but not quite to the surface. Different caller. Same result.

The third call finally broke. James fumbled for the phone, eyes gritty. Mind foggy. Brian Thompson. James answered.

Brian. James. Jesus. I just saw your incident report. Why didn't you call me yesterday?

James sat up. Room tilting slightly. Dehydration and exhaustion making everything harder than it should be. I did call you Saturday. You told me to document it and wait for Monday.

Silence. Then Brian's voice came back. Quita. The 52page report. You wrote that Sunday.

Sunday night after I neutralized the threat. It's all in the documentation, timeline, evidence, defensive measures, everything. James, Patricia Harrison fired you this morning. I know. I was there.

Did you brief anyone about the security incident before she terminated you? James felt something cold settle in his chest. I tried to tell her. She wouldn't listen, but the report is in the shared repository. Tagged maximum priority.

You're copied. Security team is copied. Everyone who needs to know has access. More silence, James. The restart is scheduled for 12:45.

Routine Monday optimization. The words took a moment to register. Then they hit like a physical impact. No. No.

Brian, you can't restart the system. It's in the report. The defensive perimeter I built exists in system memory. A restart will wipe everything. I'm reading the report now.

But James, you're terminated. Your access is revoked. I can't just cancel a scheduled maintenance procedure based on a report from someone who was fired for sleeping during critical hours. James was on his feet moving toward his laptop before conscious decision. I wasn't sleeping because I was lazy.

I was sleeping because I'd been defending the system for 48 hours straight. The attack is real. The trigger is real. If you restart before properly integrating my defensive measures, the system will fail exactly how I documented. I believe you.

But I need to escalate this through proper channels. Get security team sign off. Maybe brief Patricia directly. There's no time. The restart is in 15 minutes.

James' laptop was booting. Remote access credentials still active because it hadn't processed the termination paperwork yet. He logged into the monitoring systems, pulled up the defensive perimeter status. Still active, still holding, but fragile. Temporary.

Built to last hours, not days. Brian, you need to stop the restart now. Don't wait for approvals. Just stop it. I can't override Jason's authority without cause.

If I cancel a routine maintenance procedure and nothing bad happens, I look like I'm protecting a fired employees paranoid conspiracy theory. The calculation was transparent. Brian weighing professional risk against uncertain threat. James pulled up the system logs looking for signs that the attack was still active. They're buried in the weekend traffic.

More probing requests. Different source IPs, but same pattern. The attackers hadn't stopped. They were waiting. Brian, I'm looking at the logs right now.

The attack is still active. They're waiting for someone to restart the system and disable my defenses. Forward me those logs. I'll take them to security immediately. There's no time.

James checked the clock. 1238. 7 minutes. His fingers moved across the keyboard. muscle memory from nine years of emergency troubleshooting. He started building a priority override for the restart protocol.

If he could inject a hold command before Jason executed the restart by enough time for Brian to escalate properly, but his access credentials were flagged. Every command he issued was logged with his user ID and his user ID was attached to a termination notice. Using his access to modify production systems after being fired would be grounds for criminal charges. Unauthorized access potential sabotage. James hesitated.

James, are you still there? I'm here. Send me everything. I'll get security team on a conference call. We'll review and make a decision.

You don't have time to review. You have seven and it's 6 now. James' screen showed the restart protocol Q. Jason had already initiated the command sequence. Just waiting for the scheduled execution time.