Chapter 93: The Council Knows

Walsh called the session for 0900 and didn't frame it as a request.

"The Council requires Captain Okafor's presence to address the events of the memorial service and the ongoing security situation aboard this vessel." The formal phrasing, transmitted through official Council channels rather than Walsh's personal comm. The language of a former senator who knew the difference between asking and summoning and had chosen the latter.

Zara hadn't slept. The engineering access logs were still open on her desk, the forty-seven-system mesh network mapped in three dimensions on the display she'd been staring at for fourteen hours. She changed her uniform jacket, splashed water on her face, and walked to the Council chamber on Deck 3.

The chamber was full. Not public-gallery full—the memorial had cured people of attending public gatherings for the moment—but every Council seat occupied, every aide present, the weight of a room where everyone had arrived early. Arriving early was a way of saying this mattered.

Walsh at the head of the table. Sixty years old, silver hair pulled back, the bearing of someone who'd spent three decades in institutional power and had learned to wear it without visible effort. She looked at Zara when she entered and the look was neither hostile nor friendly. It was evaluative. The look of a woman deciding how much of her political capital to spend on this particular morning.

Voss was already talking.

"—three civilian casualties at an event that was designed, organized, and approved by the command structure. The security response that triggered the crowd surge was authorized by the captain directly. I am not suggesting negligence. I am suggesting that the current framework for civilian safety is inadequate, and that the captain's rejection of enhanced security measures two days ago—"

"The captain rejected martial law," Tanaka said. She was seated three chairs from Voss, her posture the composed stillness of someone who'd been listening for long enough to identify exactly what needed to be said. "Martial law is not a civilian safety measure. It is a governance framework. The distinction is not academic."

"The distinction is academic when three people are dead, Councilwoman Tanaka."

"Ha." Voss's brief laugh. "Three people are dead because a political faction used a memorial as a platform and the security response was insufficient to manage the resulting crowd dynamics. The question before this Council is whether the current authority structure can prevent recurrence. I submit that it cannot, without expanded powers."

"Expanded powers for whom?" Santos asked. He'd been quiet until now, seated at the engineering liaison position that wasn't technically a Council seat but had become one through seven months of Santos being the person who could explain what the ship was actually doing. "For the captain? For you? For the Council as a body? Expanded powers is a phrase, Mr. Voss. I would like to know the specific policy."

Voss turned to Santos with the measured patience of a man who considered engineering liaisons to be useful but subordinate participants. "The specific policy is a security authorization framework that does not require the captain's personal approval for crowd management deployment. Standing authority for the security chief to act on pre-established protocols without real-time command authorization."

"You want to give Cross independent deployment authority," Zara said.

"I want to remove the bottleneck that killed three people."

The room was quiet. Walsh watched the exchange and said nothing. Letting the debate develop before intervening.

"The bottleneck," Zara said, "was not the authorization chain. Cross's team was deployed within ninety seconds of the disruption. The surge occurred because the deployment itself—the physical entry of security personnel into a corridor filled with frightened civilians—triggered the crowd compression. Faster authorization would have produced faster deployment, which would have produced an earlier surge. The outcome would have been the same or worse."

"Then the problem is the deployment methodology."

"The problem is that two thousand people in a corridor heard security approaching and panicked. No deployment methodology prevents that response in a population that has spent seven months associating security presence with crisis." She looked at Walsh. "The solution is not expanded authority. The solution is a population that trusts the security apparatus, which requires the security apparatus to be accountable to civilian oversight, which martial law and independent deployment authority both undermine."

Walsh held her gaze for three seconds. That evaluative look again. She was weighing arguments against consequences, and her face gave away none of the math.

"The Council will table the expanded authority proposal pending a formal review of the memorial security response," Walsh said. "Captain, you will provide a written incident analysis within forty-eight hours. The review body will be consulted." She paused. "The Council also requests an update on the ongoing investigation into the saboteur's activities. The memorial disruption diverted security resources, and there are questions about whether that diversion was exploited."

Zara had been waiting for this. Walsh was too experienced not to have connected the dots—the memorial, the security diversion, the saboteur's access window.

"The investigation is active," Zara said. "We've identified a pattern of system modifications across the ship that extends beyond the navigation systems. Engineering is analyzing the scope."

"The scope," Tanaka said. "Can you be more specific?"

"Forty-seven ship systems have been modified over the past seven months. The modifications are not damage. They're additions—new data pathways and power routing integrated into existing infrastructure. The pattern is consistent with deliberate construction rather than sabotage."

The room shifted. She could see it in the way bodies adjusted in chairs, the way eyes moved between faces. Construction was a different word from sabotage, and different words created different fears.

"Construction of what?" Walsh asked.

"We're determining that now."

Voss leaned forward. "Forty-seven systems modified over seven months without detection. Wouldn't you agree that this raises questions about the competency of the engineering oversight?"

"It raises questions about the capability of whoever did the work," Santos said. His voice was level but his hands were flat on the table, pressed down. "The modifications were made during legitimate maintenance windows using authorized credentials. They passed automated diagnostics because they were engineered to pass automated diagnostics. This was not a failure of oversight. This was a professional operation by someone who understood the ship's systems at a design level."

"Authorized credentials," Tanaka repeated. "Whose credentials?"

"Multiple accounts. Seventeen different maintenance authorization codes were used across the forty-seven modifications. The access patterns are distributed—no single account was used more than four times, and the timing was spread across the full seven months."

"Seventeen accounts," Walsh said. "Are we dealing with seventeen saboteurs?"

"No." Santos paused. He'd run the analysis three times before coming to the session, and the answer was the same each time. "The seventeen accounts belong to seventeen different engineering personnel who were performing routine maintenance in the areas where the modifications were made. Their access was legitimate. Their work orders were genuine. But during each of their maintenance windows, an additional modification was made that does not correspond to any work order."

"Someone piggy-backed on their access," Cross said from the security position.

"Or someone used their credentials while they were logged in. Or someone with sufficient system authority created a parallel session under their authentication. The access logs show no anomalies because the access itself was not anomalous—it occurred during real maintenance by real personnel doing real work."

"Then the saboteur is someone with broad enough system access to create parallel sessions under other people's credentials," Zara said. "Without triggering security flags."

"Yes." Santos looked at her. "Captain, the number of people on this ship with that level of system access is—" He stopped. Counted. "Twelve. Including me. Including Dr. Vance. Including three members of the original systems design team who are now in various departmental roles."

Twelve people. Zara filed the number. Twelve people with the access level required to build a parallel infrastructure inside the Exodus without being detected. Twelve people who understood the ship's systems at the depth the modifications required.

The session ended at 1030. Walsh dismissed the Council with the precise formality she used when she wanted the record clean.

Voss caught Zara in the corridor.

"Captain." He fell into step beside her. "I want you to know that my proposal was not an attack on your authority. It was a genuine assessment of the security gap."

"I know what it was."

"Then you know I will bring it again. The next time civilians die at an event you authorized, the votes will be different." He stopped walking. "I do not want civilians to die. That is not a political statement. It is a fact about my preferences. But the next time it happens, I will have the votes, and we will both know why."

He turned and walked back toward the Council wing. The precise stride of a man who'd delivered his message and considered the delivery complete.

---

Hassan called at 1400.

"Component six," she said. "I have—actually, I need to explain the framework shift first, because the decoding methodology I used for components one through five doesn't apply to component six. The previous components were addressed to the ship's communication systems—to the MX broadcast array's standard reception channels. Component six is addressed to the mesh network. The secondary infrastructure. And the encoding is different. Not the entity's standard mathematical communication structure. This is—" She paused. Her voice had been accelerating, the words compressing as they did when she was processing faster than she could speak. "This is machine language."

"Machine language."

"Operational instructions. Not symbolic communication meant for human interpretation. Direct commands formatted for execution by the mesh network's distributed processing nodes. The entity is not talking to us through the mesh network. It is talking to the mesh network itself."

Zara stood in her office. The three-dimensional mesh network map still glowing on her display. Forty-seven nodes connected by secondary data channels, routing power and data to the broadcast array.

"Can the mesh network execute commands?"

"That is what I spent three hours determining. The answer is yes. The secondary data channels are bidirectional—they can receive instructions as well as transmit data. The processing nodes at each junction have enough local computing capacity to execute simple operations. And the mesh architecture distributes complex operations across multiple nodes, so the network as a whole can execute commands that no single node could handle alone."

"What commands is the entity sending?"

"The component six transmission contains—" Hassan's voice went quiet. The particular quiet of a mathematician who'd finished her calculation and was sitting with the result. "It contains a test sequence. A diagnostic routine. The entity is verifying the mesh network's operational capacity by asking it to perform a series of increasingly complex tasks."

"What tasks?"

"Data routing verification. Power distribution confirmation. Sensor access confirmation. And—" She stopped again. Longer this time. "Navigation system interface test. The final element of the test sequence is a handshake protocol between the mesh network and the ship's primary navigation system. The entity is checking whether the mesh network can access and control navigation."

The office was quiet.

"Not through the trigger in the backup layer," Zara said.

"No. Through the mesh network's own connections. The secondary data channels that the saboteur built into the navigation system—the same channels that exist in all forty-seven modified systems. The mesh network has its own pathway into navigation. Independent of the saboteur's trigger. Independent of the backup layer."

Two pathways into navigation. The saboteur's trigger, set to activate when the primary system dropped below seventy percent. And the mesh network's own connection, controlled not by the saboteur but by the entity.

Two different approaches to the same system. Two different agents—the saboteur on the ship and the entity in the void—both building toward the navigation array.

"Hassan. Has the test sequence been executed?"

"I cannot determine that from the broadcast data alone. The test sequence was transmitted. Whether the mesh network received it and ran it—that requires monitoring the mesh network's internal traffic, which Santos's team would need to—"

"Get Santos. Now."

She cut the comm and stood in the office looking at the mesh network map. Forty-seven glowing nodes distributed across the ship's schematic. A nervous system built by a saboteur. Operated by an entity a billion kilometers away.

And the first thing the entity wanted to test was whether it could steer the ship.