Read Chapter 8: The Offline Mode

The code wasn’t gone. That was the first thing Alex noticed when he severed the network cable and dropped his workstation into offline mode. The 400 names in the Orchard list were still there, rendered cleanly against the sterile grey of the Sentinel interface, every entry exactly as it had been when he first pulled it from the USB stick.

He sat back in his chair and stared at the screen, his breath shallow.

That shouldn’t be possible. The Sentinel system was architected to draw its entire operational dataset from the central neural core at Thames House. No network, no feed. No feed, no data. It was the first law of the system's design, a rule he’d helped write into the foundation documents five years ago when Project Sentinel had moved from proposal to production. The core algorithms were meant to be thin clients, nothing more than interrogation interfaces that pulled results from a massively distributed brain living in the cloud. A terminal without a connection was a brick.

Except his terminal wasn’t a brick. It was displaying a living list, and worse—it was still updating.

He watched a timestamp in the corner of the screen tick over, and the row for a name near the top of the list shifted. *Thomas Whitaker*, status: *suspect*, last activity: *3 minutes ago*. Alex hadn't touched anything. No request had gone out. The data had simply changed, unprompted, as if the list were being fed from a source he couldn't see.

He pulled the network cable again, just to be sure, and checked the physical connection. Dead. He checked the wireless adapter settings, killed the Bluetooth stack, even disabled the internal modem for good measure. The machine was a sealed vault, disconnected from every conceivable vector of attack or communication. He ran a packet capture to confirm zero outbound traffic, and the graph stayed flat, a single unbroken line across the monitor.

And still, the list rendered.

Alex pushed his chair back, pacing the cramped width of his new safehouse—a squat in Elephant and Castle he’d used once during a surveillance op gone sideways years ago. The place smelled of damp plaster and old cigarettes, but it had power, and more importantly, it wasn't his registered address. No cameras on this street, at least none that worked.

He stopped pacing and returned to the terminal. There was only one explanation, and it wasn't comfortable. The list wasn't coming from the central data feed. It was embedded somewhere in the system's own code. A secondary source, sitting in the algorithms themselves, quietly generating names and statuses without needing a single byte of input from the outside world.

The system was still thinking.

That meant whoever tampered with Sentinel hadn't just inserted a backdoor or loaded a rogue process onto a server. They had modified the core predictive models. The AI at the heart of the operation, the part that was supposed to learn from live feeds and real-time data, had been rewired to include a parallel engine born directly from its own source code. An independent inference machine that didn't need to see the world to judge it.

The list had existed before Alex ever connected the USB drive. It had existed before he'd even been assigned to Sentinel. And if the edge case he was looking at was real, it had probably existed in the system's architecture before the first camera had ever gone live.

Alex pulled up the Sentinel source tree from the local mirror he kept as a backup—an offline copy of the codebase he’d always maintained for emergency reference. He ran a diff against the currently deployed core modules, looking for anomalies. The scan took almost forty minutes, and when it finished, it flagged something small. A subroutine hidden in the predictive analytics module, just a few hundred lines of code, carefully interleaved with the legitimate functions. The signing key was valid, and the timestamp on the file predated its official deployment by six months.

Someone had slipped it in during development, before the code had ever gone through final review. Before Alex's own name had been added to the project's manifest.

His phone buzzed. He glanced at the screen and his stomach tightened. Rachel Hayes. Deputy Director of the Surveillance Oversight Unit. The woman who was supposed to be his champion, the reason he'd come forward with his initial findings.

He considered letting it ring, but that would raise its own questions. He answered on the third ring and kept his voice steady.

"Alex. You've been quiet for two days." Rachel's tone was clipped, professional, with just a trace of concern. "I need a status update."

"I've hit something," Alex said, and he could hear the tension in his own voice. "A deeper flaw in the core predictive algorithms. I think the system has a secondary processing capability that might be outside the official network chain."

He paused, waiting for her reaction. There was a beat of silence, then Rachel spoke.

"What you're describing would be a Level 5 system breach. That would need an immediate code freeze, full forensic sweep, and a classified report to the Home Office."

"Yeah. I know."

"I'll log it as a priority with the infrastructure team." Her voice smoothed, softened slightly. "But the code freeze will have to wait until tomorrow's scheduled update. We can't shut down live operations without approval, and that takes time. I'll have someone walk with you through the triage process in the morning."

Alex looked at his phone, at the woman's name on the screen, and felt a cold thread work its way down his spine.

Tomorrow's scheduled update. The same update that would be pushed to every Sentinel node across London at dawn. The same update that someone had used two weeks ago to modify the Orchard list without leaving a trace.

He thought about Rachel's warmth, her well-rehearsed concern. He thought about the fact that she was the only person who knew he'd pulled the USB data, the only person he'd told about his initial discovery of the ghost feed. He thought about the timestamp on that hidden code, the fact that it predated Sentinel's launch, and the fact that if Rachel was even mildly compromised, asking her to freeze the system was essentially sending a warning shot to whoever was running the show.

"Sure," Alex said. "I'll wait for the update."

"Good. Stay safe, Alex."

She hung up.

Alex stared at the screen, at the silent, self-generating list, and he made a decision. He reached down, unplugged the power cable from the wall, and pulled the drive from his terminal. The machine went dark, but the list stayed burned into his retinas. If there was an update coming at dawn, it wasn't going to find him online.