PART  12:

Don’t do that. Let Arbiter work the way it’s designed to work and adjust your AI protocols to communicate in terms Arbiter understands. You’re trying to teach it English when you should be learning its language.” The engineer stared at his screen, then suddenly his expression cleared. Oh. Oh, that’s actually brilliant.

If we restructure the AI requests as resource allocation queries instead of priority flags. Exactly. Now you’re thinking like the system instead of thinking at the system. Lena watched from the doorway, fielding calls and emails, but unable to tear herself away completely. There was something magnetic about watching Noah work, seeing him come alive in a way that cleaning offices could never allow.

This was who he was supposed to be. This was the life that had been stolen from him by an industry that valued loyalty over integrity. Around noon, Marcus Chen appeared at Lena’s elbow, his expression troubled. We need to talk. About the security footage. Lena had almost forgotten. The video of Noah accessing her laptop in the middle of the night, the evidence that had seemed so damning yesterday.

With everything happening, it felt like a problem from another lifetime. Not now, Marcus. Lena, this can’t wait. I’ve reviewed more footage. He’s been accessing multiple executive computers, not just yours. Whatever he’s doing, it’s systematic. And now you’ve brought him into our most sensitive development project.

Marcus lowered his voice. I don’t care how brilliant he is. This is a security breach. Give me until end of day, Lena said. I’ll talk to him and get an explanation. And if the explanation is that he’s stealing proprietary information? Then we’ll deal with it. But Marcus, look at him. She gestured toward the lab where Noah was explaining something to Thomas using hand gestures to illustrate system architecture.

Does that look like a corporate spy to you? The best ones never do. Marcus said darkly. End of day, Lena. Then this goes official. He left, and Lena felt the weight of another clock ticking down. She had until tonight to solve multiple impossible problems, save Genesis, clear Noah’s name, and somehow make sense of why a man who’d lost everything because of his integrity would risk it all again by stealing corporate data.

By 4:00 p.m., the engineering team had made more progress than they’d managed in the previous 2 days combined. The Arbiter framework was loading, integrating with Genesis’s core systems in ways that looked promising. Error logs that had been screaming with conflicts were starting to quiet. It wasn’t solved yet.

There were still bugs to fix, edge cases to account for, stress tests to run. But for the first time since the crisis began, Lena could see a path to success. Take a break, she told the team. Order dinner, get some air, come back in an hour. We’re going to be here late, so pace yourselves. The engineers scattered, grateful for respite.

Noah remained at the whiteboard staring at his diagrams with the focused intensity of someone checking their work for errors. Lena approached carefully. You did good today, she said. The team is listening now. Some of them. Thomas still thinks I’m a fraud who got lucky. I can see it in the way he double-checks everything I say. Noah didn’t sound offended, just tired.

Can’t blame him. In his position, I’d be skeptical, too. I need to ask you something, and I need you to be honest with me. Noah turned to face her, immediately wary. About what? Security footage shows you accessing my laptop. Multiple times over the past month, middle of the night, always when the building was empty.

You knew my password, or you bypassed it somehow. Lena kept her voice neutral, non-accusatory. I need to know what you were doing. Something flickered across Noah’s face. Not guilt, exactly, but something close to it. He was quiet for a long moment, seeming to wrestle with how much to say. Finally, he pulled out his phone and opened a folder of photographs.

He handed the phone to Lena without comment. The images showed computer screens displaying code. Specifically, code from Tech Vanguard’s security infrastructure. But interspersed with the code screenshots were other images. Vulnerabilities, backdoors, security flaws that would make any IT professional’s blood run cold.

Noah had documented dozens of critical weaknesses in the company’s systems. Each one carefully annotated with notes about potential exploits and recommended fixes. You were auditing our security, Lena breathed. Why? Because I saw the same patterns I saw at Cyberdyne. Noah said quietly. Your company is growing so fast that security is an afterthought.

Everyone’s focused on development, on features, on beating competitors to market. Nobody’s thinking about what happens when bad actors find the holes you’ve left open. I started noticing them while I was cleaning. Passwords on sticky notes, unlocked computers, sensitive data left visible on screen, so I started looking deeper.

By accessing executive computers without permission. I couldn’t exactly file a formal security report. I’m a janitor. Nobody would have listened. And by the time I realized how bad it was, I knew I had to document everything before I said anything, because otherwise it would just be my word against the company’s interests.

Noah took his phone back, his expression grim. You’ve got three separate entry points where someone with moderate skill could access your entire customer database. Your AI development servers have authentication protocols that could be bypassed by a first-year science student. And your financial systems? He shook his head.

👉 [Tap here for the Next Part ] 👈