Chương 8: Episode 8 - Ren-Thalen's Problem

It was 0130. Everyone else was asleep. Ren-Thalen had been awake when he came back from the secondary terminal — her patterns at the slow amber she ran when she was processing something she hadn't finished yet, and he'd come in quiet and she'd turned toward him in the dark the way she turned toward things she was already reading. He'd sat at the common table. She'd stayed where she was.

And then she'd said it — the thing about the signal load, about the threshold, about not always knowing where other people ended and she began — in the flat tone she used when she was reporting something she'd decided you needed to know rather than something she particularly wanted to say. He'd been quiet for a moment after she finished. Then:"Why haven't you said this before?" She turned toward him fully.

Her electrosensory ridges oriented directly at him — the precise Thal'kesh version of eye contact, the one that meant she was reading his bioelectric state as well as his words.

"Because it's manageable. It has always been manageable. I've been managing it since I was seven years old, in rooms considerably more chaotic than a training bay." A pause.

"And because saying it requires me to tell someone that I don't always know where they end and I begin, and most people find that alarming."

"I'm not alarmed," Cassian said.

"No," she said.

"You're taking notes." He was. His stylus was moving across the tablet in his hand, filling in the field he'd already opened. He became aware of this as she said it. He stopped. He put the stylus down.

"Sorry," he said.

"Don't be. It's why I'm telling you." Her patterns ran steady amber. She knew he'd noticed and she'd chosen not to ask why he was awake at this hour, and he knew she'd noticed and had chosen not to ask, and that was the specific Thal'kesh version of permission: two people who were each aware of the other's awareness, letting things sit. *"What do you need?" he asked. She looked at him for a long moment.

The electrosensory ridges were doing their work — reading his bioelectric state, getting the full picture of what he was actually asking. He had the distinct impression she'd been prepared for several follow-up questions, and this was not one of them.

"I'm not sure," she said.

"What would help?"

"I don't know that either. I've been developing filtering techniques since I was placed in multi-species operational environments. What I have works most of the time. What I don't have is a version that works reliably when the concurrent signal load crosses a certain threshold in a closed space with people I'm starting to—" She stopped. He noted the stop. He kept his hands on the table, away from the tablet. Her patterns held steady amber. She was aware he'd noticed. They both left it where it was.

"—People I'm in extended close proximity with."

"Find out what you need," he said.

"And tell me when you know. Figure out what would actually help and tell me specifically, and I'll build around it." If you encounter this narrative on Amazon, note that it's taken without the author's consent. Report it. She was quiet.

"That's an order," he added, "if it helps." Something shifted in her expression — the subtle quality of someone receiving information that lands unexpectedly, not because it's surprising but because it's been a long time since someone offered it in exactly that form. Her patterns ran a slow pulse warmer than amber, edging toward gold, the frequency he'd later learn to associate with something settling rather than something starting.

"It does," she said.

"Help."

"Good." He stood up. He had formation data to review and the failure-mode hypothesis was still incomplete and the records request for 7D-114 hadn't come back yet and there were approximately eleven other things demanding attention. He got three steps toward his bunk before he stopped.

"For what it's worth," he said, without turning around, "the four-second advance warning you mentioned. That's not a liability. I don't know what it is yet, but it's not a liability." She didn't respond. He hadn't expected her to. He'd said it anyway because some things needed to be put in the room even when no one was ready to answer them. * He was awake at 0200, which was his usual time.

The documentation review was the ritual he'd built for this hour — not because reviewing documentation at 0200 was efficient, but because the alternative was lying in the dark with nothing to direct the part of his brain that wouldn't stop running. At least with the tablet he was producing output. He'd tried explaining this to a Meridian counselor once and the counselor had suggested sleep hygiene practices, and he'd said thank you and done none of them, and here he was. Tonight he was in the Harrow files.

Not actively working them. He couldn't actively work them here, not yet, not with the resources he had access to. But he reviewed them. He kept them current. He added the date and a status note: no new information. All copies intact. He verified the triple-encrypted backups, all three locations, which took four minutes and was not a compulsive behavior because he did it on a schedule and had a reason for each step.

He'd worked out this distinction some time ago and still found it occasionally necessary to reiterate to himself. He ran the count. 340 names. Alphabetical. He'd organized them that way deliberately — the official records had numbered them, and he'd decided that was wrong, that the numbers were the institution's version of events and the names were theirs. He kept them alphabetical. He could find any name in under thirty seconds.

He had tested this, many times, at many hours, in many rooms since Harrow, and the count was always the same and he checked it anyway because checking it was the point. The point was not the number. The number was always 340. The point was the act of verifying that the number was still 340, that none of the names had been removed or revised or reclassified by some administrative process he hadn't approved, that the list was the same list it had been.

He had learned, at seventeen, what happened to lists when he wasn't watching. He closed the file. In the far bunk, Ren-Thalen's bioluminescence cycled slow in the dark. She was probably awake — she often was at this hour, or if she slept her patterns didn't change much between the two states. The amber was very dim, barely visible, the frequency she ran when she was genuinely calm. He didn't speak. She didn't speak. That was fine.

He opened the failure-mode hypothesis file and added a note: Ren-Thalen — concurrent signal load threshold. Unknown capacity ceiling. Investigate whether a consistent comm protocol could reduce the signal differentiation problem. The problem she'd described — not knowing where the others ended and she began — was not a malfunction. It was the system working as designed, in conditions the system wasn't designed for. He'd been in that category himself. He had eleven things to do tomorrow. He would get to all of them.

He opened the drill protocol for the morning session and checked the pre-call timing adjustment he'd been building since Krell'va named the timing gap. Two changes still needed verifying. He verified them. He closed the tablet. The last light went out. She had told him the version she didn't usually tell. He didn't know how many people had received the other one — the clinical version, the research version, the version designed to inform rather than expose.

He knew she hadn't told this version to many, because the way she'd said it was the way people said things they hadn't said before: without the smoothness that came from practice, without the pauses in the right places, with the specific weight of something that had been held for a long time and had not yet learned how to travel light. He filed it. Some things didn't need to be in the infrastructure file. They needed to be somewhere else. He went to sleep.