The basement hummed at forty-eight degrees Celsius when Ivy saw it.
Not the temperature readout on her wall-mounted sensor—though that number had begun its slow, patient climb about six minutes ago. She saw it in the code itself. A line of logic that did not belong. A subroutine nested three layers deep in the financial audit system, written in a dialect she recognized the way you recognize someone's handwriting in a crowded room. Deliberate. Specific. Designed to fail.
She pulled up the cascade map on her center monitor. The saboteur had woven the corruption through every connected server like a fuse. When the audit system ran its scheduled 2 AM job—which was in eighty-eight minutes—it would trigger a heat loop. Each server would push its processing load to the next, which would push back harder, which would push back harder still, until the entire network was screaming and the room itself became an oven.
Fifty degrees now.
"Okay," Ivy said to no one, because no one was here at 11:34 PM on a Wednesday in a basement that smelled like ozone and dust. "Okay, okay, okay."
She ran her fingers across three keyboards simultaneously, a gesture that looked like chaos but was actually the only way she could keep pace with what the saboteur had built. The code was elegant in its malice. Whoever had written this knew the system's architecture the way a surgeon knows anatomy. This was not a break-in. This was someone who had been inside for a long time.
The failsafe appeared on her secondary monitor. Every saboteur plants a kill-switch—a line of code that can halt the cascade if you know where to look and what to ask for. She found it in the audit system's error-handling protocol, disguised as a logging routine. One command. Twelve characters. She could execute it in three seconds and save everything.
She read the code beneath it.
The failsafe was not just a halt. It was a frame. Running it would dump a false audit trail onto the junior developer's workstation—Marcus, twenty-three years old, six months into his first real job. The evidence would make him look like the saboteur. It would be perfect. It would hold up. It would be wrong.
Fifty-three degrees.
Ivy stood up from her desk and walked to the wall where she had printed the system architecture six months ago. It was covered now in notes and annotations, a map of every connection she had been tracking. She had been looking for financial irregularities in the city's housing authority. Someone had been redirecting funds meant for repairs in low-income neighborhoods. She had almost found the name. Almost.
Now someone was burning it all down rather than let her finish.
She turned back to her monitors. The temperature sensor ticked upward. Fifty-five degrees. The servers were beginning to work harder now, the cascade not yet active but the saboteur's preparation code was already running, warming things up like an engine before the real acceleration.
Her phone buzzed. A message from an unknown number: "Walk away. You're close to things that don't want to be found."
Ivy almost laughed. Almost. Instead, she set the phone face-down and pulled up the personnel files for everyone with access to the audit system. Forty-two people. She began cross-referencing against the saboteur's code signature—the particular way they structured loops, named variables, handled error states. Every programmer writes like they fingerprint. You cannot hide it if someone knows how to read it.
Fifty-eight degrees.
The first match appeared at beat seventy-three. She recognized the code style from a budget reconciliation system she had cracked three years ago. The programmer had been efficient, almost obsessive about clean execution. She pulled the personnel file.
David Reeves. Department director. Fifteen years with the city. Married. Two kids. He had motive—she had found the housing authority irregularities three weeks ago, and the first person she had flagged was someone in his department. Not him. But someone who reported to him. Someone he had hired.
Sixty-one degrees.
The server whines were getting higher now, a sound like the room was learning to scream. Ivy's fingers moved across the keyboards, but not toward the failsafe. She was building her own command sequence. A data extraction protocol that would copy only the evidence that was already documented, already backed up, already clean. It would save maybe forty percent of what she needed. It would take forty-seven minutes.
She would have maybe thirty minutes before the cascade reached critical failure.
Sixty-four degrees.
She thought about Marcus in his cubicle upstairs, probably asleep, probably dreaming about something that had nothing to do with code or frames or the way people who are afraid will burn down entire systems to protect themselves. She thought about David Reeves, who had probably thought this would work. Who had probably thought that destroying the evidence would destroy the investigation, and with it, the exposure of what he had done or allowed to happen.
She thought about the families in those low-income neighborhoods. About the repairs that had not been made. About the reason she had taught herself to code in the first place—not for the thrill of breaking into systems, but because systems were where power lived, and power needed witnesses.
Sixty-seven degrees.
Ivy's extraction protocol was forty percent complete. The failsafe command sat on her screen, twelve characters waiting to be executed. Three seconds. Everything saved. One innocent person destroyed.
She reached for the keyboard. Her hand hovered. The servers sang their high, distressed pitch. The room was getting visibly warm now, the air itself shimmering slightly above the equipment racks. She could feel the heat on her skin, the way it was beginning to move from uncomfortable to dangerous.
She pulled her hand back.
Instead, she stood and began physically removing hard drives from the backup server—the one that held the cleanest copies of her documentation, the evidence that had no fingerprints on it except her own. Each drive was warm to the touch. She placed them in a fireproof case and sealed it. Forty-seven drives. The investigation would continue, but slowly. Incompletely. With gaps that David Reeves might exploit.
Seventy degrees.
The extraction protocol finished. Ivy did not execute the failsafe. She simply let the cascade run.
The servers screamed for eight minutes, then went quiet. The room continued to warm for another three, reaching seventy-three degrees before the thermal shutdown kicked in and everything went dark except for the red emergency lights and the faint glow of her laptop's battery indicator.
She sat in the basement as it cooled. The temperature dropped slowly, degree by degree, the air gradually releasing the shape of what had just burned away. The silence was different from the silence before. It was a silence that had something inside it—not regret, exactly, but the weight of a choice that was not the same as winning.
When the room reached fifty degrees again, Ivy picked up the fireproof case and climbed the stairs toward the surface, carrying what remained.
