The target was Falcon Capital, a rival firm. Corrigan wanted their systems offline for exactly forty-seven minutes—long enough to execute a series of trades before Falcon's arbitrage bots could react. Illegal. Irreversible.

Corrigan's face went red. "What did you just—"

Maya stared at the blinking cursor on her terminal. The script was ready—427 lines of Python, elegant in its destructive purpose. Three years of building reputation as a red-team specialist, and now a single decision could erase it all.

"The script is gone," Maya said, standing up. "So am I. And if you ever come near my family again, I'll forward your encrypted emails to every regulator in the city."

Instead, she typed:

Maya had written the script as a thought exercise, a proof-of-concept she'd promised herself to never deploy. It used randomized user-agent strings, rotated proxies from a botnet she didn't want to know the origin of, and layered attacks at the application layer—slow and low, then volumetric. Hard to trace. Harder to stop.

def ethical_fail(): print("System integrity check failed.") print("Operation aborted.") sys.exit(1) She saved the file as failover.py and overwrote the original.

She walked out into the rain, heart pounding, wondering if she'd just saved her career—or ended it.

"Forty-seven minutes," Corrigan repeated. "That's all."

She chose neither.

The terminal stayed dark. The packets never flew. And somewhere, a trading platform kept running, unaware of the forty-seven minutes it would never lose. Moral of the story? The most dangerous line of code isn't the one that breaks systems—it's the one you choose not to write.

Her stomach tightened. Her mother's chemo. The debt. The job offer from Corrigan three months ago, too good to refuse.

Elegant , she'd thought when she wrote it. Now it felt like a loaded gun.

"Because you're the best. And because I know about the medical bills."