Story code: ST-000848
Part 4: Buffer Dump
Chase stared at the glowing terminal, his face cast in pale blue light. He didn’t panic. He didn’t drop the heavy glass award. Instead, he let out a long, slow sigh, the sound echoing faintly against the damp concrete walls of the service corridor.
“Do you know exactly how much your equity packet is worth tonight, Ken?” Chase asked, his voice returning to the smooth, modulated tone he had used on stage. “It’s one point two million dollars. Post-tax. That envelope is sitting on the CFO’s table right now.”
Ken kept his hands hovered over the keyboard. “You’re rejecting severe trauma claims to inflate the Q3 margin.”
“I’m keeping the company solvent,” Chase countered, taking a small step backward toward the kitchen doors. “And I’m making you a millionaire. You take that machine out of this hallway, you forfeit the shares. You walk away from a life-changing amount of money. And for what? So you can play martyr for a system that’s going to fail anyway?”
Ken looked down at the screen. The terminal was still tailing the live logs. Every few seconds, another veteran was punted into the administrative void. He thought about his brother, Mike, staring at a flat red screen in a dark warehouse. He thought about the house he was going to buy for their mother.
Ken’s fingers moved across the keyboard. He didn’t attempt to clone the protected repository. Instead, he executed a command to dump the current terminal buffer into a local, encrypted text file. It was just a few megabytes of raw text-no proprietary source code, no database structures. Just the live operational logs proving the API handshake between the medical router and the corporate accounting server. It bypassed the Data Loss Prevention alarms completely.
Chase saw the command execute. “If you try to leave this building with company property, I will have security detain you. I’ll have you arrested for corporate espionage.”
“It’s a text file, Chase,” Ken said, his voice quiet but steady. “And it’s already saved.”
Ken uncoupled his mobile hotspot, closed the laptop, and shoved it into his bag. The sudden darkness in the alcove made the humming ice machine feel louder.
“Tell the board I went home,” Ken said.
He didn’t wait for Chase to respond. Ken pushed past the project manager, shoved his way through the swinging doors, and marched back into the stifling heat of the kitchen. He ignored the shouts of an expediter as he cut straight across the line, slipping out through the loading dock doors and into the freezing night air.
The valet lot was bathed in the harsh, buzzing glow of sodium-vapor lights. Ken handed his ticket to the attendant, shivering in his suit jacket as he waited among the rows of polished Mercedes and BMWs. When his ten-year-old Corolla finally pulled up, its rusted muffler rattling against the pavement, Ken gave the valet his last five-dollar bill and climbed inside.
He shut the door. The silence of the car was absolute, a stark contrast to the roaring applause he had left behind in the ballroom.
Ken gripped the cold steering wheel, staring blankly through the windshield at the monolithic facade of the Grand Hotel. Up on the top floor, the windows were glowing with warm, golden light. The equity letters were probably being handed out right now.
A wave of nausea washed over him as the finality of what he had just done settled into his bones. His career at ValiantCare was over. He was blacklisted. The one point two million dollars was gone. He wouldn’t be paying off his mother’s mortgage, and he wouldn’t be checking Mike into the expensive, private psychiatric facility he had researched. He was just an unemployed developer sitting in a freezing car, about to become the target of a massive corporate legal team.
Ken reached into his bag and pulled out the laptop. He balanced it on the center console and opened the lid, the screen illuminating the dark cabin.
It was 11:42 PM.
In eighteen minutes, Chase’s automated cron job would execute, purging the server’s deployment history and erasing all evidence of the executive override. ValiantCare would wipe the slate clean.
Ken reconnected his hotspot. He opened a browser and navigated away from his usual development environments, typing in the URL for the federal Office of the Inspector General. He clicked through to the whistleblower tip line.
The website was archaic, built on clunky, plain HTML forms that took too long to load over his cellular connection. Ken filled out his real name, his personal phone number, and his home address. He wasn’t going to hide.
In the description box, he typed a brief, clinical summary: *Live operational logs demonstrating ValiantCare AI routing engine bypassing medical baseline protocols. Logic altered via ‘dynamic_threshold_optimizer.py’ to deny expedited care based on live corporate accounting API queries.*
He clicked the attachment button, navigated to his encrypted drive, and uploaded the text file containing the terminal buffer. It included his brother’s user ID, the severity score of ninety-two, and the API override that changed the threshold to ninety-nine.
Ken hovered his cursor over the submit button. He looked at the hotel one last time. Then, he clicked his mouse.
The browser spun for five agonizing seconds before returning a sterile, gray screen with a twelve-digit confirmation number.
It was done. The government had the logs.
Ken closed the laptop and tossed it onto the passenger seat. He pulled out his phone and opened the text thread with his brother. The screenshot of the red denial screen was still the last message.
Ken typed rapidly. *System error. I’m coming over right now. We’ll figure it out.*
He hit send, put the car in drive, and pulled out of the valet lot, merging onto the empty highway as midnight approached.