The notification came in at 22:47, which was not unusual. What was unusual was the subject line.

*Rail Hero Kai spotted at Aureon Bay Central Maintenance Hub — new sighting??*

Kai Arven read it twice, set his phone face-down on the console, and returned his attention to the signal diagnostic running on Monitor Three. The diagnostic had been running for eleven minutes. It would run for another four. In those four minutes, he did not need to think about the notification, the fanpage, or the particular flavor of mild dread that the words *Rail Hero* produced somewhere in the vicinity of his jaw.

He had been called worse things. He had been called better things too, but those tended not to stick.

The maintenance hub for Aureon Bay’s high-speed rail system occupied the eastern edge of the city’s port district, in a building that had been functional before it had ever been designed. Three floors of signal monitoring equipment, maintenance scheduling systems, and the particular accumulated clutter of an operation that ran continuously and had no time to clean up after itself. Kai’s workspace was on the second floor: a desk, two monitors, a chair that had been ergonomically correct when it was new and had since developed its own opinions, and a window that faced the bay.

The bay at night was one of the few things about Aureon that Kai considered straightforwardly good. The lights of the port reflecting on the water. The long curve of the sea bridge carrying its freight of headlights. The sense of things in motion, purposeful and unhurried, the machinery of the city doing what it was supposed to do.

He found it easier to think near water. He had never examined this preference too closely.

Monitor Three finished its diagnostic. Kai leaned forward.

The signal anomaly he had been tracking for the past three shifts had not resolved. It appeared in the same location each time: a forty-meter stretch of the Starline test corridor, the dedicated section of track that the overnight sleeper service used for its trial runs between Aureon Bay and Narae City. The anomaly was not large — a variance of 0.3 milliseconds in the timing sequence, well within the range that automated systems flagged as non-critical. The kind of thing that generated a yellow indicator rather than a red one. The kind of thing that got pushed to the bottom of the queue.

Kai had been pulling it back to the top of the queue for three shifts now, because 0.3 milliseconds in a timing sequence was only non-critical until it wasn’t, and because he had a specific, trained distrust of anomalies that repeated themselves without escalating. Systems that were going to fail catastrophically often announced themselves this way: quietly, persistently, in a register that the automated monitoring was designed to ignore.

He knew this from experience. He preferred not to think about the experience.

“You’re doing the thing again,” said Pren from the next desk.

Kai did not look up. “What thing.”

“The staring at the anomaly thing. The ‘this is fine but also nothing is fine’ thing.” Pren spun his chair a quarter turn. He was twenty-four and had been at the hub for eight months and had developed, in those eight months, a reasonable working model of Kai’s behavioral patterns. “The Rail Hero Kai is sensing danger thing.”

“Don’t,” Kai said.

“There’s a new post on the fan —”

“I know. I got the notification.”

“They got a picture of you coming out of the parking structure. It’s actually a good photo, you look very —”

“Pren.”

Pren stopped. He had also developed, in eight months, a reasonable working model of when to stop.

Kai pulled up the anomaly data on Monitor Two and ran a side-by-side comparison with the signal logs from the previous two nights. The variance appeared at the same point in the timing sequence each time, within a margin of error small enough to be meaningless unless it wasn’t. He exported the comparison to a new file, attached it to the incident report he had already filed twice without response, and filed it a third time with a subject line that he rewrote four times before settling on something that conveyed urgency without sounding like he was overreacting.

He knew how overreacting was received in this building. He had learned that too, two years ago, in a way he was not going to think about tonight.

At 23:30, his supervisor Gant came through on the way to the break room, paused behind Kai’s chair, and looked at Monitor Two for approximately four seconds.

“Still on the Starline anomaly?”

“Third night in a row.”

Gant made a sound that was not quite a word. “It’s point three milliseconds, Arven.”

“It’s point three milliseconds every night in exactly the same place.”

“Starline’s engineering team has signed off on the corridor.”

“Starline’s engineering team didn’t flag it in the first place.”

Gant made the sound again. It conveyed, without committing to, a range of positions from *you might have a point* to *this is not my problem at 23:30*. He went to the break room. He came back with coffee. He did not stop at Kai’s desk again.

Kai worked until midnight. He was scheduled until 06:00 but had learned, after two years, that working through the night without purpose was different from working through the night with one. He had purpose until midnight. After that he had maintenance logs to review, which was a different thing.

At 00:23, he went to check the Starline corridor in person.

This was not in his job description. His job description covered signal monitoring, maintenance scheduling, and fault documentation. It did not cover walking the test corridor at half past midnight to look at a stretch of track that had generated a non-critical variance three nights running. He did it anyway, because he was the kind of person who needed to see the physical thing, not just the data the physical thing produced. Because in his experience, the data and the thing were not always telling the same story.

The Starline test corridor branched off the main Aureon Bay line at the southern junction, running parallel to it for two kilometers before rejoining at the coastal interchange. At this hour it was empty and dark, lit only by the low-level maintenance strips along the track bed, casting everything in a dim amber that made the rails look older than they were.

Kai walked the forty-meter section. He crouched down at the midpoint and looked at the rail-side signal sensors — small grey boxes bolted to the track bed at regular intervals, their indicator lights the steady green of systems functioning within normal parameters. He ran his gloved hand along the sensor housing. Nothing visibly wrong. Nothing audibly wrong. The rails were clean, the fasteners correctly torqued, the bed material undisturbed.

He was standing up when the control panel at the section’s midpoint lit up.

Not amber. Not red. Blue — a thin, bright pulse of blue light along the panel’s status strip, there and gone in less than a second, like a camera flash from somewhere inside the system. The panel’s normal indicators remained green throughout. The blue light appeared in no documented status color for this equipment.

Kai looked at the panel for a moment.

Then he reached for the manual override. The override was a physical switch, a failsafe built into every signal control point on the network, designed to allow immediate disconnection from the automated system in case of emergency. You were supposed to use it only in emergencies. Kai used it now because a light that was not in the documentation was the kind of thing that qualified, in his personal taxonomy, as an emergency regardless of what the automated system thought.

He threw the switch.

The panel discharged.

It was not a large discharge. The emergency interruption of a signal circuit produced a brief electrical release — this was documented, expected, the reason the override switches had insulated handles. What was not documented was the way the discharge traveled up the insulated handle anyway, through his glove, into his palm, up his forearm. A current that should not have been strong enough to feel. A current that felt, distinctly and inexplicably, like a frequency.

Not pain. A frequency. Like a very low note finding resonance in the bones of his hand.

It lasted less than two seconds. The panel reset. The indicator lights ran through their restart sequence and settled back to green. The blue was gone as if it had never been.

Kai stood in the amber-lit corridor with his right hand slightly raised.

He lowered it. He removed his glove and looked at his palm: no burn, no mark, the skin exactly as it had been. He put the glove back on. He pulled out his phone and documented the incident with the precision of someone who had learned that precision was the only thing that stood between an observation and a story nobody believed: time, location, duration of anomalous light, nature of discharge, physical effect, absence of visible damage to equipment or personnel.

He filed it as an addendum to the incident report.

He walked back to the hub.

Pren had gone home by the time he returned. The second-floor workspace was quiet, only Kai and a maintenance tech on the far side of the room who was working through a backlog of calibration records and paying no attention to anything else. Kai sat at his desk and stared at Monitor Two for a long time without seeing it.

The frequency. That was the part he kept returning to. Not the blue light, which could be a fault in the status display circuitry. Not the discharge through the insulated handle, which could be an anomalous grounding issue. Those had explanations, or at minimum had categories of explanation. The frequency was different. The frequency had felt like communication.

He did not write that in the incident report.

At 02:15, still at his desk, Kai fell asleep.

He did not intend to. He was reading calibration records and then he was not reading calibration records, and the transition between those two states had no perceptible boundary. One moment the monitor was in front of him. The next moment there was a train.

Not a high-speed rail train. Not anything from the Aureon Bay network. A different kind of train entirely — longer, darker, its carriages the deep black of something that had absorbed so much darkness it had become it. The windows did not show interiors. They reflected the sky, and the sky was full of stars in a density he had never seen outside of long-exposure photographs, stars so numerous they seemed less like individual lights and more like a texture, like the dark was cloth and the stars were what the cloth was made of.

He was standing on a platform.

Across a set of tracks, there was another platform. And on that platform there was a woman.

He could not see her clearly — the starlight was sourceless and diffuse, falling from everywhere at once and illuminating nothing with precision. She was slight. She was wearing something white, a coat or a jacket, the kind of thing that caught light even when there was not much light to catch. She was standing very still, and she was looking at something — the tracks, or the distance, or some middle point between the two — with the focused attention of a person who was trying to hear something over a great deal of background noise.

Kai watched her.

He had the sense, which he could not account for, that she had been here before he arrived. That she was the constant in this place and he was the variable. That if he spoke, she would not be surprised.

He opened his mouth.

She turned.

Her face was still unclear, still blurred by the wrong light, but she turned toward him with the speed of someone who had been waiting for exactly this. And what he saw in the half-second before the train came — the black train, arriving from nowhere, its windows full of reflected stars, passing through the station without stopping and taking the air with it as it went — was not her features but her expression.

Alert. Tired. Precise in the way of people who had trained themselves to notice things.

The expression of someone who was, in some other life, responsible for keeping people alive.

The train passed. The platform was empty.

Kai sat up at his desk with his hand braced against the console, catching himself before he could tip the monitor. The hub was quiet. The maintenance tech on the far side of the room had not noticed. The clock on Monitor Two read 02:38.

He sat still for a moment, his breathing evening out.

The woman in the white coat. The platform across the tracks. He had the same feeling he always had when he woke from a dream that left a residue — not the dream itself, which was already fragmenting, but the shape of it. The space it had occupied. The particular quality of having been somewhere real.

He opened his incident report and looked at it for a long time.

Then he opened the notes field and typed, without thinking too carefully about it: *Does the girl in the white coat know how to wake the dead?*

He read it back. He deleted it.

He reopened the notes field. This time he typed: *Anomalous frequency in discharge — subjective experience of resonance in hand, approximately 1.8 seconds. No objective correlate identified.*

That was the correct way to document it. That was the version that belonged in a report.

He filed it and went back to the calibration records.

The bay outside his window was dark and still, the port lights steady on the water. Somewhere across it, the coastal interchange marked the point where the Starline test corridor rejoined the main line. The signal at that junction had been green all night.

Kai looked at it for a moment before he turned back to his screen.

His right hand, resting on the keyboard, held a faint memory of a frequency he could not explain and could not stop thinking about.

At 03:00, his phone lit up with a new message from the number he had been ignoring for two weeks.

Liora Vale. Fan account manager, self-described. Regular sender of messages that ranged from the mundane — *new photo set dropping Friday, just to let you know* — to the inexplicable — *don’t take the overnight train if you can help it, something is wrong with the 00:17*. He had never responded to any of them. He had not blocked her either, which he had examined occasionally as a fact about himself without reaching a conclusion.

Tonight’s message was different from the others. It was shorter, for one thing. And it contained, embedded in its text, a nine-digit alphanumeric code that Kai recognized immediately as a Starline internal signal routing identifier. The kind of code that appeared in maintenance documentation and engineering handoffs and nowhere else. The kind of code that a person running a fan account had no legitimate means of obtaining.

*Don’t trust the sleep corridor. If you hear the 00:17 whistle in a dream, you’re already inside it. — Liora. P.S.: SL-TRK-004-NB is the section you’ve been watching.*

Kai read the message three times.

SL-TRK-004-NB was the section identifier for the forty-meter corridor he had walked tonight. The stretch where the anomaly repeated. The panel that had lit up blue.

He typed: *Where did you get this code?*

He did not expect an answer at 03:00. He got one anyway, thirty seconds later.

*My brother worked on the trial run. He hasn’t woken up since.*

Kai set his phone down carefully on the console.

Outside, the bay was still. The port lights held their positions on the water, steady and indifferent. The coastal interchange signal blinked green, as it had all night, as it would until something changed.

He picked the phone back up. He did not block the number.

Instead he opened a new document and began, for the first time, to write down everything he had observed in the past three nights not as a maintenance report but as a record: the anomaly, the blue light, the discharge, the frequency in his hand. The dream — he included the dream, with the same precision he applied to everything else, because precision was the only tool he had and he was going to use it on all of it or none of it.

The woman in the white coat. The platform across the tracks. The way she had turned toward him as if she had been waiting.

He wrote it all down.

He did not know what he was going to do with it yet. But he had learned, a long time ago and in a way he preferred not to revisit, that the cost of not documenting things was always higher than the cost of documenting them. Even the things that didn’t belong in a report. Even the things that had no explanation.

Especially those.

His shift ended at 06:00. He stayed until 06:30, finishing the record, reading it back, finding it no less strange on second reading. Then he shut down his monitors, put on his jacket, and walked out through the hub into the early morning. The sea air hit him at the door — salt, diesel, the particular cold of a coastal city waking up — and he stopped for a moment on the steps and breathed it in.

He had not slept well in two years. He had learned to function on insufficient sleep the way you learned to function with a bad shoulder: by adjusting your movement around the limitation, by not drawing attention to it, by hoping it resolved on its own.

It had not resolved on its own.

But tonight, or this morning, walking to his car in the grey light with the bay spread out to his right and the city beginning to unspool itself from sleep, he was aware of something that was not quite hope and not quite dread but occupied the same register as both. The feeling of a variable that had just changed. A signal that had shifted from noise to pattern.

He got in his car.

On the drive home, he kept the radio off.