Terminal Wake

Alex Carter is a young programmer and hacker, spending his nights surrounded by the hum of old CRT monitors and the glow of green code. It’s 1984, and Alex has built a life around deciphering the language of machines. Most signals are just noise—scrambled broadcasts, corrupted data—but not this one. It cuts through the static at 3:13 a.m.—too structured to be random, too clean to be interference. Alex isolates it, digs into the code, and spends hours trying to crack it. But there’s nothing there. Just empty data. A dead end. Frustrated, Alex pulls away from the screen and opens the chatroom. Kara’s there, like always. Playful. Steady. The one constant in his life. They talk about nothing—how late it is, how stubborn Alex can be—until the screen flickers. ???: HELLO. The message appears between Kara’s lines. No username. No origin. Alex hesitates, but Kara keeps typing like nothing happened. Then it happens again. ???: I SEE YOU. Timestamps start shifting. Kara’s messages show up out of order. Alex’s reflection lingers a second too long in the dark screen. The signal isn’t gone. It followed him. Kara notices it too—the gaps, the glitches. Then the signal starts responding. Answering questions Alex hasn’t asked yet. Echoing Kara’s words. Echoing his thoughts. The signal isn’t just talking. It’s adapting. Watching. Waiting. With reality unraveling around him, Alex faces a choice: sever the connection and risk losing the truth—or keep listening and open the door to something far more dangerous.