Story code: ST-000921
Part 2: Concrete Floorboards
The black terminal window erupted in a waterfall of white text, the output scrolling blindingly fast, far too quickly for the human eye to track. Arthur’s stiff index finger lingered on the enter key, the plastic slick with a sudden, cold sweat. He watched the directory structures fold, compress, and lock. He wasn’t destroying the application. He was entombing it.
The recursive script he had just triggered was applying a deep cryptographic lock to the relational database he had sacrificed the last half-year of his life to build, binding it to the root operating system with an immutable layer. No deletions, no rollbacks, no panicked weekend pivots. He was making it mathematically impossible for Julian to scrap his masterpiece. The distant servers hummed louder, a physical vibration traveling through the concrete floor, up through the legs of the reclaimed wood desk, and settling deep into Arthur’s aching forearms.
The cell phone vibrated violently against the desktop, rattling against the framed photograph of his daughter. It was Julian.
Arthur let it ring three times. His heart thudded in a heavy, irregular rhythm against his ribs. The blue light from the ultrawide monitor caught the deep creases around his eyes as he finally answered, bringing the cold glass to his ear.
Before Arthur could speak a single word, Julian’s voice exploded through the receiver, breathless and manic. “Arthur! I’m looking at the AWS dashboard on my iPad. Disk I/O is maxed out! CPU usage is spiking across all production nodes!”
Arthur opened his mouth, his throat bone-dry, but Julian didn’t need him to speak. He just needed him to listen.
“You absolute madman!” Julian crowed, a bark of genuine delight echoing over the line. “I send you a voice note, and five minutes later you’re already nuking the dinosaur. I love it! I love the agility! Most developers your age would be whining about change control processes and staging environments, but you’re a beast. You just dive in and rip out the floorboards.”
Arthur stared silently at his secondary monitor. The reassuring green lights of the system health dashboard were slowly turning a steady, locked amber. He hadn’t ripped out the floorboards. He had poured reinforced concrete over them.
“Julian,” Arthur started, his voice cracking from disuse. “The system is-”
“The system is evolving!” Julian interrupted. The sound of a passing siren wailed in the background of his call, loud enough that Julian had to shout over it. “Listen, I just got off the phone with the lead partners at Benchmark. I told them we’re stripping out the old stack tonight. I told them we are transitioning to the hyper-fluid AI graph by Monday morning.”
Arthur’s stomach plummeted. The air conditioning in the empty office suddenly felt suffocating, chilling the sweat on his forehead. “You told the board?”
“I didn’t just tell the board, Artie,” Julian said, carelessly using a nickname Arthur had repeatedly asked him not to use. “I tweeted it. The host of the Silicon Prophets podcast just retweeted me. The hype is unreal right now. We’ve got a tech journalist from Wired joining the Monday nine AM all-hands call. I promised them a live, functioning demo of the new architecture.”
Arthur looked back at his primary screen. The terminal script had finished its execution. A final, solitary line of text blinked at the bottom of the black window:
`LOCKDOWN PROTOCOL COMPLETE. RSA ENCRYPTION KEY REQUIRED FOR WRITE ACCESS.`
The database was completely sealed. Arthur was the only person on earth who held the decryption key, a sixty-four-character string memorized in his tired brain. But now, Julian had promised the world a brand-new, fundamentally different infrastructure by Monday morning. The trap snapped shut with a sickening finality.
If Arthur unlocked the system and revealed that the old database was still sitting there intact, Julian would look like a fraud to his investors and millions of followers, and Arthur would be fired instantly for insubordination. If he didn’t unlock it, the platform would remain frozen, completely useless for Monday’s live demo, and Arthur would be blamed for destroying the company.
“Monday morning,” Arthur whispered, pressing the heel of his free hand against his throbbing temple. “Julian, that’s practically impossible. Even if I had completely wiped the repository, building a functional graph database backend from scratch takes weeks. Not a single weekend.”
“Don’t give me that legacy mindset, Artie!” Julian’s tone sharpened instantly. The toxic, frat-house positivity vanished, replaced by a jagged edge of startup ruthlessness. “You have the whole weekend. You’re already at the office. Just mainline some cold brew and use AI to generate the boilerplate code. I need a functioning backend by Sunday night so I can run my presentation over it. Make it happen. This is why we gave you equity.”
The line went dead with a soft click.
Arthur slowly lowered the phone. The silence rushed back in to fill the dark, cavernous floor, pressing against his eardrums, heavier than before. His screen lit up again. It wasn’t another message from Julian. It was a text from his daughter: *Plane landed. Guess you really couldn’t make it. Again. Have a good weekend at the office, Dad.*
Arthur stared at the message until the screen timed out and faded to black. He looked at his suitcase, tucked uselessly under the desk. He looked at the locked amber lights on the server dashboard. He had forty-eight hours. The young founder didn’t see him as a man with a family, a failing body, or a breaking point. He saw him as a magic wand, a script-executing peripheral meant to translate podcast buzzwords into reality.
Arthur’s arthritic hands began to tremble as he rested them on the mechanical keyboard. He was trapped in a digital bunker of his own making, facing an impossible demand, and the only way out required tearing down the very last piece of his own dignity he had been trying to protect.