Story code: ST-001752
Part 2: Live Execution
My fingers hovered over the slick, black keys of the laptop. The three venture capitalists leaned in, their breathing shallow with anticipation. Brooks’s heavy, tailored arm rested casually on the back of my chair, effectively pinning me in place. The scent of his Tom Ford cologne was suffocating.
I needed to buy time, or at least modify the execution string to point to a local loopback environment. I rapidly typed `sudo ./genesis.sh`, intending to append the `–dry-run` flag that would keep the payload entirely within my machine’s memory.
Before I could strike the dash key, Brooks’s index finger tapped hard against the screen, right next to the command line. “None of that sandbox nonsense, Matty. We promised Aris a live look at the production environment. Run it as is.”
He had no idea what he was asking for. When he hijacked my AWS instances that morning, he hadn’t just copied a codebase; he had seized control of a live, breathing infrastructure utilized by one of the most ruthless contraband syndicates on the Eastern Seaboard.
“Brooks, the production environment is… volatile right now,” I stammered, my throat parched. “We haven’t sanitized the test databases.”
“That’s the beauty of it,” Aris, the cashmere-clad VC, said smoothly. “We want to see how it handles raw, unpolished execution. Show us the latency.”
Brooks’s grip on the back of my chair tightened. It was a silent, violent warning. *Do it, or you’re done.*
I swallowed hard, closed my eyes for a fraction of a second, and hit Enter.
The terminal instantly flooded with lines of green cryptographic hashes. A split second later, the graphical dashboard Brooks had commissioned from a cheap front-end agency flared to life on the screen. The interface was sleek, all dark mode and neon accents, entirely masking the horrifying reality of the data it was visualizing.
`HANDSHAKE CONFIRMED.`
`NODE A TO NODE B ROUTING ESTABLISHED.`
`LATENCY: 14ms.`
Aris let out a low whistle. “Fourteen milliseconds? On a decentralized mesh? That’s faster than AWS internal routing.”
“It’s entirely peer-to-peer,” Brooks gloated, removing his hand from my chair to gesture grandly at the screen. “No centralized server bottlenecks. The protocol finds the most efficient physical and digital path instantly.”
It was fast because the syndicate’s dispatch servers were heavily optimized, military-grade hardware sitting in a concrete bunker in New Jersey. And right now, those servers had just logged a confirmed pickup request from our exact GPS coordinates.
“Pull up the geographic visualizer, Mateo,” Brooks ordered. “Let’s show them the physical routing simulation.”
My chest seized. I didn’t want to switch tabs, but Aris was already leaning over me, her eyes tracking my cursor. I clicked into the map view.
A dark, stylized map of Manhattan filled the screen. Two pulsating dots appeared. One was a bright red circle directly over Midtown-specifically, the geographic coordinates of Le Bernardin. The other was a blue triangle down in the Meatpacking District.
As we watched, the blue triangle jerked forward, inching its way north on 8th Avenue.
“Incredible,” whispered Sterling, another of the VCs, adjusting his rimless glasses. “You’ve built a live simulation suite that tracks dummy couriers with artificial traffic delays?”
“We spare no expense on proof of concept,” Brooks lied effortlessly, flashing his blinding smile.
It wasn’t a simulation. It wasn’t artificial traffic. The blue triangle was a real syndicate courier in a real vehicle, fighting real Manhattan traffic to get to our location. The protocol dictated that when a genesis drop was initiated, the closest available “driver” was immediately dispatched to the requesting node’s coordinates.
My mind raced, calculating the syndicate’s operational rules. The courier would expect to find a biometric lockbox at the origin point, containing whatever illicit payload the network had slated for transfer. If the courier arrived and found nothing-if they suspected a sting operation, or worse, theft-the syndicate’s automated retaliation protocols would trigger. They didn’t send customer service reps to investigate missing packages; they sent “cleaners.”
And they were heading straight for this dining room.
Deep in my blazer pocket, my burner phone-a device I kept strictly for the network’s automated emergency alerts-emitted a single, sharp vibration.
“This is exactly what we’ve been looking for,” Aris said, stepping back from the laptop and looking at Brooks with newfound respect. “If the code holds up to scrutiny, I think we’re prepared to move very quickly on a Series A.”
“I assure you, the code is immaculate,” Brooks said, pouring a fresh round of Dom Pérignon into the crystal flutes on the table. “Mateo and I will grant your technical due diligence team full repository access tomorrow at nine AM sharp.”
I stared at my screen, the blood draining from my face. Full repository access. If the VC’s technical team looked at the backend logs, they wouldn’t just see dummy data. They would see the encrypted manifests. They would see the staggering volume of illicit transactions. The VCs would legally have to contact the FBI. I would go to federal prison for the rest of my life, while Brooks would feign ignorance and throw me to the wolves.
My burner phone vibrated again. Two short bursts.
I carefully slipped my left hand into my pocket and pressed the button to wake the screen, angling it so no one else could see.
`DISPATCH ALERT: COURIER 88 EN ROUTE. ETA 6 MINUTES. ENSURE PAYLOAD IS READY AT ORIGIN MARKER.`
Six minutes.
I had to get outside. I had to intercept the courier, explain there was a glitch in the routing table, and somehow abort the drop before they stormed the restaurant looking for a nonexistent package.
I started to close my laptop. “I need to use the restroom,” I said, my voice tight.
Brooks instantly reached out, his heavy hand clamping down on my wrist, forcing my hand back to the table. He smiled at the VCs, but his eyes were entirely dead when he looked at me.
“Hold on, Matty,” Brooks said, his voice a low, commanding purr. “Sterling has a few questions about the cryptographic consensus algorithm, and you’re not going anywhere until he’s completely satisfied. Right, Sterling?”
Sterling nodded eagerly, pulling out a notepad.
I looked back at the screen. The blue triangle had just cleared 34th Street. I was completely trapped.