Leo typed a reply. Deleted it. Typed again. Deleted.
That was the night Elena left.
He’d typed the command on a whim, a reflex from his early IT days. The system spat back the description: The network connection was aborted by the local system.
The logs didn’t lie. His system—his choice —had terminated the connection. The local system, indeed. net helpmsg 2250
The network connection was aborted by the local system.
Leo minimized the terminal and opened a folder he hadn’t touched in months: /home/leo/archive/elena/ . Inside were photos, shared playlists, scans of handwritten notes she’d left on the fridge. He clicked on a voice memo. Her laugh filled the room—bright, unguarded, from a camping trip three summers ago.
He closed the laptop. The screen went dark. The local system had finally learned: some connections shouldn’t be aborted. Some errors can only be fixed by walking out the door. Leo typed a reply
"I’m leaving the terminal. Give me twenty minutes."
He stared at those words until they blurred. Then, slowly, he typed a new command—not a system call, but a message to Mia:
He remembered the argument—or rather, the silence that swallowed it. She’d stood by the door, suitcase in hand, and said, "You’re more present in that screen than you’ve ever been with me." He’d opened his mouth to respond, but the network monitor on his second screen had flashed red. A critical node went down. He turned to fix it. Deleted
Leo leaned back, the cheap office chair creaking. Two years ago, that error would have sent him into a frenzy of diagnostics—checking cables, resetting adapters, tracing packet loss. Now, it felt like a verdict.
He closed it fast, heart pounding.
He didn’t reply. Instead, he pulled up the old server logs from the night everything changed. Timestamps scrolled past. 23:14:02 — connection established. 23:14:09 — connection aborted. Local system. Not a remote failure. Not a hacker. His own machine had pulled the plug.
By the time he looked up, she was gone.