Chapter 88: Pressure

Voss introduced the motion at the start of the Council session.

No preamble. No background context that the members didn't already have. Just the motion itself, presented in the clean corporate language of a man who'd spent a career writing policy documents that said complicated things simply enough to be voted on.

"I move to establish a formal oversight requirement for all command-structure decisions affecting classified ship systems. Specifically: any decision to monitor, modify, block, or interact with the ship's classified architecture—including the MX algorithm network, the broadcast mechanism, and the priority classification matrix—requires prior Council committee authorization. Emergency exceptions requiring immediate action may be authorized by the Council Chair within two hours of the action."

Walsh looked at the motion on her datapad. Her face showed nothing.

Eduardo Santos looked at Voss. The engineering anger—flat, precise—from the previous session was still there, but it had settled into something steadier. The anger of a man who'd had a night to recalibrate what he was angry at.

"I will address the motion," Santos said. "Not to oppose it. To refine it." He placed his datapad on the table. "The underlying principle is correct. The command structure has been managing classified systems with a level of unilateral authority that this Council's oversight mandate does not support. The filter deployment. The dormant algorithm responses. The atmospheric modification monitoring. These decisions were made operationally, reported after the fact, without prior committee review."

Walsh said nothing.

"But the two-hour authorization window is unworkable. Two hours in a fast-moving technical situation is a window that the emergency will have closed before the committee can open it. I would propose: six-hour authorization for non-emergency decisions, one-hour confirmation requirement for emergency decisions already taken."

Voss looked at Santos. The brief, calculating look of a man adjusting his tactical position. "I accept the amendment."

The revised motion was on the table. Walsh asked for discussion. The three regional representatives—the ones who hadn't aligned with either Voss or Santos in the previous week's sessions—asked procedural questions that were really questions about what the motion meant for the specific practical realities of emergency management on a ship in which emergencies were not hypothetical.

Tanaka was quiet. She'd been quiet since the session where she'd offered to resign and been told the offer was noted but not acted upon. Her silence in this session had the quality of someone watching a game and deciding which direction to move based on where the other pieces ended up.

The vote came at 1040.

Voss: yes. Tanaka: yes. Regional representative Marchand: yes.

Walsh: no. Eduardo Santos: no. Regional representative Kim: no. Regional representative Osei: no.

Four to three. The motion failed.

Voss put his datapad flat on the table. The movement of a man placing something down deliberately rather than dropping it—acknowledging the outcome without conceding the position.

"The Council has voted," Walsh said.

"The Council has voted today," Voss said. Not aggressively. Just the flat statement of a man noting a fact that would remain relevant after the session ended.

---

The corridor outside the chamber was empty. Walsh found Zara at the water point at the end of the hall—the small dispenser that produced water slightly less flat-tasting than the atmospheric recycler output, which passed for a amenity on Deck 5.

"Four to three," Walsh said.

"I heard the vote."

"It will be three to four next time if one more regional representative moves." Walsh took her own cup. Didn't drink—held it. "Osei voted with me today because I have done two years of relationship maintenance with his constituency, and that relationship maintenance is finite. It purchases a vote when the ask is not too large. Next time Voss's motion is framed more narrowly, more procedurally, in terms that make a no-vote look obstructionist rather than principled—Osei may land differently."

"How long?"

"Two sessions. Three if Voss is building carefully." She looked at the cup. "He is always building carefully."

"What would the oversight requirement actually change?"

"For immediate decisions: very little, if the authorization window is workable. For the patterns of decision-making—the accumulation of small unilateral choices that have been how this command structure operates since launch—it would change the tempo. Force every classified system interaction through a committee consideration. Make the process slower and more visible." Walsh looked at her. "Which is, honestly, not an unreasonable ask. The command structure made unilateral decisions for months. The committee found out about them in a briefing."

"The command structure was managing crises. The committee would have—"

"Complicated the management. Yes. I know." She didn't say it dismissively—the acknowledgment of someone who understood both sides of the argument from the inside. "I am not telling you Voss is wrong. I am telling you that whether or not Voss is wrong, the four-to-three margin is what you have and it is narrower than you need to feel stable."

Zara's comm buzzed. Santos the engineer.

"Sorry," she said to Walsh.

"Take it. I have eleven more conversations like this one before end of shift."

---

"Ferreira," Santos said when she answered.

"Tell me."

"I finished the analysis of his four-minute window. Captain—he was running a network connectivity test. He found a fault in the junction's relay cluster and was tracking it through the terminal to isolate the source. The test took four minutes longer than the documented task because the fault was in a secondary relay that required additional diagnostic steps." Santos's voice was the flat delivery of an engineer presenting data that contradicted the theory he'd been working with. "He was doing exactly what his work order documented. The extra time was legitimate."

Zara pressed her free hand against the corridor wall. The cool composite. The hum.

"Cross is with him now. Ferreira is—" Santos paused. "He is not pleased about the surveillance. He knows he was being watched. He knows why. His supervisor has been notified."

"Another Kowalski."

"An engineer doing his job, yes. The methodology fingerprint I identified is—" Another pause, this one carrying the weight of an analyst confronting the limits of his own analysis. "The fingerprint describes a way of working that is not unique to the saboteur. It describes competent navigation of the permission structure under time pressure. Any engineer who's worked in the network architecture long enough will develop something like it. The saboteur is using a method that looks like normal work because it is normal work, refined. I cannot distinguish the saboteur from the competent engineer by methodology alone."

"Then we need something else."

"Yes." He paused again. The third pause in sixty seconds—Santos managing information he was reluctant to deliver. "Captain, while Cross was investigating Ferreira, the navigation system's backup parameter layer was accessed through a different terminal. Junction 34-D, Deck 9. Accessed during an authorized maintenance window. A routine check. Logged correctly. Duration: on schedule."

The saboteur. While Cross was watching junction 22-C, the saboteur used junction 34-D. While the investigation's attention was on Ferreira, the real work continued through a different door.

"What was done in the access?"

"I am still analyzing. The preliminary read suggests—" Santos's voice went careful. "It is not a modification to the navigation parameters. It is an addition. Something was added to the navigation system's backup layer. Something that was not there before."

"What kind of addition?"

"I need two hours to characterize it fully. But Captain—the access patterns Santos cross-referenced, the structural modification methodology, the incremental work over seven months—whoever has been doing this has been building something. Not destroying. Building." He stopped. "The navigation system was sabotaged at the start. The hull resonance modifications expanded the broadcast. The atmospheric modifications are external—the entity's work. But this addition to the navigation backup layer—this is something the saboteur built and placed."

"Into the navigation system."

"Into the backup parameter layer. The system that contains the secondary navigation calculations. The fallback that the ship would use if the primary navigation failed."

The primary navigation was already damaged. The ship was already relying on Hassan's improvised star-position calculations. The backup layer—the last redundancy—had just been modified by someone who'd been planning this for months.

"Get me the characterization in two hours. And Santos—" She looked down the Deck 5 corridor, the clean-lit Tier 1 air, the full-spectrum lighting. "Don't alert anyone. Don't flag the terminal. Don't do anything that tells the person who made this addition that we're looking at it."

"Understood."

She closed the comm. Walsh was gone—she'd left while Zara was on the call, disappearing into the political schedule that a Council Chair maintained through the kind of constant relationship work that didn't get logged in security systems but kept four-to-three votes from flipping.

Zara stood in the corridor and thought about the shape of this. The saboteur building something in the navigation backup layer. The entity building something in the ship's network. The review body building a case from the MX data. Wendt building a revised understanding of the ship he'd designed. Thomas building a documentary record of a crisis that had been accumulating for seven months.

Everyone was building.

---

Webb stopped her in the Deck 7 transit corridor at 1400.

He was coming from the manufacturing sector—the section of the ship where the practical elements of daily life were produced and maintained. He'd been meeting with supervisors about the maintenance queue reform that the assembly's demand list had initiated, and he had the look of a man who'd spent two hours managing the practical gap between policy statements and operational reality.

He didn't soften his approach when he saw her. Webb never softened approaches. He adjusted their speed.

"Captain. The memorial service."

"I've heard the proposal."

"The families are asking. There are families of the eighty-three who haven't had any formal acknowledgment. The ship has had deaths since launch—accidents, medical conditions, the expected attrition of a large population over seven months. We hold services in the residential community centers. We've never held a ship-wide memorial." He fell into step beside her. "I understand the timing is not ideal."

"There is no ideal timing."

"No. But the ideal function is real. People need a place to put the grief that's been—" He stopped. Looked for the word. "Accumulating. The assembly addressed the political accountability. But the grief hasn't had a place. A ship-wide memorial gives it one."

"A ship-wide memorial brings tens of thousands of people into shared public spaces at a moment when the political temperature is the highest it's been since launch."

"Yes. It does. I know that." He didn't back away from it—the acknowledgment of a man who understood the risk and was asking her to accept it anyway. "Captain, the alternative is the grief continues to accumulate without a place, and it finds its own place eventually. It always does. A grief that has a formal structure is grief I can help manage. Grief without structure manages itself."

She looked at him. The working-class directness. The accent. The man who had been to every corner of the ship in seven months and knew what it felt like from the inside in ways she could only approximate from the outside.

"Date and location."

"Four days. Deck 12 and 14 common areas, with audio throughout all residential decks. Service led by the interfaith coalition—all faiths, secular option for those who want it. Open participation. I will manage the crowd."

"Cross will support the crowd management."

"I know. And Captain—I will not use the memorial as an assembly. The political work is happening in the Council. The memorial is for the dead." He held her gaze. "My word."

Webb's word was not nothing. In seven months she'd watched him operate, and the one thing she'd identified as consistent was that he kept the commitments he made in direct conversation, in terms like this—private, explicit, not performative. The commitments he made in public were political, subject to political pressure. The ones he made in private were personal.

"Approved," she said.

He nodded. The quiet nod of a man who'd asked for a hard thing and received it without celebration.

---

Santos called at 1600 with the characterization.

"The addition to the navigation backup layer is a trigger structure," he said. "A piece of executable code embedded in the parameter layer. It has two components. The first is a monitoring function—it tracks the primary navigation system's operational status. When the primary system falls below a specific operational threshold—when it is damaged enough that the ship would normally switch to the backup layer—the monitor detects this."

"And the second component?"

Santos was quiet for three seconds.

"The second component executes when the monitor detects the switch. It activates when the ship falls back on the backup navigation layer. And what it does—" His voice was precise and careful in the way it was careful when precision was the only available protection against the full force of the information. "What it does is corrupt the backup layer's parameter set. If the primary navigation system fails and the ship attempts to rely on the backup, the backup's parameters will be falsified. The navigation data the ship would fall back on would be wrong. Not randomly wrong—systematically wrong. The corruption is designed to produce consistent errors that would look like genuine navigation data until they'd compounded far enough that course correction would be impossible."

She said nothing.

"The saboteur has not yet damaged the primary navigation system again. The trigger is in place but the trigger condition has not been met. The primary system is still functional—damaged from the original sabotage, running on Hassan's improvised framework, but functional." His voice held steady. "Captain, when the saboteur damages the primary system—and I believe they will, I believe this is the sequence they have been building toward—the ship will switch to the backup layer and be given false navigation data. The ship will believe it is on a course it is not on."

The memorial in four days. The political pressure from the review body. The entity building something in the network architecture. The dormant algorithms. The saboteur who had been patient and incremental for seven months and had just finished placing the final component of whatever they'd been building.

"The trigger," she said. "Can it be removed?"

"Removing it carries the same risk as removing MX-3. If the saboteur monitors the backup layer—and they almost certainly do—they will know the trigger has been found. They may act immediately. Before we can identify them. Before we can stop whatever comes next." A pause. "Or they may have a manual override that activates the primary system damage without waiting for the trigger. If they know we've found the trigger, the trigger becomes irrelevant."

"Options."

"We leave the trigger in place and intensify the investigation. We find the saboteur before they act." Another pause. "Or we leave the trigger in place and we harden the primary navigation system to the point where the trigger condition cannot be met. If the primary system cannot be damaged enough to fail, the backup layer is never activated, and the corrupted parameters are never used."

"How long to harden the primary system?"

"Three weeks. Minimum. With full engineering resources."

"And the investigation?"

"Unknown. The saboteur is moving carefully. The addition was made during an authorized window through a legitimate terminal. We have the junction logged but we cannot narrow the access to a specific individual without correlating every person who had authorized access to that junction during that window—which is, again, several hundred people."

The ship hummed its constant note. The broadcast cycle was seven hours away.

The saboteur had just finished building their weapon. The trigger was in the navigation backup layer, waiting for the primary system to fail, waiting for the moment when the ship needed its fallback and found its fallback had been designed to lead it into the dark.

And somewhere in the same ship, the entity was building something too—something in the network architecture, incrementally, using the existing infrastructure as a foundation—and Preet Kaur was the only person who'd noticed, and she'd noticed because she'd been paying attention to the wrong thing for the right reasons.

"Start hardening the primary system," Zara said. "Quietly. Use the maintenance schedule to cover it. Three weeks. And keep watching the junctions."

She closed the comm. Four days until the memorial. Three weeks until the primary navigation was hardened. An unknown amount of time until the saboteur decided the setup was complete and the trigger was no longer the strategy.

The pressure was all pointing in the same direction. The only question was which thing would move first.