The fanpage broke its own record the week the coverage peaked.

Pren texted Kai a screenshot with the caption: *this is technically your fault.* The screenshot showed the Rail Hero Kai fanpage at four hundred thousand followers, which was a number Kai found abstractly interesting in the same way he found large infrastructure numbers interesting: notable, but not particularly connected to anything he needed to act on.

He showed it to Mina.

She looked at the number. “Four hundred thousand people,” she said.

“Apparently.”

“Have you looked at what they’re saying?”

“No.” He put the phone down. “Pren is managing it.”

“Pren is twenty-four,” she said.

“He’s competent.”

She looked at him with the expression she used when she was deciding whether to push on something. She pushed. “Kai. There are four hundred thousand people who are following a story about you because you filed signal reports that nobody read and they turned out to matter. That’s not nothing.”

“I know it’s not nothing,” he said. “But it’s not something I know what to do with.”

“You don’t have to do anything with it. But ignoring it entirely is also a choice, and maybe not the right one.” She paused. “Yuna is going to call you about the Starline offer again.”

“She already did. I said no.”

“I know. But there are going to be other offers, and some of them are going to be about things that matter — rail safety advocacy, regulatory testimony, the kind of work that uses the attention rather than just absorbing it.” She looked at him steadily. “I’m not saying you have to do any of it. I’m saying you might want to think about which version of the visibility you’re willing to use.”

He was quiet for a moment. She had said this precisely, which was how she said things she had thought about carefully, and he had the specific experience of receiving information that required updating a model he had assumed was settled.

“You think I should respond to some of it,” he said.

“I think the Rail Hero Kai that four hundred thousand people are following is not you,” she said. “And you know that. But the story of someone who filed reports for three months because the signal was wrong and the system told him it wasn’t — that story is you. And that story, told correctly, is useful.”

He looked at her.

“I’m not telling you what to decide,” she said. “I’m saying the decision exists.”

He thought about this for the rest of the day and some of the next.

On Thursday, he called Yuna.

“Not the Starline ambassadorship,” he said. “But the rail safety board testimony, if they ask. And one interview, in a technical publication, about signal anomaly documentation and why recurring non-critical flags need systematic review. Not about the system, not about me. About the documentation protocol.”

Yuna was quiet for a moment. He could hear her updating her model.

“That’s very Kai of you,” she said.

“Is that a problem?”

“No,” she said. “It’s exactly right.”

He called Mina after.

“Yuna says it’s exactly right,” he said.

“She’s correct,” Mina said. “Tell me about the protocol article.”

He told her. She listened with the attentiveness she gave everything that mattered, and asked two questions that improved the framing, and said: “Write it the way you write the incident reports. Complete, in order, with the evidence visible. People will trust it because it reads like a person who trusts the evidence.”

He wrote the article the following weekend, at his desk with the drawing in the window and the harbor beyond it. It took four hours. He sent it to the transport safety journal he had been interviewed in two years ago, with a note that explained what it was and what it was not. He did not copy Mina on the submission because she did not need to see everything he sent, which was its own kind of comfort: the ability to do things independently without those things being separate.

The journal published it three weeks later. It received what the editor called “substantial attention from the regulatory community.” The rail safety board cited it in their preliminary findings on the Starline case.

Pren sent a text that was entirely exclamation marks.

Yuna sent: *Good. Now come home for dinner sometime.*

Mina, when she read the published version, said: “You kept the secondary incident in paragraph four. I would have cut it.”

“The secondary incident is why the protocol matters,” he said.

“I know. That’s why I would have cut it — to let the reader arrive at the importance themselves.”

He considered this. “For the next one,” he said.

She looked at him. “There’s going to be a next one?”

“Probably. There are several documentation gaps in the current regional safety framework.”

She smiled. Not the not-quite-smile — the full version. The one he had been seeing more frequently, which he had decided was one of the better data points he had accumulated in recent months.

“For the next one,” she said, “cut the secondary incident.”

“I’ll consider it,” he said.

He would consider it. He might not cut it. But he would think about what she had said, because she was usually right about the things she said, and being right about what he wrote was one of the things he had come to value about her, among many.

He put the article away and they went for dinner, and Pren’s exclamation marks sat in his phone unacknowledged, and the four hundred thousand followers continued to follow something that was not quite him and which he was, slowly, learning to redirect toward something that was.

The harbor was visible from the restaurant window.

He was learning its rhythms.

He thought he was going to be here a long time.

Yuna came to Narae the month after the article published.

She came officially for a conference — transport safety, three days, the kind of thing Kai usually attended and this time had declined because his Narae infrastructure review was at a critical juncture. She had apparently decided that if he was not coming to the conference, the conference could come to him, at least for dinner.

He had not told her much about Mina. He had told Yuna that he had met someone and that the meeting had been unconventional and that she would understand more if she met Mina than if he tried to explain. Yuna had received this information with the specific patience of someone who had known Kai for six years and understood that *unconventional* and *I’ll explain by introducing you* were the largest disclosures he was capable of making in advance.

They met for dinner at the restaurant near the hospital, which was Mina’s suggestion and which he had accepted because he trusted her read of restaurants that served their purpose without requiring the restaurant to be a statement.

He arrived first. Mina arrived two minutes later, from a shift that had run slightly long, still in the specific quality of someone who was transitioning between work-mode and evening-mode. He had learned to read this transition and to not require it to be complete before the evening started.

Yuna arrived three minutes after that and stopped in the doorway to assess, which was what Yuna always did: build the picture before engaging with it.

She looked at them at the table together. He saw her look.

She crossed the restaurant and sat down.

“Dr. Seol,” she said to Mina. “I’ve been following the case coverage. Your documentation work was very clean.”

“Thank you,” Mina said. “Your management of the public communications was also very clean. The technical journal redirect was particularly good.”

Yuna looked at her. “I didn’t announce that publicly.”

“Kai mentioned it,” Mina said. “I thought it was smart.”

Yuna looked at Kai. He looked back with the expression of someone who had not violated any confidence and was comfortable with this.

Yuna said: “He doesn’t usually tell people things.”

“I know,” Mina said. “Which is one of the reasons I noticed when he did.”

Yuna looked at Mina for a moment. Then she looked at Kai. Then she looked at the menu.

“All right,” she said. “I’ll have the fish.”

Dinner was, Kai thought, successful. The definition of success in this context was: Yuna and Mina had a conversation that he mostly listened to, which addressed a range of topics including the rail safety article, the documentation standards for corporate technology oversight, and the question of whether the cardiologist from Mina’s compliance meeting had been right to describe the situation as a regulatory failure rather than a corporate one. Both of them had opinions. The opinions were well-argued and partially compatible.

At the end, when Mina had gone to get her coat, Yuna said to him: “Hold onto this person.”

“I know,” he said.

“And?”

“I’m aware,” he said.

Yuna looked at him with the expression of someone who had known him long enough to read the specific quality of *I’m aware* as the thing it was: not a minimal response but the largest response he was going to give in this context, which was to say: yes, I know, I am doing exactly that, it does not require announcement.

She nodded.

Mina came back with her coat.

They walked Yuna to her hotel, which was near the conference center, and said goodnight. Mina and Kai walked back through the Seon district in the evening.

“She approves,” Mina said.

“Yes,” he said.

“Did you already know she would?”

He considered this. “I knew she would see clearly. I didn’t know what she’d see clearly.”

“And?”

“She saw clearly,” he said.

Mina looked at him. The not-quite-smile, the full version, the one that appeared more frequently now. “You’re not going to say what she said.”

“No.”

“That’s fine.” She took his hand. “I got the message anyway.”

They walked the rest of the way in the comfortable quiet that was not absence.

The city did what it did.

He was aware of what he was holding.

The rail safety board testimony came two months later.

Kai had prepared with the thoroughness he brought to all presentations: the documentation organized chronologically, the technical arguments sequenced from evidence to conclusion, the potential counterarguments identified and addressed within the testimony itself. He had not asked Mina to review it, because her domain was medicine and the testimony was engineering, and he was particular about that distinction.

She had reviewed it anyway, the night before, at his request. He had said: “Tell me if any of this is unclear to a non-specialist.”

She had read through it and said: “Paragraph seven. The phrase ‘differential timing offset’ — define it before you use it.”

He had defined it before he used it.

The testimony was three hours. He presented, answered questions, was cross-examined by a board member who appeared to have read his signal documentation in detail and had substantive objections, which he addressed in detail. The cross-examination was, he thought afterward, the most technically satisfying part of the day: the experience of having done the work thoroughly enough that a well-prepared challenge could be met with equal preparation.

The board member who had challenged him, at the end, said: “Your documentation practice is exemplary. I’ve read the original reports. If the system had acted on the first filing, this would have been addressed two months earlier.”

He nodded. “Yes.”

“We’re going to recommend that the authority adopt your documentation protocol as a standard. We’ll need someone to help develop the training materials.”

He had not expected this. He considered it for a moment.

“I’m in Narae now,” he said. “But I can do remote work on the materials.”

“That would be acceptable,” the board member said.

He called Mina on the way out of the building.

“How did it go?” she said.

“The testimony was good. They’re going to adopt the documentation protocol as a standard.”

A pause. “Kai.”

“Yes.”

“That’s…” She was quiet for a moment. “That’s the thing you were trying to do from the beginning. Not the Starline case. The protocol.”

He thought about the first incident report, filed three months before the case broke, marked *non-critical* and pushed to the bottom of the queue. He thought about the specific feeling of following a signal that the system said did not matter.

“Yes,” he said. “That’s what I was trying to do.”

“Good,” she said. The word carrying its weight.

He walked back to the station through the city, which was not Narae — he had traveled for the testimony, would take the evening train home — and thought about what it meant to have done the thing you were trying to do. Not the dramatic version, not the version with headlines. The protocol version. The documentation version. The version that would mean the next person who filed three months of reports that nobody read would have a system that was designed to catch what they were seeing.

He thought: *this is what the signal was always pointing toward.*

He got on the train.

He sent the signal sequence before he sat down, from three cities away, as he always did.

Her reply came in forty seconds, across the distance.

The phrase. And: *Come home.*

He looked at *come home* and thought about what home meant now: the harbor, the apartment, the morning walk route he had learned by walking it with her, the drawing in the window, the restaurant she had taken him to on the first Thursday.

He thought about the accumulation of days.

He thought: *yes. I’m coming.*

He went home.

The training materials took three months.

He worked on them in the evenings, at his desk, with the same approach he brought to the incident reports: complete, in order, evidence visible, no unnecessary language. Mina read drafts sometimes, at his request, for clarity checks. She had become, without either of them announcing it, a reliable test case for whether technical documentation was accessible to a careful, intelligent non-specialist.

She was not always gentle in her feedback.

“This section,” she said, pointing at a training module, “assumes the reader already understands why timing sequences matter. They don’t. Start two steps earlier.”

He started two steps earlier.

The materials were published by the regional rail authority six months after the testimony. The board member who had cross-examined him sent a brief note: *The documentation standard is now in effect. Your reports are the model examples.*

He showed the note to Mina.

She read it. She handed it back.

“Your reports were always the model examples,” she said. “Everybody else just caught up.”

He looked at her.

“Is that not accurate?” she said.

“It’s accurate,” he said. “I wasn’t sure you were going to say it.”

“I say what’s true,” she said. “You know that.”

He knew that.

It was one of the many things he knew about her now, accumulated over months of being in the same city, the same rooms, the same conversations. The things she said and the things she did not say. The way her attention shifted when something mattered. The specific quality of her voice when she was about to tell him something he needed to hear.

He filed these in the part of himself that was not documentation but was its own kind of record: the knowledge of a person that lived in the body rather than in files, that could not be erased because it was not stored in any system but in the texture of every morning and every evening and every walk and every conversation.

The system was gone.

This remained.

He thought: *this is what load-bearing looks like from inside the structure.*

The structure was holding.

He went back to work.

Pren visited Narae in the spring.

He arrived on a Friday evening with a bag that suggested an overnight stay and the specific energy of someone who had been curious about something for a long time and had finally decided to find out. He met Mina at the restaurant near the hospital — Kai had decided that this was where these introductions happened now, since it had worked for Yuna, which was a sample size of one but sufficient for a pattern — and spent the dinner alternating between asking her questions about emergency medicine and watching Kai with the expression of a person recalibrating a model they had held for two years.

Afterward, walking to the transit station where Pren was catching the night train back, he fell into step beside Kai and said: “She’s very direct.”

“Yes,” Kai said.

“You like that.”

“Yes.”

Pren was quiet for a moment. “You seem…” He searched for the word. “Settled.”

Kai considered this. “Yes,” he said. “That’s accurate.”

“I’ve been working with you for over a year and I’ve never seen you settled,” Pren said. “You were always… tracking something. Like there was always an anomaly somewhere that needed following.”

“There was,” Kai said.

“And now?”

“Now the anomaly resolved.” He paused. “And I’m building the protocol that catches the next one.”

Pren was quiet for another moment.

“The fanpage is going to be sad when they find out you’re boring now,” he said.

“I was always boring,” Kai said.

“You were never boring,” Pren said. “But you’re… quieter. In a good way. Like the signal is… not loud anymore.”

Kai looked at the city around them. The Narae evening: the lights, the foot traffic, the transit station ahead with its departure board cycling through information.

He thought about the signal at SL-TRK-004-NB, flat for months now. He thought about the four hundred thousand people following a story about him that was not quite him. He thought about the training materials and the testimony and the documentation protocol that was now standard.

He thought about Mina, walking back to his apartment to let herself in with the key she had had for six weeks, because it had seemed sensible and they had agreed on sensible.

“The signal is clear,” he said. “That’s not the same as quiet.”

Pren looked at him.

“A clear signal and a quiet one look the same from outside the system,” Kai said. “From inside, they’re very different.”

Pren nodded, with the specific nod of someone who did not fully understand but recognized that a person who understood had said something true.

“Okay,” Pren said.

They reached the station. Pren caught his train. Kai walked back through the evening to an apartment where the lights were on and a key had been used and someone was probably making tea because that was what she did in his kitchen in the evenings when she was there.

He was right about the tea.

He hung up his jacket and sat down.

The signal was clear.

The structure was holding.

He was, for the first time in a long time, exactly where he was supposed to be.