The screen flickered. For a split second, Singh saw something that wasn't a login prompt—a grainy black-and-white image of a corridor he didn't recognize, lined with five empty chairs. And in the sixth chair, a figure in an ISF uniform, head tilted back, eyes open.
He turned back to his terminal. The screen glowed with the words:
Singh reached for the red phone. But before his hand touched the receiver, a new message appeared on his screen:
Singh sat back. His pulse hammered against his ribs. He glanced at the clock: 03:51. The shift log showed nothing out of the ordinary. His own login timestamp read 00:00—clean. isf watchkeeper 4 login
He typed slowly, almost unwillingly:
Through the static, a low, rhythmic thrum —too slow for a heartbeat, too regular for wind. Then a sound like stone grating on stone. Then nothing.
But every night since, at 03:47, his token fob flashes 000000 for exactly one second. And every night, he logs in anyway. The screen flickered
The screen went dark. Then, in tiny gray letters at the bottom corner:
> UNEXPECTED QUIET DETECTED. ZONE 7 THERMAL SHADOW. LOG CONFIRMED.
> ISF WATCHKEEPER 4 // LOGOUT
> WATCHKEEPER 4: DO NOT ESCALATE. REPEAT: DO NOT ESCALATE. AWAIT GREEN CONFIRMATION.
He never mentioned it to the Major. And two weeks later, when they found Node 14's backup storage corrupted beyond recovery, he signed the report without comment.