Chapter 83: The Designer's Burden

Hofer sat in the security office with his hands on the table and his face doing nothing to hide what he thought of being there.

He was thirty-two. Round face, engineer's build, the kind of person who carried himself with the unself-conscious confidence of someone who'd never had reason to doubt his own judgment. His left cheekbone had started to bruise from the altercation in the Deck 11 corridor—a purple-gray shadow beneath his eye that he'd declined to let the medic look at because the medic was lower priority than being in this room.

He'd said this to Cross's operative. Not as a complaint. As a fact.

Zara sat across from him. Cross stood near the door.

"You told people in the Deck 11 overflow that the atmospheric modifications are a communication system," Zara said.

"Yes."

"That they are the signal."

"Yes."

"Where did you get that characterization?"

Hofer's eyes moved to the door, then back to Zara. The brief look of a man checking whether his employer was behind him, then deciding it didn't change anything. "Friedrich. He'd been working on the atmospheric analysis since the modifications began. He shared it with me this morning."

"And you decided to share it with an assembly crowd."

"I decided that people who are breathing modified air have a right to know why the air is being modified." He said it without aggression—a simple statement of principle that he'd clearly worked out in advance and was not interested in revising under pressure. "I understand that the information is classified. I understand that Dr. Wendt should not have shared it with me before the review body completed its analysis. I made a calculation. The classification was keeping information from people it affected directly. The people who asked me questions at that assembly weren't asking about policy. They were asking about their air."

"You caused a physical altercation."

"Someone disagreed with me about whether the modifications were dangerous. The disagreement became physical. I did not initiate the physical component."

Zara looked at him for a moment. The composed certainty of a man who'd done something he believed was right and was prepared to pay the cost of it without flinching, which was different from bravado because bravado flinched when the cost became specific. This was the quieter conviction of someone who'd already accepted the specific cost before he'd opened his mouth.

"Mr. Hofer. The information you shared was technically accurate."

He waited.

"The characterization—'we are the signal'—is an accurate description of what the analysis indicates." She kept her voice level. "It is also incomplete. The entity's purpose is not established. The modifications may serve functions we have not yet determined. The phrase carries a certainty we do not have."

"Seven thousand people were in that assembly. They were talking about the atmospheric modifications in terms of danger, of toxicity, of something being done to them against their will. The only response I had that addressed the actual situation was the technical one." He pressed his hands flatter on the table. "I told them what it is. Not what it might be. Not what I speculated. What the analysis shows."

"The analysis shows an entity transmitting environmental specifications through a dormant algorithm. What that means is not established."

"What it looks like to six thousand people who just learned their medical emergencies were deprioritized by a software system is that something else is now adjusting their air without their consent. That needed context. I gave it the most accurate context I had."

Zara sat with this. The room's fluorescent hum. Cross near the door, his face professionally blank, logging everything.

"You're released," she said.

Hofer stood. The careful movement of a man managing a bruised face.

"Your access to Wendt's analysis is suspended. Direct any information about the review body's findings to the review body's public liaison, not to public assemblies."

"That's reasonable."

He walked to the door. Cross opened it.

"Mr. Hofer."

He turned.

"You were right that people should know what the modifications are. You were wrong that you were the person who should tell them, in that format, without review body authorization." She held his gaze. "The difference between those two things matters."

He thought about this. "I know," he said, and left.

---

Wendt was waiting outside.

He'd positioned himself in the corridor with the patient composure of a man who'd decided that waiting was more efficient than not waiting, and who had very few feelings about the situation. When Hofer came through the door and walked past him without a word—not cold, just the particular silence of two people who'd already processed their disagreement before this moment—Wendt watched him go and then turned to Zara.

"He will not compromise the review body's work," Wendt said. "He acted independently. He was wrong to. But his motive was legible and his error is not a pattern."

"He knew things you gave him. He made a decision you didn't authorize."

"Yes." A pause. Not for effect—for the word he wanted next. "The responsibility for that is mine."

Wendt didn't apologize. He used the word *responsibility* the way other people used apologies—as a formal acknowledgment that something had happened that he would have prevented if he'd made a different choice. No emotional weight attached. Just the accounting.

"The review session is at 1700," Zara said.

"Two hours. I would like to use them."

She led him to the closet-office. Not the briefing rooms—the briefing rooms were now associated with the review body and the committee and the structures of disclosure that had been producing documents and votes and public findings for the last thirty-six hours. The closet-office was small and smelled like lubricant and conduit and the half-eaten protein bar that Santos had left on the corner of the desk the night before.

Wendt sat on the supply crate. Looked around the office with the appraising attention of a man cataloguing a space he'd designed in schematic and was now encountering in its inhabited form.

"Tell me about the consultant," Zara said.

"I will tell you everything I know. Some of it is uncertain—I have dates, I have communication logs, I have technical specifications, but I have no identity. The consultant used encrypted channels that were standard for the era but that predate my ability to verify the routing."

"Name."

"He identified himself as Dr. Arik Solen. I had no way to verify the identity. The name does not appear in Fleet Command's contractor records. It does not appear in any corporate consortium personnel database I have checked. The name may be false."

"Or he was never officially contracted."

"Or he was contracted through a channel that does not appear in official records. There is a category of Fleet Command work that is not documented in standard contractor databases—classified programs, special projects divisions, advanced research groups. I was aware of this category. I accepted that he might be operating in it."

"What did he look like?"

"I never met him physically. All communication was remote. Encrypted video calls. His image was obscured—standard practice for classified contractors concerned about facial recognition. His voice was—processed. Unidentifiable by vocal pattern. I knew his name, his technical knowledge, and nothing else."

Zara leaned back in the folding chair. "His technical knowledge."

"He understood generation ship architecture at a level that suggested direct construction experience. He understood the specific engineering challenges of designing a vessel meant to carry a closed biological system across interstellar distances. He understood the hull composite's resonance properties before I had fully characterized them. He understood things that should have been proprietary to my design process." Wendt's hands were folded in his lap. "I attributed this to Fleet Command's classified technical division. They had access to my preliminary schematics through the project's oversight structure. It was plausible."

"And the structural modifications. The ones implemented through maintenance orders after launch."

"I identified three sets of hull resonance modifications in the first eight months of the journey. Small adjustments—the kind that fall within normal engineering tolerance for a new vessel settling into operational conditions. I flagged two of them as anomalous in my private analysis because the modifications improved broadcast efficiency in ways that matched Solen's original specifications. The third modification correlated directly with the entity's second response packet."

"Someone on this ship has been executing Solen's instructions."

"Someone with engineering access and the technical knowledge to implement hull resonance modifications through maintenance protocols. And the authorization to file those modifications as routine settling-period adjustments."

"How many people on this ship have that level of hull systems access?"

"Eleven. Including your chief engineer and myself." He paused. "And Dr. Elena Vance."

The name was in the outline—Chief Scientist, knows every system, hiding the ship's true limitations. Essential and dangerous. But she was still eight hundred chapters away from being revealed as the saboteur. In these early chapters, she was simply a name among suspects.

Zara wrote the name. "Vance designed the ship's operational systems."

"I designed the hull and structural architecture. Vance designed the systems that run inside it. The boundary between those domains is, in practice, more permeable than the organizational chart suggests. A hull resonance modification of the type I identified would require understanding of both domains." His voice remained flat. "I want to be precise about what I am and am not saying. I am not naming Dr. Vance as the person implementing these modifications. I am saying that the technical competency required falls within her knowledge set."

"Along with ten other people."

"Along with ten other people."

Santos called at 1615. Zara held up a hand to Wendt, took the comm.

"Captain. I've been running the structural modification orders against the navigation sabotage access logs. Looking for methodology fingerprints—timing patterns, authorization sequencing, the specific signature of how someone moves through the network when they're working outside their documented scope."

"And?"

A pause. The kind Santos used when the information was worth more than a rapid delivery. "They match. Not perfectly—the navigation sabotage was faster, more aggressive, designed to complete in a single session. The hull modifications were incremental, spread across months. But the underlying authorization pattern—the way the actor moved through the permission structure before making the modification—is the same sequence. The same intervals. The same technique for avoiding the automated verification flags."

"The same person."

"Or two people trained in the same method. The probability of independent development of an identical evasion pattern is—" He paused again, this time for calculation rather than precision. "Very low. Captain, whoever implemented the hull resonance modifications also sabotaged the navigation system. Or they learned to work from the same teacher."

Wendt was watching her. He'd heard Santos's voice without the words, and his expression held the patient stillness of a man who was waiting to learn how much worse the situation had just gotten.

"The teacher," Zara said. "Or the consultant."

She closed the comm.

"Santos found a methodology match," she told Wendt. "The hull resonance modifications and the navigation sabotage use the same access pattern."

Wendt was quiet for three full seconds. The longest silence she'd heard from him.

"Then Solen's agent has been on this ship since before the first hull modification. Since the early operational period." His hands unfolded and then folded again. The only physical expression of something moving behind the composed surface. "Or Solen himself is on this ship. And has been since launch."

The conduit overhead hummed. The ship's circulatory system, the infrastructure that Wendt had designed and that someone was using as a vehicle for actions that the ship's captain was only now beginning to understand.

---

The 1700 review session was held in the Deck 3 briefing room with the same seven members and Santos in the observer's chair and a tension in the room's geometry that the 0900 session hadn't had.

Chakraborti had spent six hours with the biological data. She presented standing up, which she hadn't done this morning, and her presentation was shorter than Victor's had been, which in Zara's experience meant the findings were either very simple or very alarming.

"The entity's data acquisition model shows systematic interest in population hierarchy," Chakraborti began. "This is consistent with standard xenobiological first-contact hypothesis—an unknown intelligence trying to understand an unknown species will attempt to map social structure. What I did not expect is the sophistication of the mapping."

She put the analysis on the central display. Data visualizations—network graphs, correlation matrices, the technical vocabulary of population biology applied to the MX algorithm's acquisition patterns.

"The entity has received thirty-two broadcast cycles of data from the ship's environmental and medical monitoring systems. During that time, the data acquisition has shown systematic bias toward certain signal categories." She highlighted the graph. "Physiological stress markers. Communication frequency patterns. Access log data—who uses which systems, how often, during what times. Movement patterns. Proximity data."

"The medical surveillance," Oyelaran said.

"Yes. But not for health assessment. The data categories being prioritized correspond to social network analysis—the same variables that a sociologist would use to map influence, authority, and communication flow in a human population." Chakraborti's hands moved to her next display. "The entity is not building a medical model of the ship's population. It is building a power map. It is trying to determine who makes decisions. Who influences whom. Where authority originates and how it flows."

The room was quiet.

"The tier classification data that MX-9 encoded and transmitted," Wendt said from the head of the table. His voice was level. Precise. "The corporate hierarchy. The resource allocation structure."

"The entity received the tier data early in the broadcast cycle sequence. My analysis suggests that the tier classification was one of the first coherent structural data sets the entity was able to process—a clear hierarchical organization with consistent correspondence between tier code and resource distribution." Chakraborti's expression was the careful neutral of a scientist presenting unwelcome findings without inflection. "From the entity's perspective, the tier system would look like an intentional map of the ship's authority structure. A guide to who has power and who does not."

"And MX-3's atmospheric modifications," Zara said. "Tier-differentiated."

"The entity read the tier data and used it to sort the population. Not punitively—the modifications don't harm the lower tiers. But the differentiation is real. The entity is treating different tiers as different categories." Chakraborti paused. "I don't have certainty about what those categories mean to the entity. But it is treating them as meaningful. As though they correspond to something more than resource allocation."

"As though they correspond to biological significance," Wendt said.

"Possibly. Or social significance. The distinction may not exist in the entity's model of what we are."

Park, the Webb coalition structural engineer, spoke for the first time in the session. "What does it want?"

Chakraborti looked at him. "I don't know."

"Can we ask?"

The room's attention converged on the question. Seven people, Santos against the wall, Zara at the end of the table—all holding the same silence that forms when a simple question has an answer too complex to deliver quickly.

"The entity's response patterns contain structured elements that Hassan has been analyzing," Zara said. "The navigation team has been attempting to decode the responses for the last three weeks. We have not established a communication protocol."

"But it's getting smarter," Park said.

"Twenty-seven percent improvement in response speed over thirty days."

Park absorbed this. "What happens at a hundred percent?"

Nobody answered. Because nobody knew. The entity's learning curve had a trajectory but no destination—a line climbing into a space that the ship's instruments couldn't reach.

The session ran ninety minutes. When it broke at 1830, the review body had a new action item: Chakraborti would develop a formal recommendation on whether the entity's data acquisition should be characterized as intelligence-gathering, first-contact protocol, or something else that the existing taxonomy didn't cover.

In the meantime, MX-3 continued its atmospheric modifications. Cycle four had completed during the session. The cumulative atmospheric adjustment now stood at 0.08 percent, still within safe parameters, still differentiated by tier, still serving a purpose that the entity understood and the ship's crew did not.

Zara left the briefing room at 1835. Santos caught up with her in the corridor.

"Captain. The 1800 broadcast cycle."

"I know."

"The entity's response arrived twelve minutes ago. Hassan has been processing it."

"What did it contain?"

Santos looked at his datapad. Then at her. The expression of an engineer who'd been delivering alarming information with steady professionalism for two days and who had finally received a piece of information that made professionalism feel inadequate.

"The response contains the standard environmental specifications. And a new element." He handed her the datapad. "Hassan has not decoded it fully. But the new element has a consistent reference signature—a code that appears seven times across the response packet. The code cross-references with a specific data set in the MX-7 broadcast."

Zara looked at the display. The code. The cross-reference. The data set it pointed to.

Her command access log. The record of which systems she interacted with, when, at what authorization level, with what effect on ship operations. The trace that her command codes left in the ship's network every time she made a decision that touched any monitored system.

The entity had received thirty-two cycles of that data.

It had just sent back a response that specifically referenced it.

"The entity knows who runs this ship," she said.

"Hassan believes the response contains a query structure—a request for specific information. The query is directed at your command code signature." Santos's voice held steady. "The entity is not addressing the ship. It is addressing you."

The corridor hummed. The broadcast cycle complete, the response packet delivered, the entity at 14.7 degrees settling into its calculations with data that was growing more detailed and more organized with every transmission.

Something across a billion kilometers of dark had learned her name—not her name, exactly, but her function. Her place in the hierarchy. The pattern her decisions made in the ship's nervous system, repeated and recognizable and specific enough that thirty-two cycles of population data had been enough to find her.

She handed the datapad back to Santos.

"Get me Hassan."