Story code: ST-000536
Part 3: The Immutable Ledger
My fingers moved purely by muscle memory. The C-shaped aura of my migraine had expanded, turning the right side of my monitor into a shimmering, fractured kaleidoscope. I kept my left eye open, typing blindly with the other squeezed shut, fighting back waves of nausea. The thumping bass from the sales floor vibrated through the particleboard desk, sending fresh spikes of agony into my skull.
At 11:58 AM, I hit the final keystroke. The compiler ran. Green text cascaded down my terminal. The integration patch was successfully pushed to the staging server.
I slumped back, wiping a sheen of cold sweat from my forehead. A shadow immediately fell over my keyboard.
“Conference room. Now,” Chloe said, not bothering to lower her clipboard.
I unplugged my laptop, my hands still trembling, and followed her across the blinding expanse of the bullpen. Derek’s corner office offered no sanctuary. The glass walls trapped the overhead glare, and the silence inside felt heavy, almost suffocating.
On the massive eighty-inch wall monitor, a silver-haired man in a stark white office stared back at us. This was Vance, the lead technical auditor for the venture capital firm. His assessment would determine if the millions in Series A funding would actually hit our bank accounts.
“And here is our brilliant architect now,” Derek said, flashing a flawless, camera-ready smile. He adjusted his platinum cufflinks and gestured to the empty chair beside him. “Silas has the final integration ready to go. We’re pushing maximum synergistic throughput today, Vance. It’s a beautiful thing.”
Vance didn’t smile. “Show me the live transaction logs. I want to see how the algorithm handles the raw data ingestion in real-time. No sanitized front-end interfaces.”
“Of course,” I muttered, my voice raspy. I sat down and plugged the HDMI cable into my laptop.
My screen mirrored onto the massive wall display. To show Vance the raw, unfiltered data throughput, I needed to bypass the standard user interface. I opened up the backdoor administrative dashboard. I had hardcoded this master diagnostic layer myself in the garage. It was an immutable, append-only ledger, designed specifically for strict financial compliance. Once a system event, database query, or API call was executed anywhere on our company network, it was permanently etched into this master log. It could not be edited, deleted, or hidden. Not even by me.
The black terminal window filled the eighty-inch screen. I typed in the search parameter to filter for the latest staging server traffic.
But as I hit enter, a massive block of system-level alerts from the newly integrated HR portal API flooded the query results. The automated data sync had just run, fetching all backend administrative actions and permanently archiving them into my immutable ledger.
I blinked, trying to clear the shimmering migraine aura from my vision, but the red text on the wall monitor was impossible to miss. My name was everywhere.
I froze, my hands hovering over the keyboard.
There, projected in seventy-point font for the entire room-and the lead investor-to see, was a sequential list of database actions executed by Derek’s master administrative account.
`[11:02:14] USER: Derek_Admin`
`[ACTION]: OVERRIDE_COMPLIANCE_REQUIREMENT`
`[TARGET]: Silas_ADA_Accommodation_Medical_History.pdf`
`[EXECUTION]: PURGE_FILE`
My heart slammed against my ribs. I stared at the screen, my breath catching in my throat. Derek hadn’t just ignored my medical documentation for my workstation accommodations; he had manually logged into the system and deleted the three years of medical records I had uploaded.
But the logs didn’t stop there. Below the deletion command were the workflow triggers he had manually configured with Chloe’s HR software.
`[11:05:33] USER: Derek_Admin`
`[ACTION]: TRIGGER_WORKFLOW [Hostile_Workspace_Protocol]`
`[MEMO_LOG_ENTRY]: “Ensure third insubordination strike is issued before October 14. Do not allow ADA compliance workaround.”`
`[SYSTEM_FLAG]: “Accelerate Termination_For_Cause workflow to force 49% equity forfeiture before Vesting Cliff date.”`
The glowing red text bathed the conference room in a harsh, neon light. The silence that followed was absolute.
I slowly turned my head to look at Derek. The charismatic, camera-ready smile had completely vanished from his face. The color had drained from his cheeks, leaving him looking sickly under the fluorescent bulbs. He was staring at the wall monitor, his mouth slightly open, his eyes wide with a sudden, raw panic.
He hadn’t known about the immutable ledger. He had thought whatever he and Chloe typed into the shiny new HR software was their own private domain. He didn’t realize that every single keystroke was hardwired into the uneditable architecture I had built to protect this company.
“Silas, just…” Derek started, his voice barely a whisper, completely stripped of its confident corporate buzzwords. “Just close that window. Let’s look at the algorithm.”
I didn’t touch the laptop. I looked down at the timestamp on the memo. October 14. The vesting cliff was exactly five days away. He had orchestrated the entire morning-ripping down my dividers, locking the lights on maximum, banning my headphones-specifically to trigger a neurological meltdown so he could legally steal my life’s work.
Chloe shifted her weight, the clipboard trembling slightly against her side. She looked at Derek, waiting for him to take control, but he remained paralyzed.
From the wall speakers, Vance’s deep, gravelly voice shattered the silence.
“Derek,” the auditor said slowly, his tone devoid of any warmth. “Would you care to explain why your immutable server logs show you intentionally deleting medical records to fabricate a termination for cause?”
Derek swallowed hard, his Adam’s apple bobbing, but no words came out.