The CTO blamed me for crashing the company network and demanded I sign a performance plan, but when I bypassed his wiped software logs and plugged directly into the physical switch, I found the secret crypto-mining operation melting our backup servers.

The CTO blamed me for crashing the company network, expecting me to accept the blame for the crypto-mining operation he was running on our backup servers.

My name is Anna Torres. I am a systems administrator for a mid-sized data analytics firm. Software logs can be manipulated or deleted if you have the top-level administrative password, which he did. But you cannot delete heat, and you cannot hide raw power draw from the cooling units. The hardware always tells the truth.

My sanctuary is the physical infrastructure. I know every cable, every switch, and every power distribution unit in the building. On a Tuesday morning, three weeks before the crash, a severe latency ticket came in from the sales floor. The client dashboards were timing out, dropping connections mid-query. I did not bother with the high-level monitoring software that the executives favored. I walked directly into the server room. The air was a perfect, clinically maintained sixty-three degrees. The hum of the racks was a physical vibration in my jaw, a familiar, steady rhythm.

I pulled my custom crimping tool from my belt—a heavy, steel-handled device I used to terminate the exact lengths of Cat6 cable that kept our physical network flawless. I bypassed the management interface and plugged my console cable directly into the command line interface of the core routing switch.

It took me exactly ninety seconds to find the anomaly. A misconfigured spanning tree protocol on a secondary switch was creating a massive broadcast storm, essentially forcing the network to swallow its own tail and choke on redundant data. I executed the kill command on the rogue port. I watched the traffic graphs on my screen instantly flatline back to normal resting levels. The latency dropped to zero. I unclipped my console cable, coiled it in perfect symmetry, and slotted my crimping tool back into its holster.

Brian Wallace, our Chief Technology Officer, walked into the server room just as I was locking the metal cage door. He carried a brushed steel, temperature-controlled coffee mug. He set the heavy mug directly on top of the crash cart, dangerously close to an exposed patch panel.

“Anna, you need to rely on the software dashboards more,” Brian said, tapping the smooth glass of his tablet with his index finger. “You spend too much time crawling around in the metal. The dashboard said it was a temporary ISP throttle. You didn’t need to come down here and pull cables.”

“The dashboard was lying,” I said. “It was a layer-two routing loop.”

Brian took a slow sip from his steel mug. He picked it up, leaving a faint ring of condensation on the metal cart. “We are a high-level analytics firm. Stop playing cable monkey and trust the UI.”

He walked out. I took a microfiber cloth from my pocket and wiped the condensation off the cart.

Two weeks later, the network collapsed.

It started on a Saturday night. The backup clusters—massive, expensive rigs designed to sit idle and take the load only if the primary servers failed—suddenly started screaming. The automated thermal alerts lit up my phone at 2:00 AM. I tried to log in remotely to diagnose the load, but the access was throttled to an absolute crawl. The entire system was choking on an invisible demand. Clients started calling the emergency line by Sunday morning, demanding to know why their data streams had flatlined.

I drove to the office in the dark. I wanted to take the backup clusters completely offline to run a full diagnostic isolation. Brian denied the request.

“They are mission critical,” he told me over the phone, his voice completely steady, absent of any panic. “Do not touch the power array. Reroute the primary traffic through the secondary switches and find the software bug. Do your job, Anna.”

I spent thirty hours on the floor of the server room trying to stabilize a network that felt like it was actively fighting me. I skipped meals. I drank stale water. By Monday morning, the damage was done. We lost two major client uploads, costing the firm tens of thousands of dollars in SLA penalties.

At 9:00 AM on Monday, Brian sent a company-wide email to all two hundred employees. He blamed the weekend outage entirely on “suboptimal routing configurations deployed by the sysadmin team.” He stated that the physical infrastructure was perfectly sound, but human error in the network topology had caused a catastrophic bottleneck.

At 10:00 AM, Human Resources placed a blue folder on my desk. Inside was a formal Performance Improvement Plan. It required my immediate signature. It explicitly stated that one more network failure would result in my immediate termination for cause.

On Tuesday, I went back into the server room.

The ambient temperature was wrong. The digital thermostat on the wall read sixty-eight degrees. It was a five-degree spike. In a room designed to disperse massive thermal loads, five degrees is an earthquake. I walked down the cold aisle toward the backup clusters. The exhaust fans were whining at maximum RPM, a high-pitched mechanical shriek. I checked the physical hypervisor screens attached directly to the racks. The CPU loads on the backup clusters were pegged at ninety-nine percent. It was a Tuesday afternoon. Our backup traffic should have been dead zero.

I went to my desk. I pulled the software access logs for the backup servers.

Empty.

Wiped clean. Zeroed out by a master administrative override.

I closed the software dashboard.

I grabbed my laptop and my blue console cable. I walked back into the server room.

I sat on the raised floor grates.

I plugged directly into the core physical switch.

I bypassed the server operating systems entirely.

I pulled the SNMP logs. Simple Network Management Protocol is the raw packet tracker embedded in the hardware itself; you cannot wipe it without shutting down the entire building’s internet connection.

The packets flooded my screen. Millions of them.

They were not client analytics. They were not internal company data.

They were outbound requests. Routing to external IP addresses.

I ran the IP addresses through a global registry.

They belonged to three of the largest cryptocurrency mining pools in the world.

I opened a new terminal window. I accessed the building’s industrial HVAC controllers. I pulled the raw power consumption metrics for the server room cooling units over the last thirty days.

Massive electrical spikes. Peaking every night between midnight and 6:00 AM.

I cross-referenced the power spikes with the building’s physical keycard swipe logs.

Brian Wallace’s executive badge swiped into the elevator at 11:45 PM every night the power spiked.

He didn’t find a configuration error. He melted the servers mining Bitcoin.

I sat on the metal grates. The cold air blew up through the vents, freezing the sweat on my arms. The servers roared above me, degrading their own silicon to mint his money. I closed the laptop screen. I unplugged the console cable. I wrapped the cord around my hand, loop by loop. I placed the laptop in my bag. I zipped it shut. I stood up. I brushed the dust from my knees.

The worst part wasn’t the evidence I held in my bag. The worst part was that the all-hands technical post-mortem meeting was starting in exactly twenty minutes, and Brian was going to stand in front of a whiteboard and present his fabricated case against me, completely unaware of what I had just pulled from the metal.

The primary server room was a closed ecosystem. I spent my first two years at the firm building it from bare metal, routing every connection to ensure perfect thermal balance and zero latency. Six months ago, Brian Wallace started treating the backup clusters as his personal property.

I was terminating a new bundle of Cat6 cables for the sales floor expansion when he swiped his executive badge into the metal cage after hours. He did not look at the racks; he looked at his phone. “I’m setting up a cron job on the secondary hypervisors,” he said, scrolling through a screen. “Dynamic stress testing.”

I explained that the secondary clusters were failovers, not testing environments. If the primary system failed, the secondary needed zero thermal load to take the handoff smoothly. He smiled. It was not a professional acknowledgment, but the tolerant smile of an adult listening to a child explain a toy. “We have a million dollars of compute sitting idle, Anna. It’s a waste of silicon. I’m going to run background analytics.”

He reached into his pocket and pulled out a sealed plastic blister pack containing a new biometric USB security key. He did not have scissors. He reached across my cart and picked up my custom steel crimping tool. He wedged the heavy termination teeth under the thick plastic seam and twisted hard, using the precision mechanism as a crude pry bar. The plastic snapped open. He pulled out the key.

He tossed the crimping tool back onto my cart. It landed hard against the metal tray. The calibration spring clicked out of alignment. He walked out to begin his testing. I picked up my tool and spent ten minutes recalibrating the tension I needed to do my job.

The consequences of his background analytics arrived on a Saturday night. The phone on my nightstand vibrated at 2:14 AM.

The automated thermal alerts did not just ping; they cascaded in a continuous stream of critical warnings. I opened the high-level monitoring dashboard on my home laptop. The interface was swimming in molasses. The primary traffic from our clients in Asia was hitting a massive wall of latency. The system was choking on an invisible demand that the software could not identify.

I attempted to execute a remote-spool command to shift the Asian traffic to the secondary clusters to relieve the pressure. The command timed out. The secondary clusters were not just running his background analytics; the CPU load was entirely consumed. The dashboard showed the processors running at ninety-nine percent capacity, creating a thermal block that prevented any new traffic from entering the racks.

Clients began calling the emergency escalation line at 3:00 AM. I could see the missed connections piling up in the queue, thousands of data queries dropping into the void and triggering SLA financial penalties by the minute. The software dashboards provided by Brian’s preferred vendors were useless, returning endless loading wheels instead of raw data.

I closed the laptop screen. I put on my shoes in the dark. I drove to the office at 4:00 AM, the empty freeway offering no resistance compared to the network I was about to fight.

The noise in the server room was a physical wall. The industrial HVAC units were firing at maximum capacity, trying to pull heat out of racks that were generating it faster than the physics of the room allowed.

I called Brian on speakerphone, setting my device on the crash cart so I could use both hands on the physical terminal. I told him I was pulling the physical power array on the secondary clusters to force a hard reset and clear the rogue processes. “Absolutely not,” his voice came through the tiny speaker, perfectly steady, completely devoid of the panic echoing off the metal walls around me.

“They are mission critical,” he said. I shouted over the roar of the fans that they were acting as a bottleneck, that the primary traffic was dying because the secondaries were hoarding all the compute. “Do not touch the physical power, Anna. That is a direct order. Reroute the primary traffic through the tertiary switches and find the software bug. Do your job.”

He was the Chief Technology Officer. He held the master administrative keys. If I pulled the power against a direct order, I would be legally liable for the client data loss. He knew that. He used his authority to lock me out of the physical solution, forcing me to fight a hardware fire with software tools.

I pressed the red icon on my screen to end the call. I looked through the perforated metal of the rack doors at the glowing green lights of the servers. I spent the next thirty hours sitting on the freezing floor grates, typing lines of code into a terminal, trying to save a system that had been designed to fail.

On Tuesday afternoon, with the network limping and the Performance Improvement Plan sitting unsigned on my desk, I returned to the server room.

The digital thermostat on the wall read sixty-eight degrees. It was a five-degree spike. In a room engineered to disperse massive thermal loads, five degrees is an earthquake. I walked down the cold aisle toward the backup clusters. The exhaust fans were whining at a high-pitched mechanical shriek, vibrating the floor plates beneath my boots.

I checked the physical hypervisor screens attached directly to the racks. The CPU loads on the backup clusters were pegged at ninety-nine percent. It was a Tuesday afternoon. Our backup traffic should have been dead zero. I walked out to my desk. I opened the master software access logs for the backup servers.

Empty. Wiped clean. Zeroed out by a master administrative override.

He believed his technical superiority allowed him to exploit the company without leaving a trail. He thought I was just a cable monkey who only understood what the dashboard told her.

I closed the software dashboard. I unplugged my laptop. I grabbed my blue console cable. I walked back into the server room and locked the metal cage door behind me.

I sat on the raised floor grates.

I plugged directly into the core physical switch.

I bypassed the server operating systems entirely.

I pulled the SNMP logs.

Simple Network Management Protocol is the raw packet tracker embedded in the hardware itself. You cannot wipe it without shutting down the entire building’s internet connection.

The packets flooded my screen. Millions of them.

They were not client analytics.

They were outbound requests. Routing to external IP addresses.

I ran the addresses through a global registry.

Cryptocurrency mining pools. Three of the largest in the world.

I opened a new terminal window.

I accessed the building’s industrial HVAC controllers.

I pulled the raw power consumption metrics for the cooling units over the last thirty days.

Massive electrical spikes. Peaking every night between midnight and 6:00 AM.

I cross-referenced the power spikes with the building’s physical keycard swipe logs.

Brian Wallace’s executive badge swiped into the elevator at 11:45 PM every night the power spiked.

I sat on the metal grates. The cold air blew up through the vents. The servers roared above me. My blue console cable rested on my knee. I closed the laptop screen. I unplugged the cable. I wrapped the cord around my hand, loop by loop.

I opened my laptop bag. I took out a blank, hardware-encrypted flash drive. I plugged it into my machine and exported the raw SNMP traffic data, the HVAC power graphs, and the keycard swipe logs. I ejected the drive and put it in my pocket.

I opened my email client. I drafted a single line to the CEO and the Board of Directors, carbon-copying Brian.

I am requesting five minutes to present physical infrastructure data at the all-hands post-mortem meeting.

I hit send.

I sat at my desk, watching the sent email sit in my outbox. The timestamp ticked forward. One minute. Two minutes.

My desk phone rang. It was not a reply from the board. The caller ID displayed the extension for David Evans, the CEO’s Chief of Staff.

“Anna,” David said. His voice dropped an octave, adopting the forced, measured sympathy of corporate management. “The CEO saw your request for the floor. I am calling to let you know we are denying it.”

I kept my hand resting on my computer mouse. “I have physical infrastructure logs that explain the weekend outage. The board needs to see them.”

“Brian already briefed the executive team this morning,” David said. He exhaled slowly into the receiver. “He warned us you might try to pull unverified raw metrics to deflect from the routing topology failure. He explained that hardware anomalies are standard side effects of a layer-two software loop. We need to keep the post-mortem focused on the software failure so we can satisfy the clients. We cannot have a public debate about infrastructure during an all-hands meeting.”

I looked at the blue console cable coiled on my desk. “The software logs were wiped, David. Brian wiped them. The hardware tells the truth.”

“Brian has the master logs, Anna,” David said softly. “He is the Chief Technology Officer. He holds the administrative keys. Please, just attend the meeting. Take notes. Do not make this harder than it needs to be.”

He hung up. The dial tone hummed in my ear, a flat, dead frequency. I set the receiver back into the cradle. The plastic clicked into place.

I leaned back in my ergonomic chair. I looked at the blinking green lights of the floor switch mounted on the far wall. For six months, I had watched the signs. I had documented the anomalies. And I had chosen to categorize them as executive incompetence. I saw him pry open a biometric security key with my crimping tool. I watched him claim a million dollars of backup compute for his undefined testing parameters. I noticed the ambient temperature in the server room rising by fractions of a degree every single week. I saw the power draw creeping upward on the HVAC graphs.

I saw all of it. I chose to believe he was just an arrogant manager who did not respect the metal. I justified my silence by telling myself my job was to maintain the cables, not to police the CTO. I let him build his parasite inside my network because I trusted the corporate hierarchy more than I trusted my own temperature readings. I gave him the benefit of the doubt, and he used it to mint cryptocurrency while my servers burned.

The all-hands post-mortem was scheduled for 2:00 PM in the primary boardroom.

At 1:50 PM, I walked down the main executive corridor. The hallway was lined with floor-to-ceiling glass, offering a clear view into the staging area outside the boardroom doors.

Brian Wallace stood next to the catering table. He was holding his brushed steel, temperature-controlled coffee mug. He was speaking to Marcus, our lead software developer. Marcus breathed rapidly, clutching a stack of printed dashboard reports against his chest.

Brian was entirely relaxed. He shifted his weight, took a slow sip from his mug, and placed a hand on Marcus’s shoulder.

“Just stick to the presentation track, Marcus,” Brian said. His voice carried clearly through the open glass door. “I’ll handle the topology explanation. It’s a classic layer-two failure. The board just needs to see the software breakdown. It’s an open-and-shut case.”

Marcus nodded quickly, his eyes darting toward the boardroom.

“And Marcus?” Brian added. He swirled the coffee in his metal mug. “Make sure Anna has a seat near the door. She is already on a Performance Improvement Plan. Having her infrastructure blamed publicly in front of the CEO is going to be difficult for her. We should give her an easy exit when it gets to be too much. It’s the compassionate thing to do.”

Brian smiled. It was a perfectly calm, generous smile. He took another sip of his coffee. He believed the digital world belonged to him. He believed his administrative override was absolute, and he believed I had no weapons left to fight him.

The boardroom presentation system ran on a proprietary wireless casting protocol. Anyone with executive privileges could override the screen. Brian had already locked the digital queue to his own tablet. He had secured the software.

I did not walk into the boardroom.

I turned left, down the narrow, uncarpeted hallway that led to the AV control closet. The door was locked. The physical key mechanism matched the master server room key on my belt. I unclipped my keyring. I inserted the brass key and turned it. The heavy lock disengaged.

The closet smelled of warm dust and ozone. I stepped inside and turned on the overhead fluorescent light. Bolted to the wall was the main HDMI matrix switch, the physical hardware that routed the video feeds to the massive projector hanging from the boardroom ceiling.

I set my laptop on the metal utility cart. I unzipped my bag and took out the hardware-encrypted flash drive containing the raw SNMP traffic and the HVAC power graphs. I plugged it into my machine.

I reached up to the wall rack. I found the input port labeled ‘WIRELESS RECEIVER 1’. I gripped the thick plastic housing of the connector. I pulled it out. The wireless feed was dead.

I pulled a fifty-foot HDMI cable from the backup spool on the wall. I plugged one end directly into the master hardware feed on the matrix switch. I plugged the other end into my laptop.

My screen flickered. The digital lock was bypassed by physical copper.

I picked up my laptop with my left hand. I gripped the thick black cable with my right hand. I kept the connection tethered, unspooling the slack from the wall as I backed out of the AV closet. I turned toward the boardroom doors.

I pushed open the heavy oak doors of the primary boardroom. The room was designed to seat thirty executives, and it was at full capacity. The air conditioning was set to a comfortable, climate-controlled seventy degrees, a stark contrast to the freezing, high-velocity wind of the server cage.

I held my laptop in my left hand. A thick, black HDMI cable trailed behind me. It ran across the carpeted floor, out the doors, and down the hallway, physically tethering my machine directly to the building’s master matrix switch in the AV closet.

Brian Wallace was standing at the head of the long mahogany table. He held a black dry-erase marker. He had drawn a complex, looping diagram on the whiteboard, explicitly labeling the failing nodes with my team’s routing designations. To his right, a one-hundred-and-twenty-inch projection screen displayed a pristine, color-coded software dashboard. It was a simulation of the weekend outage, entirely sanitized and scrubbed of any raw hardware data.

“The failure cascaded through the secondary nodes,” Brian was saying, tapping the marker against the board to emphasize his point. “Because the physical infrastructure team failed to terminate the redundant pathways. It is a textbook layer-two topology loop. The hardware is entirely fine. It simply followed a flawed map.”

He paused. He picked up his brushed steel coffee mug from the podium and took a slow sip.

“I have already initiated formal disciplinary protocols for the sysadmin team,” he said smoothly, looking toward the CEO. “We cannot afford this level of fundamental incompetence when handling client analytics. The board has my assurance that the network topology will be redesigned under my direct supervision.”

He was firing me. He was standing in front of the executive board, using my professional reputation as a heat shield to protect his theft.

I walked to the empty chair at the far end of the long table. The heavy HDMI cable dragged against the carpet with a dull, continuous static sound. Heads turned. I did not apologize for the interruption. I set my laptop down on the polished wood.

I pressed the enter key to execute the display override.

The proprietary wireless casting receiver was instantly bypassed by the hardwired copper connection. The massive projection screen went black for a fraction of a second.

Then, it illuminated with the raw command-line interface of the core physical switch.

There were no color-coded graphs. There were no management summaries. There was only a black background with rapidly scrolling white text. Millions of packets, updating in real-time, completely unredacted.

Brian stopped talking. He lowered his coffee mug. He looked at the screen, then down at his tablet, swiping his thumb in a rapid, frustrated motion to refresh his locked feed.

“Anna,” Brian said. His voice was sharp, carrying the practiced, heavy authority of an executive interrupted by a subordinate. “We are in the middle of the software post-mortem. Cut your feed. We are not reviewing raw packet dumps today.”

“Those are the SNMP logs from the core switch,” I said. My voice did not shake. The professional container of my discipline held the anger perfectly in check. “They are showing continuous outbound traffic to three external IP addresses.”

David Evans, the Chief of Staff, had been scrolling through his phone, actively ignoring the technical presentation in favor of his email. His thumb stopped moving. He looked up at the scrolling white text on the massive screen, then turned his head slowly to trace the thick black cable running from my laptop, across the floor, and out the door. He placed his phone face-down on the table. He did not ask me to leave.

Brian took a step away from the whiteboard. He gripped his marker tightly. The casual relaxation was gone from his shoulders. “That is unverified packet data. It is an artifact of the dynamic stress testing I authorized on the secondary clusters. Turn the screen off, Anna.”

I pressed the right arrow key on my laptop.

The screen switched from the scrolling text to a stark, high-contrast bar graph.

“This is the raw power consumption data from the industrial HVAC units in the server room,” I said. “The power draw spiked by four hundred percent every night between midnight and six in the morning. The company has paid over forty thousand dollars in excess electricity this month to cool backup servers that were running at maximum compute.”

I pressed the arrow key one final time. A simple, indisputable spreadsheet appeared on the screen.

“And these are the building’s physical keycard logs,” I said.

The spreadsheet showed one name, one badge ID, and a repeating timestamp: Brian Wallace. 11:45 PM. Every single night for the past thirty days.

Marcus, the lead software developer, had been holding a thick stack of printed dashboards against his chest, standing by the wall ready to support Brian’s topology theory. His arms went slack. The glossy papers slid from his grasp and scattered across the polished mahogany table, spilling onto the floor. He did not try to pick them up. He stared at the keycard timestamps.

Brian looked at the CEO, Robert Vance, who sat at the center of the table. Brian’s posture shifted entirely. He abandoned the technical defense and moved instinctively to executive hierarchy.

“Robert, this is a gross violation of security protocol,” Brian said, his voice rising in volume. “She physically bypassed the AV matrix. She is currently on a Performance Improvement Plan and she is retaliating with manipulated hardware metrics because she doesn’t understand the software layer.”

I did not look at the CEO. I did not look at the board. I looked directly at Brian.

“It wasn’t a routing loop, Brian,” I said. The facts required no elevation in volume. “You didn’t find a configuration error. You melted the servers mining Bitcoin.”

Robert Vance had been leaning back in his leather chair, observing the presentation with a detached calm. He unclasped his hands. He leaned forward, resting his forearms heavily on the edge of the table. He stared directly at the keycard timestamps on the screen, then shifted his gaze to the massive spikes on the HVAC power graph. He reached out and deliberately closed the cover of his notebook.

The silence in the room was absolute. There were thirty people present, and the only sound was the faint, steady hum of the projector fan overhead. The corporate hierarchy, the sanitized software dashboards, the executive protection—none of it could argue with the raw physics of heat and power displayed on the wall. The institutional mechanism had been presented with undeniable, physical theft.

Robert Vance stood up. He did not raise his voice. He did not express outrage. He invoked the institution.

“Brian,” Robert said. “Place your corporate badge and your tablet on the table.”

Brian stood perfectly still. He looked at the white text on the black screen. He looked at the black cable tethering my laptop to the wall. He opened his mouth to speak, to offer another layer of technical obfuscation, to claim the data was flawed, to try and leverage his title one last time.

“Now,” Robert said. The word was flat and final.

Brian reached into his pocket. He pulled out his executive badge lanyard. He unclipped his company tablet from his belt. He set them both on the mahogany wood. He did not look at me. He did not look at the engineers he had publicly blamed moments before. The arrogance that had allowed him to pry open security keys and claim millions of dollars of hardware as his own personal sandbox simply evaporated, leaving nothing behind but a man standing next to a whiteboard.

“This is a mistake,” Brian said.

It was a hollow, quiet sentence. It was not a defense; it was just the only thing left to say.

He turned and walked toward the heavy oak doors. Two men from corporate security, who had been standing by the catering tables in the hallway, stepped forward and flanked him immediately. They escorted him down the glass-lined corridor. The heavy boardroom doors clicked shut behind him, sealing the room.

The executive board did not ask me to stay for the remainder of the meeting. Once the corporate security detail removed Brian from the floor, I disconnected my HDMI cable from the matrix switch. I rolled the thick black cord back into a tight coil, returned it to the plastic spool in the AV closet, locked the door, and walked back to the basement.

The quiet atmosphere of the executive corridor transitioned back into the mechanical roar of the server cage.

I unlocked the metal door and stepped onto the raised floor grates. The company would eventually recover the stolen electricity costs through civil litigation. They would hire a new Chief Technology Officer who would bring a new suite of software dashboards. Human Resources would quietly discard the Performance Improvement Plan sitting on my desk.

None of that repaired the physical damage in front of me.

I stood in front of the backup clusters. I bypassed the terminal and reached directly for the master power distribution unit. I gripped the heavy plastic breakers and pulled them down. The massive exhaust fans spooled down immediately, their high-pitched shriek descending into a low, dying rattle before stopping completely. The sudden absence of sound in the cold aisle was heavy.

I unlatched the back panel of the rack and pulled it open. The heat hit my face instantly. It was not the clean, ambient warmth of a functioning machine. It smelled of ozone, melting copper cladding, and degrading thermal paste. The processors had been running at maximum capacity for weeks without a break. The silicon was permanently scarred.

I sat down on the floor grates. I pulled my custom crimping tool from the holster on my belt. When I first built this room two years ago, I used this heavy steel instrument to terminate the pristine blue Cat6 cables, measuring every length to the millimeter, creating a perfect, flawless nervous system for the company. The spring-loaded handles had moved with a smooth, satisfying resistance. Now, I reached into the back of the corrupted rack and clamped the steel teeth around the primary data trunk. The plastic shielding on the cables had turned brittle from the constant, unnatural heat of the mining operation. When I squeezed the handles of the crimping tool, there was no clean cut. The degraded plastic crunched and splintered under the steel. I was not building a network anymore. I was amputating dead tissue. I worked my way down the rack, using the heavy tool to sever the ruined connections one by one, dropping the burnt cables onto the metal floor beside me.

The imperfect reality was stacked in front of me. I would have to spend the next twelve months completely rebuilding the infrastructure from bare metal. The pristine network I had meticulously engineered was gone, reduced to a triage zone of compromised hardware and failing power supplies. I had stopped the parasite, but the burden of restoring the physical environment fell entirely on my shoulders.

I placed the crimping tool on the metal crash cart. I picked up a severed length of cable from the floor. The copper wire exposed at the end was blackened and warped.

Brian thought he could hide his theft in the software. He believed he could override the logs, manipulate the dashboards, and use his administrative authority to rewrite the reality of what he was doing. He didn’t understand that computing is physical, and the physics always leave a mark.

I tossed the burnt cable into the industrial trash bin. I turned back to the open rack, grabbed the next bundle of ruined wires, and started pulling.