Story code: ST-001445
Part 2: Deployment Blocked
The red numbers on the primary monitor shifted from 14:00 to 13:59.
Marcus dragged his mouse over the security prompt, frantically clicking the ‘Cancel’ button. The modal window remained frozen, stubbornly demanding the sixteen-character alphanumeric override key. He had handed that key directly to Elias Vance, the technical director for the Texas Liberty PAC, at five o’clock yesterday afternoon. The handover marked the end of his contract. Marcus had built the cage, locked it, and surrendered the only key.
He reached for his cell phone, his hands shaking so violently he nearly knocked over his coffee mug. He scrolled to Chloe’s contact and hit dial. He pressed the phone to his ear, listening to the agonizingly slow rings. One. Two. Three.
“Hey, you’ve reached Chloe. Leave a message!”
Marcus opened his mouth, the words *Get out of there, they know* forming on his tongue, but he abruptly ended the call. He couldn’t leave a voicemail. He couldn’t even send a text. The very system he was staring at aggressively scraped unencrypted SMS and telecom metadata through data brokers. If he contacted her now, the algorithm would instantly map the connection between Subject 884-B and its lead developer, flagging them both for conspiracy to bypass state law. He tossed the phone onto the desk as if it were burning him.
*Timer: 11:42.*
Marcus minimized the dashboard and opened a black terminal window. If he couldn’t stop the export through the front-end interface, he would have to kill the backend process. His fingers flew across the mechanical keyboard, muscle memory taking over as he typed the SSH command to access the production server.
`ssh -i ~/.ssh/tlp_prod admin@192.168.x.x`
He hit enter and rapidly typed out his master passphrase.
`Permission denied (publickey).`
He tried again, forcing himself to slow down and hit every key deliberately.
`Permission denied (publickey).`
Marcus let out a ragged breath. The client’s IT team had wasted no time. The moment he surrendered the override code, they had rotated the cryptographic keys and purged his developer access from the production environment. He was completely locked out of the live server. He was nothing but a read-only spectator watching his daughter’s life barrel toward ruin.
*Timer: 08:15.*
He stared at the countdown. Once the timer hit zero, the system would compile the telemetry data, the financial records, and the visual evidence-including the un-blurred photo of her face-into an encrypted JSON payload. That payload would automatically route through an AWS Lambda server straight to the local sheriff’s department and the PAC’s hostile litigation team.
He couldn’t stop the compilation. But he knew how the payload traveled.
He still had his GitHub developer credentials. The code repository wasn’t the live server, but it fed directly into it via an automated deployment pipeline. If he pushed a critical flaw into the transmission protocol-a deliberate bug-the pipeline would deploy it to the server, crashing the Lambda function before the payload could successfully route.
*Timer: 06:30.*
Marcus opened his code editor and found the `export_router.js` file. His chest tightened, a cold sweat breaking out across his forehead. He navigated to the core transmission loop and began altering the syntax. He didn’t just need an error; he needed a fatal memory leak. He wrote a recursive function that would call itself infinitely without ever returning a value, designed to overwhelm the server’s allocated memory and instantly trigger a catastrophic crash. It was sloppy, brute-force sabotage, but it would buy him time to physically get to Chloe.
He saved the file. He swapped back to the terminal.
`git commit -m “hotfix: routing latency patch”`
`git push origin main`
He hit enter. The terminal output confirmed the upload.
*Timer: 04:11.*
Marcus switched his browser to the PAC’s cloud integration dashboard to watch the deployment pipeline. A series of gray circles appeared on the screen, representing the steps to push the code live.
The first circle, *Build*, spun for a few seconds before turning a solid, reassuring green.
The second circle, *Automated Testing*, began to spin. Marcus held his breath. The tests were designed to catch infinite loops. He had hastily disabled the unit tests in his commit, but he didn’t know if the PAC had enabled secondary server-side checks. The circle kept spinning. Ten seconds. Twenty seconds.
It turned green.
Marcus leaned forward, a desperate surge of hope rising in his throat. Just one step left. The third circle, *Deploy to Production*, began to spin. If this turned green, the transmission function would crash. The timer, now at 02:50, would fail to send the tip.
The third circle stopped spinning. It flashed a bright, blinding red.
A hard stop error message populated beneath it in stark white text.
`DEPLOYMENT BLOCKED: Branch protection rules enforced. Critical infrastructure modifications require one (1) approving review from repository administrator.`
`Administrator: Elias Vance.`
Marcus stared at the screen, the breath knocked out of him. He had implemented that safety protocol himself three months ago to prevent junior developers from accidentally taking down the system. Now, it was a reinforced steel wall between him and his daughter.
He couldn’t approve his own sabotage.
*Timer: 01:45.*
The silence in the office was suddenly shattered by the harsh, vibrating buzz of his cell phone against the wooden desk.
Marcus flinched. He looked at the caller ID. It was a restricted number, but he recognized the Dallas area code.
He answered the call, pressing the phone to his ear with a trembling hand.
“Marcus,” Elias Vance’s voice was smooth, completely devoid of sleep despite it being two in the morning.
“Elias,” Marcus croaked, his throat entirely dry.
“I just received a PagerDuty alert on my phone,” Elias said, the faint, rhythmic sound of typing echoing in the background. “The system says you just attempted to push a massive recursive loop into the main export router. A change that bypasses our testing protocols and requires my manual approval.”
Marcus watched the red timer on his monitor drop below the one-minute mark. *00:59.*
“It’s a critical patch,” Marcus lied, his voice sounding hollow to his own ears. “I noticed a memory leak in the compilation cache. I was just trying to fix it before the next batch went out.”
“Is that right?” Elias asked softly. “Because it looks a lot less like a patch, and a lot more like a deliberate attempt to crash the node. And what I find incredibly interesting, Marcus, is that you are trying to break the transmission router exactly fifty-four seconds before the system is scheduled to export a ninety-eight percent confidence packet.”
Elias paused, the typing in the background ceasing. “Who is Subject 884-B, Marcus?”