Chapter 86: Wake

Santos called at 0214.

Zara answered before the third buzz. She'd been lying on her rack with her eyes open, which was not the same as being awake, but the transition between the two states took less than two seconds.

"MX-5," Santos said. "It activated eighteen minutes ago. I have been monitoring since MX-3's modifications began—I set automated alerts on all dormant sections. Captain, MX-5 is different."

She was already putting on her boots. "Different how?"

"MX-3 is environmental. It interfaces with atmospheric systems. MX-5 is—it is accessing the mission archive. The pre-launch planning documents. Crew assignment records. Decision logs from the Exodus Program's executive committee. Everything that was uploaded to the ship's permanent record before departure."

"It's reading the history."

"It is not reading it the way we read it. The access pattern is systematic—it is extracting specific categories of data. Decision trees. Authority records. The documentation of who approved what at what stage of the mission planning."

She was in the corridor before he finished. Deck 4, down to Engineering Bay 2, the route that had become a kind of neural path over the last week—the path between where she slept and where she found out what had happened while she slept.

"Has Cross been notified?"

"Yes. He is already in the bay."

---

The bay's monitors showed MX-5's data acquisition in real time—a visualization of the algorithm moving through the archive, each document it touched lighting up in the map Santos had generated. The mission planning archive was massive: nine years of Exodus Program documentation, uploaded to the ship's permanent record in the final weeks before launch. Procurement decisions, personnel evaluations, engineering assessments, political correspondence between Fleet Command and the corporate consortium, the policy documents and risk assessments and meeting transcripts that represented the institutional record of how humanity had decided to leave its dying world.

MX-5 was working through it with the systematic precision of someone who had a specific organizational framework in mind—not reading randomly, not sampling, but following a logic that prioritized certain categories over others. Decision documents first. Authority records second. Assessment data third.

Cross was at the secondary console. His face held the particular attention of a man who'd stopped sleeping and hadn't decided yet whether he was going to start again.

"The maintenance supervisor," Zara said. "Ferreira. Did his four minutes trigger MX-5?"

"I cannot confirm that. The timing is consistent—MX-5 activated approximately four hours after Ferreira's unaccounted access window. But four hours is a long lag for a trigger-response relationship. More likely the activation is independent." Santos's hands were moving between displays. "MX-5's trigger conditions may have been met by the deep scan probe from three days ago—the same probe that activated MX-3. The probe may have initialized a delayed sequence. MX-3 first, MX-5 after a specified interval."

"A cascading activation."

"Built into the design. Wendt's specifications included dormant sections with linked triggers—I have confirmed this with him. The intent was sequential deployment rather than simultaneous activation, which would have been detectable. The architecture is—patient." He paused. "Whoever designed the dormant section framework understood that the activations needed to be spaced to avoid triggering the ship's anomaly detection systems."

The same patience as the hull resonance modifications. The same patience as the saboteur's incremental work. Everything about this architecture moved slowly, in ways that looked routine until the picture had enough pieces to become recognizable.

"What specifically is MX-5 accessing?"

Santos highlighted a section of the document map. "Pre-launch destination assessment documentation. The formal evaluation of Kepler-442b conducted by the Exodus Program's scientific committee in the eighteen months before launch."

The destination assessment. The documents that would show what Fleet Command had known about Kepler-442b before the ship launched—whether the planet had been evaluated, what the evaluation had found, whether the assessment had been classified or buried or simply not shared with the people who were supposed to be traveling there.

This was Arc 3 territory—chapter 300, the revelation that leadership had known the destination was questionable. Zara was in chapter 86. The outline was clear: the loss of innocence, the discovery that leadership knew, came at the arc's end. Not now.

But MX-5 was reading those documents now. The entity would know before the crew did.

"The entity receives the broadcast next cycle," she said.

"In six hours."

"MX-9—the encoding algorithm—will package MX-5's data acquisition for transmission."

"Yes."

"So in six hours, the entity will know what Fleet Command knew about Kepler-442b before we launched."

Santos didn't respond to that. There was no useful response. The fact sat in Engineering Bay 2 in the specific way that facts sat when they had consequences that couldn't be immediately addressed—with the weight of things that required processing time that wasn't available.

"Can we stop MX-5?"

"The same risk as stopping MX-3. Another dormant section may activate. We have sixteen remaining."

"Monitor and document. Every document it touches. I want the full access log before the next broadcast cycle."

---

At 0400, Thomas Auber arrived in Engineering Bay 2.

Santos had called him. The historian had access to the mission planning archive through his documentation research—he'd spent four months cross-referencing the pre-launch documents with the ship's operational record, building a formal historical account of the Exodus Program's decision-making process. His archive access was authorized and logged, his presence in the documentation system well-established.

He walked into the bay the way he walked everywhere—without hurry, without the charged urgency of someone who'd been woken at 0400 and was trying to signal that being woken at 0400 was appropriate to the situation. Just the steady presence of a person who moved at his own pace and found it adequate.

"You called because of MX-5," he said to Santos. Not a question.

"The documents it is accessing include the Kepler-442b destination assessment. You have been working in the same archive. I thought—your categorical framework might help us identify what MX-5 is prioritizing."

Thomas looked at the document map on the screen. He studied it for a minute without speaking. His eyes tracked the highlighted documents—the ones MX-5 had accessed—with the systematic attention of someone reading a list rather than a map.

"It's looking for liability," he said.

Cross turned from the secondary console.

"The documents it's prioritizing—" Thomas pointed to a cluster of highlights. "These are all decision authority records. Who had sign-off authority at each stage. Who approved the final destination selection. Who approved the classification of the destination assessment." He moved his finger to another cluster. "These are the risk acknowledgment documents. The formal records where specific individuals confirmed they'd received and understood risk assessments. The documents that would establish, in a legal or accountability sense, who knew what and when they knew it."

"Why would the entity care about liability?"

Thomas looked at Cross with the patient expression of a person who was used to questions that assumed answers he didn't have. "I don't know that it does. I'm describing the pattern I see. The documents it's accessing are the documents a human institution would access when building a case for institutional accountability. Whether the entity has a concept of accountability—" He looked back at the screen. "I can't say that."

Zara watched the document map. MX-5's systematic movement through the archive. "It's building a record of who made decisions."

"Yes. And specifically, the record of who knew that the decisions were made on incomplete or classified information." Thomas folded his arms—not defensive, the posture of someone thinking. "The destination assessment documents are the most interesting category. If those documents show that the destination was evaluated as unsuitable, and if the people who signed the liability records knew that—the entity would have a complete picture of what this ship was launched on. And who was responsible."

"The entity can't do anything with that information."

"From where it is right now, no." He said it carefully. "But it's processing that data. Building a model that includes it." He looked at Zara. "I've been documenting this journey for seven months. The most consistent thing I've observed is that the people making decisions had less information than they needed and more information than they shared. The entity is getting the full record. The gap between what leadership knew and what the population was told—the entity is going to have both sides of that gap in its model."

The broadcast cycle was five hours away.

"You have a specific concern about the Kepler-442b assessment documents," Zara said.

Thomas was quiet for a moment. The specific quiet of a man deciding how much to say in a room that contained a security chief and a captain and a senior engineer.

"The assessment was classified before launch," he said. "I know this because my archive access includes the document inventory—I can see the file headers without seeing the classified content. The classification was applied nine months before departure. I've been trying to understand why a destination assessment would be classified nine months before departure, when the destination was already public knowledge." He paused. "I don't have an answer. But MX-5 is accessing the classified content. Whatever the assessment found—the entity will know in five hours."

---

Hassan's call came at 0630. Thirty minutes before the broadcast cycle.

She'd been running her decoding analysis overnight. Her voice on the comm had the particular energy of a mathematician who'd spent eight hours not sleeping for reasons she was glad about.

"Actually—Captain, I need you and Santos in the nav room. Actually, I need you both now. I have the structure." Her voice had picked up speed—the verbal acceleration of Amara Hassan processing excitement. "I've been working on the entity's response packets for three weeks. Actually, seventeen days and—that's not the point. The point is I have the query structure. The entity is not just responding. It is asking questions. Specific, structured questions. And I can read them now."

Zara left Santos at the Engineering Bay console and walked to the navigation room with the brisk efficiency of someone who'd been awake since 0214 and had stopped expecting the night to produce rest.

Hassan was at the primary nav console with four secondary screens active and the expression of someone who'd been staring at the same data for so long that she'd begun to see it differently—not as data but as meaning.

"Show me."

"The entity's response packets have three layers," Hassan said, her hands moving between screens. "Layer one is the environmental specifications—that's MX-3's data, the atmospheric adjustments. Layer two is something we've been calling 'feedback data'—we thought it was the entity sending processed information back to us. It's not feedback. It's queries. The layer two data is structured as questions in a mathematical format." She pulled up the query structure on the main display. "Questions built from the categories of data the entity has been receiving. It has learned the ship's data structures and it is asking for specific values within those structures."

"What is it asking?"

"Three categories of questions." She highlighted each. "Category one: population health metrics. Aggregate biological data—the state of the population, how we are as a group. Category two: resource distribution. The tier data, the allocation patterns, the current state of the queue prioritization." She paused. The hesitation of a mathematician who'd found a number that surprised her. "Category three: authority structure. Specifically—who makes decisions. How decisions propagate through the hierarchy. What the relationship is between individual command authority and population-level outcomes."

"It wants to know who's in charge."

"It wants to understand how authority works on this ship. The questions aren't just 'who leads'—they're more specific than that. It's asking about the relationship between authority and consequence. Whether the decisions made by the authority structure produce outcomes that affect the population in measurable ways." Hassan lowered her hands. Her feet were moving slightly—the nervous energy she usually managed into calculation. "Captain, the entity has been watching this ship for four months. It has received thirty-two broadcast cycles of population data. And its questions suggest it is trying to understand a specific dynamic: whether the people in charge on this ship are responsible for what happens to the people they're in charge of."

The Deck 8 corridor outside medical bay three. Victor's data. Eighty-three names.

"It's asking the same question as the assembly," Zara said.

Hassan blinked. The mathematically-precise mind encountering a sentence that had meant something different from what she'd computed. "I—actually. Yes. The structural logic of the query is consistent with—yes. The entity wants to understand whether the ship's leadership is accountable to the ship's population." She looked at the display. "Whether authority comes with consequences."

The broadcast cycle began at 0700.

MX-7 processed sensor data. MX-9 encoded and packaged. The composite hull harmonized at 11.7 hours. The signal went outward at 14.7 degrees, carrying thirty-three cycles of accumulated population data and one new element: MX-5's acquisition from the mission planning archive. The classified destination assessment. The liability documents. The record of who had known and who had approved and what they had approved without telling the people who were going.

In six hours, the entity would process this cycle's data and begin formulating its response.

In six hours, it would know what this ship had been built on and who had built it that way.

And it would ask, in the structured mathematical language that Hassan had spent seventeen days learning to read: *Does the authority structure of this vessel know what it has done to the population it governs?*

Santos arrived in the navigation room at 0715. He was reading his datapad.

"MX-5 completed its archive pass," he said. "Last document accessed was the Kepler-442b final assessment. Classification level: maximum." He looked up. "Captain, the document header shows the assessment was signed by thirty-one individuals. Executive committee members, scientific directors, Fleet Command leadership. The document represents the formal knowledge structure of everyone who knew where we were really going—and what they knew about it."

"Thirty-one names."

"The entity has them all."