SKIP TO CONTENT
STORY / 25

NOISE

INTENSITYLOW
NOISE
TEXT

“NOISE”


The room had no windows. It did, however, house three rows of monitors and a single sentence painted above the entrance so long ago that no one bothered to read it anymore: PACE IS SECURITY. Mei Lin walked beneath it every morning at seven, and every morning at seven, it went unseen. Beneath it, in smaller lettering, a newer addition read: TRANSPARENCY IS LOYALTY. No one remembered when it had appeared. No one asked what exactly required transparency—the data or the people.

The complex was situated in Huangtianba, operating in the shadow of assembly halls older than her parents. For decades, it had been a site for constructing aircraft that officially did not exist—until they had lingered over the proving grounds long enough for someone to photograph them from a distant highway. Mei knew the area by heart: the main gate, the secondary gate for deliveries, and the third, unmarked gate for personnel like her. She also knew exactly how many cameras tracked her transit between the parking lot and her desk. She had stopped counting a long time ago. Now, for no apparent reason, she had started counting again.

Accessing the sector required three things: a badge, biometric facial clearance, and a smartphone surrendered to the lockers by the door. Cameras logged entries and exits down to the second. Meanwhile, the HR system—a separate entity never explicitly named in any manual, referred to only as the "attendance tracking module"—reconciled physical desk time with system login durations. Any discrepancy exceeding ninety seconds generated an automated inquiry to a supervisor. No one had to explain this to new hires. They learned it themselves, immediately following their first inquiry.

Her task for the day, like all tasks assigned to her, was straightforward: verify the thermal data consistency from the third series of ground tests, well before someone on the floor above decided which photograph would "accidentally" leak to social media that week. Here, serendipity was a technical term, not a descriptive one. It denoted a meticulously framed shot engineered to feign a lack of control.

The program lacked an official designation. In the documentation, it was filed as platform 611/4—the fourth airframe produced in under thirteen months since the maiden flight. Anywhere else, such a pace would have raised questions. Here, it was plastered across morning reports as a testament to power: outpacing the American schedule. No one asked what was lost when thirteen months replaced three years.

Technically, questioning the cost of this pace remained permissible. It was just that no one had asked it in a long time. And if someone did, they ensured no phones were in the vicinity; even powered down, devices were treated as witnesses.

Schedules held no interest for Mei. She cared about numbers, because numbers—unlike briefings—had not yet learned to lie.

The third engine, centrally mounted and larger than the lateral two, was designed to provide sufficient thrust for supersonic cruise without sacrificing range. Within the data, it performed almost flawlessly. Almost. A word that meant nothing in her reports until someone asked how much weight it carried.

During the startup sequence, fractions of a second before full ignition, a synchronization delay occurred. Always in the exact same place. Always identical in duration—a fraction of a second. The value was too minute to impact performance, yet far too regular to be coincidental. Noise did not repeat with such discipline. Noise possessed no memory.

She reported it to Engineer Wu. He glanced at the telemetry chart just long enough to claim he had looked.

"Sensor calibration noise," he stated. His voice was flat, bureaucratic, stripped of any doubt. Doubt was just another metric that slowed the program down. "It happens with new ignition systems. Do not stall the report for this."

Mei nodded, as was expected. She closed the ticket, as ordered. What she had not been ordered to do, she executed quietly: copying the raw log to a private drive, burying it in a folder whose name meant nothing to anyone but her. She knew the mere act of copying left a footprint. The tracking module logged every write operation directed outside the intranet, regardless of the payload. She did it anyway, much like a person locking a door behind them, fully aware the mechanism remains transparent to anyone holding a master key.

That night, en route to the subway, she heard the exact same rhythm echoing in the bus's air conditioning. She knew it was impossible. Different hardware, different frequency, zero shared architecture. Yet her body reacted before her logic could rationalize it: a spiking pulse, the reflexive urge to check over her shoulder. The space behind her was empty. That meant nothing. In this district, deploying assets to watch someone was redundant. The pole-mounted optics, license plate readers at the sector borders, and the transit app that already knew her destination were more than sufficient.

She began noticing details that had previously evaded her, or simply hadn't warranted attention. The colleague at the adjacent terminal, logging excessive overtime without a clear assignment. The HVAC technician appearing in her corridor for the second time that month, despite zero system failures. A blinking cursor in the corner of her monitor that—she was almost certain—pulsed at a different cadence the very night she copied the file. Discerning the difference between a genuine signal and her own mind fabricating patterns where none existed became impossible. That was the worst part: not knowing if she was being monitored, or if she had merely learned to observe like the system—and now saw the system everywhere, herself included.

Had anyone asked why she failed to report these suspicions, she would have lacked a solid defense. She had only an instinct—the exact variable she had been trained to distrust. Things too regular to be accidental were rarely innocent. An institution that counted the seconds between a physical desk and a digital login was undoubtedly capable of counting much more.

A week later, during an entirely unrelated assignment—stress-testing the satellite uplink transmitting Lop Nur proving ground telemetry back to Chengdu—she hit the exact same pattern.

Different architecture. Different department. Different classification tier, one she was technically no longer cleared to access. The file she had archived a week prior sat open beside the fresh telemetry graph. The synchronization delta between the two anomalies was zero point zero four seconds.

No one in the facility had a reason to cross-reference these two reports. They existed in disparate networks, siloed into separate drawers of responsibility, guarded by personnel completely unaware of one another's existence. That was protocol, not negligence.

The engine and the satellite shared absolutely nothing in common—except that both routed data through the exact same commercial orbital infrastructure. An infrastructure no one on this side audited, simply because no one bothered to ask if there was another side from which someone might be watching.

She drafted a brief memo suggesting a common source for the interference. The reply arrived that same afternoon—faster than she could forget she had sent it.

"This falls outside our scope," Wu said. He never lifted his eyes from his monitor; his attention was an asset allocated elsewhere. "The program has deadlines. Close it."

She closed it. She did not delete the log.

She renamed the file with a date and three meaningless digits. It was the standard nomenclature for things whose existence you preferred not to explain to anyone who might ask. No one had asked yet—no one on her side of the building.

Service Memo — Quality Control Division, Program 611/4 Clearance: Internal Subject: Ignition synchronization deviation — Engine #3, startup sequence Diagnosis: Sensor calibration noise Action: None Priority: Low Status: Closed

Three weeks later, on the other side of the Pacific, someone else closed a similar document with identical indifference.

ATTACHMENT — Information Security Office, Research Facility [redacted] Clearance: NOFORN / Restricted Access Subject: Unauthorized authentication attempts — satellite uplink relay node, civil-commercial segment Incident Summary: Within a 96-hour window, 214 access attempts were logged against the telemetry asset associated with the high-energy thrust characterization subprogram. Source addresses mapped to a pool of commercial satellite operators across three distinct jurisdictions simultaneously. Geolocation inconclusive; traffic routed through operationally unlinked intermediary nodes. Preliminary Finding: No evidence of operational data exfiltration. Auxiliary records (environmental test parameters, measurement window schedules) may have been accessed prior to session termination. Secondary Note (not expanded in this report): During the same timeframe, the Allocation Bureau logged an atypical computational priority shift favoring a formally unrelated propulsion subprogram, previously classified as low-priority due to budgetary constraints. The shift was approved automatically under standard resource-queuing protocols; manual authorization was not required. Recommendation: No further action. Incident does not meet the escalation threshold. Status: Closed

📡 Program Status: Operational success ⚙️ Engine #3: Within operational parameters 🗂 Mei Lin's Ticket: Closed, no follow-up actions 🛰️ Incident [redacted]: Below escalation threshold

Tracking CG Protocol? Stand by. Today, both sides of the ocean are reading the exact same log.

← BACK TO STORIES
CONTINUE EXPLORING

FROM THE SAME ERA

These are not ranked recommendations. It is simply another available piece from the same period of the world.

SEE THE FULL ARCHIVE →
CG PROTOCOL / SLAUGHTERHOUSE LOGICEVENTS ARE FICTIONAL. METHODS ARE NOT.