I was leaning against the counter watching Derek struggle with a pod that was clearly labeled decaf while he muttered about optimizing caffeine throughput. It was a Tuesday, or maybe a Wednesday — honestly, the days blurred together in that windowless room. I was the senior systems administrator, the one who never skipped a step, the one who kept the classified systems running like clockwork. Then Ethan happened.
Ethan was the new guy, fresh out of some online certification program, and he had a habit of treating our security protocols like suggestions. That morning, he was standing in front of the mainframe, his hands hovering over the keyboard, and I saw it — a command sequence that shouldn’t exist outside of a textbook warning. I told him to stop. I told him we needed to run the rehashing sequence first, the one that only existed in my head and on a secure offline drive.
He laughed. He said I was being paranoid, that the system could handle it, that he’d done this a hundred times. I watched him flush the cache without the proper sequence. The system didn’t crash.
It didn’t even blink. But I knew what he’d done. The checksums were gone, and the system was designed to assume that if they vanish suddenly, the facility has been overrun by hostiles. I could feel a cold knot in my stomach as I pulled up the access logs from my terminal, bypassing the standard monitoring because I was the one who wrote those exceptions.
The logs showed a silent alarm, a 64-byte packet sent via a subfrequency that goes straight to the federal oversight board. Ethan just looked at me, confused, holding a coffee cup that was clearly not his. I told him what he’d done. I told him about the silent alarm, about the federal response, about how the system was now locked in a state that only I could unlock.
The words came out flat, calm, but they were screaming inside. Ethan’s face went pale, his fingers twitching at his sides. He tried to deny it, tried to blame the system, tried to say he’d just been following a routine update. But I had the logs on my screen, and the logs don’t lie.
The worst part was that I’d trained him. I’d walked him through the protocols, showed him the back doors we kept for emergencies, made sure he understood the difference between a standard cache flush and one that required the rehash. He was the only other person who knew about the override, and I thought he’d respected it. I guess respect doesn’t survive ego.
The next morning, my badge didn’t work. I stood in front of the security door, swiping it like an idiot, but the light stayed red. Derek, my manager, came down from his office, his face tight, and told me that Ethan had filed a report claiming I was the one who’d triggered the alarm, that I’d been acting erratic, that I’d threatened him. I tried to explain, but Derek just shook his head.
He told me to pack my things and leave before legal got involved. The look in his eyes wasn’t anger. It was fear. And then the call came.
My phone buzzed with a number I didn’t recognize, an area code from Washington, D. C. It was the federal oversight board, and they wanted to discuss my security clearance. Effective immediately.
They said I’d been flagged for unauthorized access, that my biometrics had been used to log into a classified node at 2:47 AM — a time I was at home, sleeping, with my phone on the nightstand. They’d pulled the logs, and the logs showed my ID, my credentials, everything. Except I hadn’t touched that system. I hadn’t even been in the building.
I tried to tell them it was a mistake, that someone was framing me, but the voice on the other end was steel. They said they’d be sending an adjudication team to my house, and that I was not to contact the site, not to log in remotely, not to do anything until they arrived. They warned me that if I touched any government system, my clearance would be revoked permanently, and I’d face felony charges. Then they hung up.
I stood in my kitchen, staring at my reflection in the microwave. My hands were shaking. My phone buzzed again — a text from Derek. He said he was sorry, but he’d had to sign the termination paperwork.
He said they’d offered me a deal: if I signed the NDA and left quietly, they’d drop the federal investigation. He said it was the best I could hope for. I didn’t respond. That night, I couldn’t sleep.
I kept replaying the moment Ethan flushed the cache, the way he’d looked at me after, the way he’d smiled. It wasn’t embarrassment. It was relief. He’d known exactly what he was doing.
He’d set me up from the start, and I was too busy watching the code to see it. The adjudication team arrived the next day, two men in dark suits with badges. They sat in my living room, asked me questions about my security clearance, about my last login, about my relationship with Ethan. I told them the truth, but they just wrote things down, their faces blank.
One of them, a man with a thick mustache, asked me if I had any enemies at the company. I almost laughed. Just one, I said. He wrote that down too.
Then they asked me about the Reddit post. I blinked. What Reddit post? They told me someone had posted detailed schematics of our facility’s security system on a public forum, complete with access codes and encryption keys.
The post was timestamped the night of the alarm, and the account was under my name. I’d never seen that account before in my life. But when they showed me the printout, I recognized the writing style — short sentences, obsessive details, a specific phrase I used in my own private notes. It was Ethan’s voice, disguised as mine.
I told them about Ethan’s file names, about how he’d been pulling code from public sources, about his sloppy work. But they weren’t listening. They were focused on the one thing they could prove: a federal resource had been compromised, and my account was the trail. They said I was being suspended pending further investigation.
They said not to leave the city. The next week was a blur of lawyers and phone calls. I couldn’t find anyone who believed me. My friends at the company stopped answering my texts.
My own manager, Derek, wouldn’t take my calls. I was told I’d lost my clearance, permanently. I was told to sign the NDA or face charges. I was told I should have been more careful.
And then, late on a Thursday night, I got an email from an address I didn’t recognize. The subject line was empty. The body contained a single link and a timestamp. I clicked it, and it took me to a secure shell session — a session that matched my old login credentials.
On the screen, before it was closed, I saw the system status. It wasn’t running. It wasn’t locked. It was purged.
All data, all backups, all logs — gone. Something had happened to the system the night of the alarm, something I hadn’t done. I pulled up the access logs stored on my personal drive — the backup I’d made against policy. The logs showed a series of commands entered with my credentials at 2:47 AM.
The commands weren’t the ones I’d used to prevent Ethan’s crash. They were something else. They were the commands someone would use to wipe everything. And that’s when I saw the file name.
It was the one Ethan had used the day of the incident, the one I’d shown him as an example. The file was named after a song he said was his favorite. He’d never said what it was, but I knew. I’d seen it in his notes.
It was the name of a song about someone who never gets caught. I’m not signing anything, I said to myself, laying back on my couch. I’m not going to let him win. But I don’t know what to do next.
I don’t know who to trust. I only know that somewhere out there, Ethan is smiling, and the systems that used to be mine are gone. It’s a strange thing to lose everything you built. They say the code is just data, but it’s not.
It’s your memory, your habits, your protection. And when someone takes it from you, you don’t just lose a job. You lose your whole world. I still check my email every night, waiting for a message that never comes.
But I know that code remembers everything. You can lie to your boss, you can lie to the government, but you can never lie to the code. The code always remembers. So I’m writing this down, the only way I know how.
Not because I think it will help. But because I need someone to know the truth before it all goes dark.