The fanpage had been running for two years, which was approximately two years longer than Kai had expected it to run.
In the first week after the video went viral, he had assumed it would resolve on its own — that the internet’s attention would move on, as it always moved on, to the next available story. He had been wrong about this in a way that had required a specific kind of recalibration. The video had been viewed fourteen million times. The fanpage had accumulated eighty thousand followers. People had sent him train models, hand-drawn illustrations, letters written on paper and mailed to the Aureon Bay Rail Authority headquarters, which had no system for forwarding personal mail to individual maintenance engineers and had therefore developed, over the course of several bewildered months, an informal system that amounted to leaving a box on Kai’s desk.
He had never opened most of the letters. He had never engaged with the fanpage. He had given one interview, to a transport industry journal, in which he had explained the technical details of the signal fault and declined to discuss anything else. The journalist had published it under the headline *The Man Who Saved the Train* and included, against his explicit request, a photograph.
Pren had printed the photograph and taped it above the break room coffee machine. Kai had taken it down. Pren had put up another one. This had continued for several months before achieving a kind of equilibrium in which neither of them acknowledged the photograph’s existence.
The point was that Kai had established, over two years, a functional indifference to the fanpage’s existence. He checked it occasionally, with the same attitude he applied to things he needed to be aware of without being influenced by: quarterly maintenance budget reports, weather forecasts for the Bay, the accumulated messages of people who believed they knew him based on fourteen seconds of footage.
Liora Vale had been messaging him for six months.
Her messages were categorically different from the others, and he had known this from the first one. Not in tone — her tone was direct, measured, with none of the effusive energy of the fan accounts that populated most of his inbox. In content. She wrote about specific things: signal timing variance on the Starline test corridor, the neural interface specifications of the overnight sleep system, a reference to a published paper on shared-frequency electromagnetic resonance in neural networks. She wrote about these things as if she expected him to know what she was talking about, which he did, which was in itself unusual because most people who messaged him did not know what he talked about professionally and did not particularly care.
He had not responded to any of her messages. He had not blocked her either.
The distinction mattered to him in a way he found difficult to articulate. Blocking was a definitive act. It meant: this is not something I want to engage with. Not blocking meant: I am reserving judgment. He was in the habit of reserving judgment on things he could not yet categorize. It was the same instinct that kept him pulling the Starline anomaly back to the top of the queue when every system in the building was telling him it was not worth his attention.
At 09:15 on a Tuesday morning, three days after the discharge in the test corridor, he opened the fanpage message thread and read through Liora’s messages in chronological order for the first time.
There were forty-seven of them.
He read them with the focused attention he gave to technical documentation, tracking the throughline: an early period of general inquiry, specific questions about the Starline test corridor, a shift toward more urgent language approximately six weeks in, and then a sustained, carefully argued case for the proposition that the overnight sleep system was malfunctioning in a way that was harming its passengers. The progression had the quality of someone who had started with a hypothesis and accumulated evidence in support of it — not cherry-picked evidence, not the selective reading of someone who had decided first and researched second, but the gradual, sometimes contradictory evidence of someone who had kept following the thread regardless of where it led.
Message thirty-one contained the routing code. SL-TRK-004-NB. He stopped at it and looked at it for a long time.
Message forty-two, sent four days ago, read: *I know you’re reading these. The signal anomaly in section NB-04 is not an equipment fault. The frequency is matching the neural interface signal from the passenger system. Someone in the design team either missed this or decided not to flag it. My brother was on the trial run. He hasn’t woken up. I’m not asking you to do anything except look at what you’re already looking at and tell me if I’m wrong.*
Message forty-seven, sent last night: *The discharge you experienced at the manual override point — it went through the insulating glove, didn’t it? Into your hand. You felt something that wasn’t pain. I need to know if I’m right.*
Kai read message forty-seven three times.
He had not told anyone about the discharge. He had documented it in the incident report addendum in language that described the physical effect without specifying the subjective experience. He had not mentioned the frequency. He had not mentioned that it had not been painful. He had not mentioned any part of the subjective experience to any person, because the subjective experience was not documentable and he was not in the habit of reporting things he could not document.
Liora Vale, who ran a fanpage about him and whose brother was in a coma, knew about the discharge through the insulating glove.
He typed: *Where did you get the routing code?*
Her response came in forty seconds. He had not expected it that fast. It was 09:22 in the morning.
*My brother worked on the preliminary installation team for the test corridor. He kept notes. Most of them I can’t interpret. Some of them I can.*
Kai typed: *You said the discharge went through the glove. How do you know that.*
*Because the same thing happened to my brother. And to at least two other people I’ve found who had contact with the interface hardware during the Bluefall window. They all describe the same thing. A frequency. Not pain. Something that felt like a signal.*
Kai looked at the word *signal* on his screen for a moment.
He typed: *What do you want from me.*
*I want you to look at the forty-seven messages I’ve sent you and tell me if the technical claims are wrong. If they are, I’ll stop. If they’re not, I need to know what you’re going to do about it.*
He pulled up the incident reports he had filed over the past three nights. He pulled up the signal comparison data. He pulled up the routing documentation for SL-TRK-004-NB and cross-referenced it against Liora’s technical claims from messages twelve through thirty-six.
It took him forty minutes. He read carefully, the way he read everything, without rushing toward a conclusion. He found two errors in her analysis, both minor, both correctable from publicly available documentation. He found nothing that was fundamentally wrong. Her core claim — that the signal variance in the test corridor was correlated with the neural interface frequency of the passenger system — was not something he could immediately disprove. It was, in fact, consistent with what he had observed.
He had not made this connection himself. He had been tracking the anomaly as an anomaly, not as a correlation. The difference between those two framings was significant.
He typed: *Your technical analysis has two errors. Message seventeen, paragraph two: the timing variance calculation doesn’t account for the baseline differential. Message twenty-nine: the resonance frequency you’re citing is for the older interface model, not the current trial hardware. Corrected, your core claim holds. I haven’t verified it independently yet.*
A pause. Longer than before.
*Thank you,* she wrote. And then: *Will you meet with me?*
Kai looked at Monitor Two. The signal comparison was still running, the anomaly appearing at its designated point with its designated regularity. The green indicator at the top of the screen informed him that the system considered everything within normal parameters.
*Yes,* he typed. *Tomorrow. Bring your brother’s notes.*
He closed the message thread.
Pren arrived at 10:00 and spent the first fifteen minutes of his shift trying to determine why Kai looked different. He circled the question twice before landing on: “You look like someone who just decided to do something they’ve been putting off.”
Kai considered this assessment.
“That’s approximately right,” he said.
Pren looked pleased with himself for the rest of the morning.
That night, in the specific way that nights had been going lately, Kai fell asleep at his desk again.
He was getting used to this, which was its own kind of information. The dreams had a consistency now, a recognizable geography: the station, the starlit sky, the tracks, the woman on the other platform. The repetition had moved them from the category of strange experience into something that felt, despite all logic, like a place he had been to before. A place he was learning the layout of.
Tonight she was closer than she had been. Not at the edge of her platform — she was standing in the middle of it, turned toward him, and in the particular sourceless light of this place he could see more of her than he had before. Dark hair. A quality of focused attention in the way she stood that reminded him, persistently, of someone who was used to making decisions quickly. She was holding something — a notebook, or a folder, the kind of thing people held when they were working, when the holding was functional rather than decorative.
She was looking at him with an expression he recognized: the expression of someone who was trying to determine whether what they were seeing was reliable data.
He felt, looking back at her, exactly the same.
“I don’t know your name,” he said.
She tilted her head. The train was not here yet — no sound of it, no displaced air. Just the station, the stars, the two of them on opposite platforms with the dark tracks between.
“I don’t know yours either,” she said.
Her voice was clear in a way her face was not. He would remember the voice, he thought. He would hold on to the voice.
“Kai,” he said.
She opened her mouth.
The train came.
He woke at his desk, reaching forward, as if he could have caught her answer before it was swallowed by the sound of the train. The monitor in front of him was still running its comparison. The timestamp read 01:47. Pren had gone home. The hub was quiet.
Kai sat in the quiet and thought about a woman on a platform who had been about to tell him her name.
He thought about how much, given everything else currently demanding his attention, he wanted to know what it was.
He went back to work. But for the rest of the night, in the back of his mind, in the place where the frequency had settled when it moved through his hand and into his bones, he kept listening.
In case she managed to say it.
In case some version of the answer was already there, waiting to be heard.
The signal comparison finished at 02:30.
Kai saved the results to the incident report folder, added a note that the correlation between the variance pattern and the neural interface frequency would require verification against the Starline engineering specifications, and forwarded the complete file to Gant with a subject line he spent longer on than usual: *Starline SL-TRK-004-NB — anomaly may indicate passenger system interference. Request engineering review.*
He did not expect a fast response. He had stopped expecting fast responses after the second filed report. What he expected was a yellow indicator: acknowledged, queued, not yet actioned. What he needed was for the documentation to exist, for the trail to be clear, for there to be a record of what he had observed and when he had observed it and what conclusions the data supported.
This was how he operated. Methodically, incrementally, with the patience of someone who had learned that the systems around him moved at their own pace and that arguing with that pace was less productive than working within it. He had not always been this patient. Two years ago, he had been less patient, and a man he respected had been hurt, and patience had come to him afterward the way certain qualities came — as a correction rather than a development.
He filed the report. He closed the comparison. He spent the remaining hours of his shift on calibration records, which required attention but not thought, which meant he could be thorough and somewhere else at the same time.
He was somewhere else most of the night.
He was on a platform, standing across from a woman who had almost told him her name.
At 06:00, he walked out of the hub into the early morning and stood for a moment at the top of the steps, breathing the salt air. The bay was grey in the pre-dawn light, the port barely beginning its day. A container ship sat motionless at the far pier. The sea bridge curved above it, its lane lights blinking in sequence.
Kai had grown up in Aureon Bay. He had grown up with the sound of trains and the smell of salt water and the particular rhythm of a city organized around transit. He had known since he was twelve that he would work in rail. He had not known that working in rail would eventually mean standing at the edge of something he could not fully see, following a signal that the official systems had decided was not worth following.
He thought about Liora’s forty-seven messages. He thought about the routing code no one outside the project should have. He thought about a seventeen-year-old boy who had written notes that his sister could not fully interpret, who had worked on the installation team and then gotten on the trial run and not woken up.
He thought about the woman on the platform who had said *I don’t know yours either* with the particular directness of someone who was not performing anything, who was just saying the true thing because it was the relevant thing.
He got in his car.
He texted Liora: *Tomorrow means today. This afternoon, if you can. Bring everything.*
Her response came before he had started the engine.
*I’ll be there at two.*
He drove home with the windows down, the morning air coming off the bay, the city assembling itself around him. He was tired in the specific way of someone who had not slept enough but had not wasted the hours they were awake. The tiredness was fine. The tiredness was workable.
He let himself into his apartment, a fourth-floor place in the port district that he had chosen for the view of the sea bridge and had continued to occupy because moving required a level of decision-making energy he had consistently chosen to allocate elsewhere. It was a functional apartment. He had not done much with it. There was a bookshelf, mostly technical manuals and a small section of fiction that he read on overnight shifts, and a desk by the window where he worked when he was not at the hub, and a kitchen that was clean because he kept it clean rather than because he spent much time in it.
He made coffee. He stood at the window and looked at the sea bridge in the morning light.
Somewhere across the water, at the coastal interchange where the Starline test corridor rejoined the main line, the signal at SL-TRK-004-NB was running its variance pattern with its 0.3-millisecond regularity. The automated system was watching it with the incurious eye of a system that had been told what to look for and was finding it.
Kai was looking for something else.
He finished his coffee. He set the cup down. He went to bed with his phone on the nightstand and the morning light coming through the blinds, and he fell asleep almost immediately for the first time in recent memory, and he did not dream.
Or if he did, he did not remember it.
But when he woke four hours later, he checked his phone before he checked anything else, with the reflexive urgency of someone expecting a message from a specific person.
Nothing from the number he was looking for.
Of course not. He did not have her number. He did not know her name. He knew only the shape of her on a platform across a set of tracks, and the clarity of her voice saying *I don’t know yours either*, and the way she held whatever she was holding with the focused grip of someone for whom information was both tool and lifeline.
He got up.
He had work to do.
You've reached the end of this chapter
The fanpage had been running for two years, which was approximately two years longer than Kai had expected it to run.
In the first week after the video went viral, he had assumed it would resolve on its own — that the internet’s attention would move on, as it always moved on, to the next available story. He had been wrong about this in a way that had required a specific kind of recalibration. The video had been viewed fourteen million times. The fanpage had accumulated eighty thousand followers. People had sent him train models, hand-drawn illustrations, letters written on paper and mailed to the Aureon Bay Rail Authority headquarters, which had no system for forwarding personal mail to individual maintenance engineers and had therefore developed, over the course of several bewildered months, an informal system that amounted to leaving a box on Kai’s desk.
He had never opened most of the letters. He had never engaged with the fanpage. He had given one interview, to a transport industry journal, in which he had explained the technical details of the signal fault and declined to discuss anything else. The journalist had published it under the headline *The Man Who Saved the Train* and included, against his explicit request, a photograph.
Pren had printed the photograph and taped it above the break room coffee machine. Kai had taken it down. Pren had put up another one. This had continued for several months before achieving a kind of equilibrium in which neither of them acknowledged the photograph’s existence.
The point was that Kai had established, over two years, a functional indifference to the fanpage’s existence. He checked it occasionally, with the same attitude he applied to things he needed to be aware of without being influenced by: quarterly maintenance budget reports, weather forecasts for the Bay, the accumulated messages of people who believed they knew him based on fourteen seconds of footage.
Liora Vale had been messaging him for six months.
Her messages were categorically different from the others, and he had known this from the first one. Not in tone — her tone was direct, measured, with none of the effusive energy of the fan accounts that populated most of his inbox. In content. She wrote about specific things: signal timing variance on the Starline test corridor, the neural interface specifications of the overnight sleep system, a reference to a published paper on shared-frequency electromagnetic resonance in neural networks. She wrote about these things as if she expected him to know what she was talking about, which he did, which was in itself unusual because most people who messaged him did not know what he talked about professionally and did not particularly care.
He had not responded to any of her messages. He had not blocked her either.
The distinction mattered to him in a way he found difficult to articulate. Blocking was a definitive act. It meant: this is not something I want to engage with. Not blocking meant: I am reserving judgment. He was in the habit of reserving judgment on things he could not yet categorize. It was the same instinct that kept him pulling the Starline anomaly back to the top of the queue when every system in the building was telling him it was not worth his attention.
At 09:15 on a Tuesday morning, three days after the discharge in the test corridor, he opened the fanpage message thread and read through Liora’s messages in chronological order for the first time.
There were forty-seven of them.
He read them with the focused attention he gave to technical documentation, tracking the throughline: an early period of general inquiry, specific questions about the Starline test corridor, a shift toward more urgent language approximately six weeks in, and then a sustained, carefully argued case for the proposition that the overnight sleep system was malfunctioning in a way that was harming its passengers. The progression had the quality of someone who had started with a hypothesis and accumulated evidence in support of it — not cherry-picked evidence, not the selective reading of someone who had decided first and researched second, but the gradual, sometimes contradictory evidence of someone who had kept following the thread regardless of where it led.
Message thirty-one contained the routing code. SL-TRK-004-NB. He stopped at it and looked at it for a long time.
Message forty-two, sent four days ago, read: *I know you’re reading these. The signal anomaly in section NB-04 is not an equipment fault. The frequency is matching the neural interface signal from the passenger system. Someone in the design team either missed this or decided not to flag it. My brother was on the trial run. He hasn’t woken up. I’m not asking you to do anything except look at what you’re already looking at and tell me if I’m wrong.*
Message forty-seven, sent last night: *The discharge you experienced at the manual override point — it went through the insulating glove, didn’t it? Into your hand. You felt something that wasn’t pain. I need to know if I’m right.*
Kai read message forty-seven three times.
He had not told anyone about the discharge. He had documented it in the incident report addendum in language that described the physical effect without specifying the subjective experience. He had not mentioned the frequency. He had not mentioned that it had not been painful. He had not mentioned any part of the subjective experience to any person, because the subjective experience was not documentable and he was not in the habit of reporting things he could not document.
Liora Vale, who ran a fanpage about him and whose brother was in a coma, knew about the discharge through the insulating glove.
He typed: *Where did you get the routing code?*
Her response came in forty seconds. He had not expected it that fast. It was 09:22 in the morning.
*My brother worked on the preliminary installation team for the test corridor. He kept notes. Most of them I can’t interpret. Some of them I can.*
Kai typed: *You said the discharge went through the glove. How do you know that.*
*Because the same thing happened to my brother. And to at least two other people I’ve found who had contact with the interface hardware during the Bluefall window. They all describe the same thing. A frequency. Not pain. Something that felt like a signal.*
Kai looked at the word *signal* on his screen for a moment.
He typed: *What do you want from me.*
*I want you to look at the forty-seven messages I’ve sent you and tell me if the technical claims are wrong. If they are, I’ll stop. If they’re not, I need to know what you’re going to do about it.*
He pulled up the incident reports he had filed over the past three nights. He pulled up the signal comparison data. He pulled up the routing documentation for SL-TRK-004-NB and cross-referenced it against Liora’s technical claims from messages twelve through thirty-six.
It took him forty minutes. He read carefully, the way he read everything, without rushing toward a conclusion. He found two errors in her analysis, both minor, both correctable from publicly available documentation. He found nothing that was fundamentally wrong. Her core claim — that the signal variance in the test corridor was correlated with the neural interface frequency of the passenger system — was not something he could immediately disprove. It was, in fact, consistent with what he had observed.
He had not made this connection himself. He had been tracking the anomaly as an anomaly, not as a correlation. The difference between those two framings was significant.
He typed: *Your technical analysis has two errors. Message seventeen, paragraph two: the timing variance calculation doesn’t account for the baseline differential. Message twenty-nine: the resonance frequency you’re citing is for the older interface model, not the current trial hardware. Corrected, your core claim holds. I haven’t verified it independently yet.*
A pause. Longer than before.
*Thank you,* she wrote. And then: *Will you meet with me?*
Kai looked at Monitor Two. The signal comparison was still running, the anomaly appearing at its designated point with its designated regularity. The green indicator at the top of the screen informed him that the system considered everything within normal parameters.
*Yes,* he typed. *Tomorrow. Bring your brother’s notes.*
He closed the message thread.
Pren arrived at 10:00 and spent the first fifteen minutes of his shift trying to determine why Kai looked different. He circled the question twice before landing on: “You look like someone who just decided to do something they’ve been putting off.”
Kai considered this assessment.
“That’s approximately right,” he said.
Pren looked pleased with himself for the rest of the morning.
That night, in the specific way that nights had been going lately, Kai fell asleep at his desk again.
He was getting used to this, which was its own kind of information. The dreams had a consistency now, a recognizable geography: the station, the starlit sky, the tracks, the woman on the other platform. The repetition had moved them from the category of strange experience into something that felt, despite all logic, like a place he had been to before. A place he was learning the layout of.
Tonight she was closer than she had been. Not at the edge of her platform — she was standing in the middle of it, turned toward him, and in the particular sourceless light of this place he could see more of her than he had before. Dark hair. A quality of focused attention in the way she stood that reminded him, persistently, of someone who was used to making decisions quickly. She was holding something — a notebook, or a folder, the kind of thing people held when they were working, when the holding was functional rather than decorative.
She was looking at him with an expression he recognized: the expression of someone who was trying to determine whether what they were seeing was reliable data.
He felt, looking back at her, exactly the same.
“I don’t know your name,” he said.
She tilted her head. The train was not here yet — no sound of it, no displaced air. Just the station, the stars, the two of them on opposite platforms with the dark tracks between.
“I don’t know yours either,” she said.
Her voice was clear in a way her face was not. He would remember the voice, he thought. He would hold on to the voice.
“Kai,” he said.
She opened her mouth.
The train came.
He woke at his desk, reaching forward, as if he could have caught her answer before it was swallowed by the sound of the train. The monitor in front of him was still running its comparison. The timestamp read 01:47. Pren had gone home. The hub was quiet.
Kai sat in the quiet and thought about a woman on a platform who had been about to tell him her name.
He thought about how much, given everything else currently demanding his attention, he wanted to know what it was.
He went back to work. But for the rest of the night, in the back of his mind, in the place where the frequency had settled when it moved through his hand and into his bones, he kept listening.
In case she managed to say it.
In case some version of the answer was already there, waiting to be heard.
The signal comparison finished at 02:30.
Kai saved the results to the incident report folder, added a note that the correlation between the variance pattern and the neural interface frequency would require verification against the Starline engineering specifications, and forwarded the complete file to Gant with a subject line he spent longer on than usual: *Starline SL-TRK-004-NB — anomaly may indicate passenger system interference. Request engineering review.*
He did not expect a fast response. He had stopped expecting fast responses after the second filed report. What he expected was a yellow indicator: acknowledged, queued, not yet actioned. What he needed was for the documentation to exist, for the trail to be clear, for there to be a record of what he had observed and when he had observed it and what conclusions the data supported.
This was how he operated. Methodically, incrementally, with the patience of someone who had learned that the systems around him moved at their own pace and that arguing with that pace was less productive than working within it. He had not always been this patient. Two years ago, he had been less patient, and a man he respected had been hurt, and patience had come to him afterward the way certain qualities came — as a correction rather than a development.
He filed the report. He closed the comparison. He spent the remaining hours of his shift on calibration records, which required attention but not thought, which meant he could be thorough and somewhere else at the same time.
He was somewhere else most of the night.
He was on a platform, standing across from a woman who had almost told him her name.
At 06:00, he walked out of the hub into the early morning and stood for a moment at the top of the steps, breathing the salt air. The bay was grey in the pre-dawn light, the port barely beginning its day. A container ship sat motionless at the far pier. The sea bridge curved above it, its lane lights blinking in sequence.
Kai had grown up in Aureon Bay. He had grown up with the sound of trains and the smell of salt water and the particular rhythm of a city organized around transit. He had known since he was twelve that he would work in rail. He had not known that working in rail would eventually mean standing at the edge of something he could not fully see, following a signal that the official systems had decided was not worth following.
He thought about Liora’s forty-seven messages. He thought about the routing code no one outside the project should have. He thought about a seventeen-year-old boy who had written notes that his sister could not fully interpret, who had worked on the installation team and then gotten on the trial run and not woken up.
He thought about the woman on the platform who had said *I don’t know yours either* with the particular directness of someone who was not performing anything, who was just saying the true thing because it was the relevant thing.
He got in his car.
He texted Liora: *Tomorrow means today. This afternoon, if you can. Bring everything.*
Her response came before he had started the engine.
*I’ll be there at two.*
He drove home with the windows down, the morning air coming off the bay, the city assembling itself around him. He was tired in the specific way of someone who had not slept enough but had not wasted the hours they were awake. The tiredness was fine. The tiredness was workable.
He let himself into his apartment, a fourth-floor place in the port district that he had chosen for the view of the sea bridge and had continued to occupy because moving required a level of decision-making energy he had consistently chosen to allocate elsewhere. It was a functional apartment. He had not done much with it. There was a bookshelf, mostly technical manuals and a small section of fiction that he read on overnight shifts, and a desk by the window where he worked when he was not at the hub, and a kitchen that was clean because he kept it clean rather than because he spent much time in it.
He made coffee. He stood at the window and looked at the sea bridge in the morning light.
Somewhere across the water, at the coastal interchange where the Starline test corridor rejoined the main line, the signal at SL-TRK-004-NB was running its variance pattern with its 0.3-millisecond regularity. The automated system was watching it with the incurious eye of a system that had been told what to look for and was finding it.
Kai was looking for something else.
He finished his coffee. He set the cup down. He went to bed with his phone on the nightstand and the morning light coming through the blinds, and he fell asleep almost immediately for the first time in recent memory, and he did not dream.
Or if he did, he did not remember it.
But when he woke four hours later, he checked his phone before he checked anything else, with the reflexive urgency of someone expecting a message from a specific person.
Nothing from the number he was looking for.
Of course not. He did not have her number. He did not know her name. He knew only the shape of her on a platform across a set of tracks, and the clarity of her voice saying *I don’t know yours either*, and the way she held whatever she was holding with the focused grip of someone for whom information was both tool and lifeline.
He got up.
He had work to do.
You've reached the end of this chapter