Chapter 3: The Courier’s Burden

Julian gestured with a dismissive flick of his hand. “Go on, then. But don’t think you’re going anywhere until I have that key in my hand.”

The enforcers mirrored his command, one blocking the main exit, the other positioning himself between me and the side door. I was trapped, but the critical first step was done. Jamal Pryor, somewhere out in the Atlanta night, was carrying the first thread of my digital grenade.

I sat back down at the console, pretending to troubleshoot the “slow system” to buy time, while subtly monitoring the connection to Jamal’s tablet. A small data stream, disguised as routing updates, flowed silently. It contained the embedded commands for a full-scale data purge, waiting for my final activation signal.

“Trouble logging in, Marcus?” Julian asked, his voice laced with mocking humor. He paced the narrow aisle, casting long shadows.

“Just some network congestion,” I mumbled, making a show of typing furiously. My real focus was on the small, green dot on a map displayed on a second monitor, hidden partially by a stack of old user manuals. That dot was Jamal.

He was moving. His delivery route was taking him past the outer perimeter of the VibeNet facility, a perimeter now crawling with Julian’s armed men. The ultimate unwitting mule.

I watched as the dot passed the first security checkpoint, then the second. Julian’s men were focused on who was coming *in*, not the legitimate VibeNet couriers making their routine deliveries *out*. They wouldn’t even think to check a standard VibeNet dispatch tablet for anything more than delivery manifests.

A small tremor of hope ran through me. It was working. The remote access I’d established through Jamal’s tablet was stable, bypassing VibeNet’s primary internal network. This was my back channel, my lifeline.

“Still waiting, Marcus,” Julian’s voice cut through my concentration. He had stopped pacing and was now leaning over my shoulder, too close. I could feel his breath on my neck. “My patience is wearing thin.”

“Almost there,” I said, feigning a frustrated sigh. I pulled up a fake error log, hoping it looked convincing. “Looks like a routing error on the main fiber grid. Classic VibeNet infrastructure.”

Julian grunted, unconvinced. “Fix it.”

But I wasn’t trying to fix Julian’s problem. I was creating a much bigger one. With Jamal’s tablet now safely outside the building and maintaining its connection, I had a choice.

I could divert the wipe command through the city’s secondary fiber grid, a slower but more secure route, less prone to immediate detection by Julian’s internal network monitors. Or I could go for a more direct, aggressive approach: cut power to the facility floor, forcing a hard reboot that might scramble their initial defenses.

The secondary grid felt safer. A stealthier attack. But Julian’s presence, his physical proximity, pushed me towards a quicker resolution. Still, caution whispered in my ear. The last thing I needed was to tip my hand too early.

“What are you doing now?” Julian demanded, noticing the shift in my screen activity. I was deliberately bringing up a network diagnostics panel, making it look like I was trying to solve *his* supposed problem.

“Checking the fiber lines,” I explained, pointing to a graph of network traffic. “If there’s a problem there, it’ll affect everything.”

It was a lie, but a plausible one. And it bought me the crucial seconds I needed to set the next stage of my plan into motion. The green dot on the map moved further away, solidifying my connection. The remote access was locked in.