Arthur frowned. "Temporal?" he muttered. He checked the BIOS clock. It was correct. He checked the NTP server. Also correct. He tried to close the window with Alt+F4. No response.
Nothing happened.
He clicked again. The box didn't close. Instead, the text changed. Arthur frowned
The error box grew. It stretched across both monitors, then flickered and began to display a command prompt window behind it—a ghost of a terminal that wasn't supposed to be there.
Then it happened.
Another buzz. His boss: "Why is the mainframe sending UDP packets to a Microsoft IP in Redmond? That building was demolished in 2023."
01101001 01101100 01101100 01100101 01100111 01100001 01101100 — ILLEGAL It was correct
The server room door slammed shut. The keycard reader sparked and died. The overhead fluorescents began to flicker in a binary pattern. Arthur squinted.
System: Windows Server 2008 R2 (Standard) User: Arthur P., Senior Systems Architect He tried to close the window with Alt+F4
A metallic CLICK echoed from the server’s speakers. The screen flickered, not with a standard Windows error chime, but with a low, guttural thrum —like a diesel engine coughing.
Arthur's phone buzzed. A text from the night security guard: "Art, the lights in the south wing just turned off by themselves. Also, all the printers started printing the same page. Just one word: 'ACTIVATE.'"