Chapter 97: The Answer

Leo told Kai at eleven PM.

Not all of it—Kai didn't need the substrate mechanics, the failure timelines, the probability distributions the composite had been generating since the debrief. Kai needed the essentials: the northern juncture was failing. Leo was going in the morning. Alone.

Kai was quiet for six seconds, which was longer than his usual silences.

"The Arbiter told you," he said.

"Yes."

"Through the sub-harmonic mapping."

"It confirmed the sub-harmonic when I asked it directly. It's been monitoring the juncture stress distribution since the first session." Leo looked at the channel's background hum. "It says the deterioration accelerated six days ago and it had been—assessing whether to tell me."

Another silence. "It sat on critical infrastructure information for six days."

"Yes."

"Because telling you would change your priorities and it didn't want your priorities changed before the crossover preparations were far enough along."

"That's what it said."

"That's—" Kai started and stopped. The boy who made up his own profanity was silent for a moment. "That's not what cooperation looks like."

"No." Leo sat down. The kitchen, the late-night quiet, David's rotation moving through the house's lower level. "It's what partial cooperation looks like. It told me eventually. It told me with enough time to act. But the six-day window where it held the information and watched me run sessions without knowing—that's its agenda intersecting with mine, not the same thing as mine."

"You still trust it?"

Leo thought about this honestly. "I trust that its information about the northern juncture is accurate—Park's surface sensors are consistent with the failure profile. I trust that it has a reason for telling me now, and that the reason is connected to the crossover." He paused. "I don't trust that I know all its reasons."

"Okay." Kai's voice shifted into the operational register—the mode he used when the situation was what it was and the useful thing to do was move forward. "Morrison's in Geneva. The arrays stay in the east district. You go to the north juncture alone. Walk me through what happens when you get there."

"Direct energy application to the juncture substrate. The same mechanism as the sprint sessions, but without the membrane and without the filter—the northern juncture doesn't have the infrastructure. I push repair energy into the substrate until the stress redistribution normalizes."

"And if the cascade failure activates while you're doing it."

"Then I handle the cascade failure."

"Which means it kills you."

"Probably once. Maybe twice." Leo's voice was even—the calibration of a man for whom dying was a cost structure rather than a finality. "The juncture's failure energy won't be targeted. It'll be reactive—the substrate architecture lashing out under destabilization stress. I've managed comparable events."

"You'll come back."

"Yes."

A pause. The Kai pause that held something he was deciding whether to say.

"Leo. The Arbiter withheld information about the northern juncture for six days while you were running sessions that open the channel to its maximum." Kai's voice was careful. "The channel is two-way now. During those sessions—when you're fully open to the seal's architecture—what else has the Arbiter had access to that you don't know about?"

The question sat in the kitchen's quiet.

"I don't know," Leo said.

"You should ask it."

"I will."

"Before you go to the northern juncture. Ask it what it's been doing with the full-channel access during the sprint sessions. Not just the juncture mapping. Everything." Kai paused. "And if the answer involves anything it's built or modified or encoded without telling you—"

"I'll deal with it."

"I know you'll deal with it. I just want you to know what you're dealing with before you walk into a failing juncture alone."

He thought through the logic of this. The composite was already preparing the framework for the question—the specific way to ask the Arbiter what it had been doing through the full-channel access, in language the language of cessation could carry without evasion. He set the framework aside and built his own.

"Go to sleep," he said.

"I was up at two working on the sub-harmonic analysis."

"Sleep is when the brain integrates analysis."

A long pause. "That's what Tanaka says."

"He's right about that one."

"I'll sleep after you tell me you've asked the Arbiter."

"I'll ask it now. Then I'll tell you. Then sleep."

"That works."

---

Leo sat in the chamber at midnight.

The channel at rest-level—the permanent open connection, the background hum of the seal's presence. The filter at its operational resonance, the receiver/transmitter imprint the Arbiter had built into the frequency-separator architecture.

He didn't announce himself. He'd been learning, over the past week of communications, that the Arbiter was always aware of the channel's state. It registered his presence the way the seal registered the repair energy—passively, continuously.

"I have questions," Leo said.

The filter's outer surface activated. The signal arriving clean.

*We anticipated.*

"The full-channel sessions. When the channel is at maximum capacity—sprint intensity, repair energy flowing—you have access to the channel's architecture at a level that's different from the between-session ambient state. What have you done with that access?"

The pause that followed was the longest he'd recorded—nine seconds before the first signal arrived. Not composition. Something else. The texture of an entity deciding how honest to be when the alternative was to lie and it couldn't lie.

*We have been listening,* the Arbiter said. *Not to you. To the seal's full architecture. During the active sessions, your repair energy activates substrate pathways that are dormant between sessions. These pathways carry information we cannot access in the ambient state. Information about the seal's structural condition. The juncture integrity measurements. The cascade failure probability distributions.*

"You've been running your own assessment of the seal's condition using my sessions as the activation mechanism."

*Yes.*

"What else."

*The filter's operation. During active sessions, we can observe the frequency-separator's processing at resolution not available in ambient state. We have been—* A careful pause. *—building a model of the filter's full architecture. Its vulnerabilities and capabilities.*

"You've been mapping the filter from the inside."

*Not for breach. The filter's suppression function remains intact. We have not been attempting to bypass it.* The signal's texture was the one Leo had learned to read as precision—the entity being exact because exactness was what it had instead of reassurance. *We have been building the model because the crossover event will interact with the filter in ways we need to understand. The specific conditions of the crossover—the full-channel opening at the primary juncture location—will place demands on the filter that differ from the sprint session demands. We needed to know what the filter can withstand.*

"And what can it withstand."

The pause that followed felt heavier than the previous ones.

*At the juncture location, without the environmental calibration of this facility's substrate architecture, the filter will experience approximately thirty to forty percent reduction in suppression efficiency during the crossover peak.* The signal was careful. Exact. *This is a manageable reduction under controlled conditions.*

"What are the controlled conditions."

*The primary juncture's catchment area—the forty-meter radius from the juncture's surface coordinates—must be clear of normal human presence during the crossover peak. The peak lasts between four and eight seconds. During those seconds, the death energy carrier wave at reduced filter efficiency will be present at lethal concentration within the catchment radius.*

*You are aware that the east district has been experiencing population reduction,* the Arbiter said. *The data you have access to through your household's monitoring indicates the catchment area is substantially cleared.*

"Substantially."

*Yes.*

The word sat in the channel's quiet. *Substantially cleared.*

"How close to completely," Leo said.

*We do not have precise data on individual occupancy within the catchment radius. Our information is derived from the juncture's substrate energy interactions with biological presence—a broader measure.* A pause. *The catchment area reads as significantly less occupied than three months ago. Whether 'significantly less' and 'clear' are equivalent—this we cannot confirm.*

The composite was already running the occupancy model—David's real estate data, the evacuation records, the monitoring from the last three months.

"You're telling me there might be people there."

*We are telling you the information we have, which is incomplete.* The Arbiter's signal was—it was the truth-texture. The frequency that couldn't encode false information. *You should verify with precision before the crossover. We cannot verify for you. We do not have that capability.*

"But the crossover still needs to happen at the primary juncture."

*Yes. The repair energy must be channeled from within the substrate catchment area for the final 0.4% to complete. The crossover cannot finalize at this distance.* A pause that felt almost human. *We have told you the cost. We have told you the conditions. What you do with that information is your choice. This was always the case.*

Leo sat in the chamber with the channel humming and the filter processing and the Arbiter's last statement doing its quiet work in the gap he held.

*This was always the case.*

---

He called Kai.

"I asked it," Leo said.

"And?"

He told Kai what the Arbiter had said. All of it: the full-channel architecture monitoring, the filter vulnerability modeling, the crossover requirement. The 40-meter catchment area. The four-to-eight second death-energy peak. The Arbiter's statement that the catchment area read as "significantly less occupied" but not confirmed as clear.

Kai was very quiet during all of this.

After Leo finished, Kai stayed quiet for another twelve seconds.

"It's been building toward this the whole time," he said.

"Yes."

"Not the northern juncture—that's a real problem it's helping with. The crossover. It needed you at the primary juncture for the final repair. And the crossover creates a death-energy event within the catchment area." A pause. "Leo. Why does the Arbiter need the catchment area to have people in it?"

Leo had been sitting with this. "It doesn't need people there. It needs the crossover to happen. Whether people are in the catchment area or not—that's the cost. The cost isn't the Arbiter arranging for deaths. It's the Arbiter needing an event that carries the risk of deaths."

"But if you clear the area—if you verify precisely—"

"The crossover happens without casualties."

"So why didn't it tell you to clear the area carefully? Why did it say 'significantly less occupied' instead of giving you the specifications of the catchment radius and telling you to do a house-by-house check?"

The question sat in the kitchen's quiet.

"Because it trusts my verification," Leo said. "Or because it trusts that my verification will be whatever I make it."

A longer silence.

"Leo," Kai said. Very quiet. "When you go to the northern juncture tomorrow—when you're doing the direct repair, alone, without the team—you're going to be exhausted afterward. The session after that—you'll be running session six in a depleted state. And then session seven, and eight. And then the crossover."

"Yes."

"And the closer you get to the crossover, the more the crossover is the focus. The more everything else is context." Kai's voice was careful. The voice of someone who'd run the model and didn't like the answer. "The catchment area verification. The house-by-house check. When does that happen?"

"Before the crossover. I have days."

"But not many. And they'll be the hardest days of the sprint." A pause. "Leo. Ask Morrison to do the verification. Proper verification. Not summary data—actual ground-level check of every structure in the forty-meter radius."

Leo had already been building toward this conclusion. Hearing it from Kai made it more real.

"Tomorrow," he said. "When Morrison's back from Geneva."

"Before you go to the northern juncture."

"After. Morrison's return is afternoon. The northern juncture can't wait until afternoon."

Kai was quiet. "Okay," he said finally. "Okay. But Morrison as soon as he's back. Not summary data—he has people on the ground. He can do a door-to-door."

"Yes."

"Promise me."

Leo thought about what promising Kai something meant. The weight of it. The thirteen-year-old who'd learned that the words adults said to reassure him were sometimes the same words they said when they couldn't guarantee the thing.

"I'll tell Morrison the first thing when he's back," Leo said. "I'll make it the condition of the crossover proceeding."

"Okay." Kai's voice settled. "Go to sleep, Leo. Tomorrow's going to be hard."

"I know."

"The northern juncture will try to kill you."

"Probably."

"Try not to let it twice."

Leo looked at the counter above his head in the darkened room. **10,489.** "I'll do my best."

"That's not the same as promising," Kai said.

"No. It's not."

A brief silence.

"Good night, Leo."

"Good night."

The channel hummed. In the north of the city, a juncture moved toward its failure window. In the east district, twelve people whose names were not in David's summary data lived in the forty-meter catchment radius of the primary juncture, in buildings that had been occupied long enough to become invisible in the monitoring data.

Leo went to sleep.

He didn't dream, which happened sometimes. The channel was always there. The seal's presence at the edge of awareness, tired and grateful, receiving its incremental repair.

Morning came the way morning came: without asking.