Santos called at 0600 with the answer she didn't want.
"The test sequence ran." His voice had the flat quality of a man reporting results that had cost him sleep. "I set up passive monitoring on the mesh network's internal traffic last night. Non-intrusive, no active queries, just listening to what was moving through the secondary channels. At 0347, the mesh network executed a series of operations matching the test sequence Hassan decoded from component six."
"All of it?"
"All of it. Data routing, power distribution, sensor access. And the navigation handshake." He paused. "Captain, the mesh network successfully interfaced with the primary navigation system. Read access confirmed. Write access confirmed. The connection was active for eleven seconds. No modifications were made. The entity ran the test and disconnected."
"Write access."
"Write access. The mesh network can send commands to the navigation system. Right now, today, without the saboteur's trigger, without the backup layer. Through its own independent pathway." Another pause. "I verified this three times. The mesh network has operational control capability over the ship's navigation. The entity chose not to use it."
She stood in her closet-office at 0600 on a ship that an alien intelligence could steer at will.
"Santos. Can we cut the mesh network's connection to navigation?"
"I can sever the secondary data channel at the navigation junction. That closes the pathway. But the mesh network has forty-seven nodes with redundant routing. If I cut one path, the network can route around the gap through adjacent nodes. To completely isolate navigation from the mesh network, I would need to sever every secondary channel in every system connected to navigation. That isâ" He stopped. Counted in his head. "Fourteen systems. Fourteen simultaneous disconnections. Each one visible in the maintenance logs. Each one a flag that tells the saboteur we've found the mesh network."
"And if the saboteur knows we've found it."
"They accelerate. They already moved the trigger threshold from forty to seventy percent after the memorial. If they know we've mapped the mesh network, they have options we haven't identified yet. The mesh network has capacity for additional nodes. Empty junction points. The construction is not complete."
She closed her eyes. The cybernetic prosthetic hummed against the socket. "Meeting. 0800. My office. Wei, you, Hassan, Cross, Victor. Closed."
---
They fit poorly in the closet-office. Six people in a space designed for one, the supply crate serving as a bench for Victor and Hassan while Wei leaned against the doorframe and Cross stood at attention near the conduit and Santos sat on the floor with his toolkit beside him like a man who'd given up on formality three crises ago.
"Twelve people on this ship have the system access level required to build the mesh network," Zara said. "We're going through them."
Santos pulled a list from his tablet. "I compiled the access profiles overnight. Twelve individuals with Tier 1 engineering authorization, which grants the ability to create parallel sessions, modify firmware at the system level, and access maintenance authentication protocols across departments."
"Names," Cross said.
Santos read them. Twelve names. Some Zara knew well. Some she'd spoken to once or twice in seven months. Each one a person with the technical knowledge and system access to have built a second nervous system inside the ship while everyone else was managing crises.
"We can eliminate five based on physical location," Santos continued. "The mesh network modifications occurred during specific maintenance windows. Access logs show when each modification was made and which section of the ship it occurred in. Five of the twelve were verifiably in other sections of the ship during one or more of the critical windows. Their badge access, their shift logs, their project assignments place them in locations incompatible with the modification sites."
"That assumes badge access records are reliable," Cross said.
"Badge access can be spoofed by someone with Tier 1 authorization. But spoofing badge access while simultaneously appearing on shift in another location requires either a co-conspirator or a physical impossibility. Three of the five were on active bridge duty during critical windows, observed by multiple crew. Two others were in medicalâone receiving treatment for a broken wrist, one performing surgery. I'm comfortable eliminating them."
"Seven remain," Wei said. "Santos, can you walk us through them?"
Santos looked at the list. "Dr. Elena Vance. Chief Scientist. Designed the Exodus's core systems architecture. She has the broadest access of anyone on this shipâbroader than mine. She was part of the original design team and her authorization was never rescoped after launch because her ongoing research requires access to the systems she designed."
"Access to all forty-seven modified systems?" Cross asked.
"Access to every system on the ship. Her design credentials were carried over from the shipyard."
Zara filed this. Vance. The woman who'd built the ship. Who understood every system because she'd drawn the specifications for them.
"Next," she said.
"Dr. Ansel Brandt. Senior systems architect. Part of the original design team. Responsible for the environmental and structural monitoring systems during construction. His access covers thirty-one of the forty-seven modified systems. He would have needed to use a colleague's credentials for the remaining sixteen."
"Or had someone else do those sixteen," Cross said.
"Correct."
"Next."
"Lena Ostrowski. Chief power systems engineer. Oversaw the ship's entire power distribution network during construction. Her access covers the power routing modifications directly, and her authorization level grants access to the other systems as a secondary function."
"Where was Ostrowski during the memorial?" Cross asked.
"On shift in Engineering. Lower decks. The modification that occurred during the memorial was on Deck 19. Engineering lower decks are on Deck 22. The transit time between them is approximately eleven minutes. The surveillance gap during the memorial was thirty minutes. It is possible but tight."
"Next."
"TomĂĄs Herrera. Structural systems lead. Original design team. Access to structural and sensor systemsâtwenty-three of the forty-seven."
"Also possible," Santos said. "Also tight on transit times for some of the modification windows."
"Next."
"Dr. Yuki Sato. Communications systems architect. Designed the MX broadcast array." Santos paused. "Her access to the broadcast array is direct and complete. She would be the natural person to modify the array's input channels to receive data from a mesh network."
"Was she on the original design team?"
"She was the communications systems lead during construction. She reported to Dr. Vance."
Zara looked at the list. Five names. One more.
"The sixth is myself," Santos said.
The office went still.
"I have Tier 1 authorization. I have access to all forty-seven systems. I have been physically present in sections of the ship where modifications occurred during relevant timeframes. I have been leading the hardening project, which gives me direct access to the navigation systems we're trying to protect." He looked at each person in the room. "If I were the saboteur, every defensive measure we have built is compromised."
Cross spoke first. "Have we considered the possibility that the person leading the defense is also running the offense?"
"I've considered it," Santos said. "So should everyone in this room."
"Zara," Wei said. His voice was quiet. The lowered register he used when the conversation required careful handling. "Have we discussed how we proceed with this information?"
"Cross. Can you verify Santos's location during every modification window?"
"I can verify the windows we've identified. If there are modifications we haven't found yet, I can't verify what I don't know about."
"Santos. You said the mesh network has empty junction points. Capacity for additional nodes. Can you tell me how many?"
"Nineteen empty junction points. Meaning the completed network would have sixty-six nodes, not forty-seven."
"Nineteen more modifications to be made. By someone on this list."
"By someone on this list. Yes."
She looked at the seven names. Vance. Brandt. Ostrowski. Herrera. Sato. Santos. And a seventh she hadn't named yet.
"The seventh," she said.
Santos checked his tablet. "Lieutenant Commander Preet Kaur."
The room went quiet again. Kaur. The engineer who'd first identified the entity's network construction in the MX system. Who'd built the analysis framework that Chakraborti was now using. Who'd come to Santos with her unauthorized research and whose work had been incorporated into the review body's record.
"Kaur identified the entity's construction pattern," Wei said.
"Kaur has Tier 1 authorization through her role as senior network infrastructure engineer. Her access covers the communications and data systemsâthirty-eight of the forty-seven modified systems." Santos's voice was careful. "She was also the first person to analyze the entity's network construction inside the MX system. Her analysis was accurate and thorough. If she is the saboteur, she handed us a map of part of her own work."
"Or she handed us a map to control the narrative around its discovery," Cross said. "Better to reveal it yourself than to have someone else find it and draw conclusions you can't manage."
Victor, who had been silent, shifted on the supply crate. "Wouldn't you agree," he said, "that the diagnostic question here is not who has access, but who has motive? Seven people have the technical capability. How many have a reason?"
"We don't know the motive," Zara said. "The entity said the agent's purpose is something we haven't understood. We've been assuming the motive is destruction. The mesh network says otherwise."
"Then what is the motive?"
"Communication. The saboteur has been building infrastructure to communicate with the entity. Or for the entity to communicate with the ship. Or for the entity to control the ship's systems." She looked at the seven names. "The motive is contact. Directed, engineered, planned contact between the Exodus and whatever is at 14.7 degrees off the bow."
The room absorbed this.
"Captain," Victor said. His voice had shifted to the formal register. "I have information that may be relevant to the question of planning."
She looked at him.
"The missing maintenance records from David's accident. The three-week window of access logs that should exist and do not." He pressed his palms together. "I have been working with the archival teamâThomas's group, the documentation project. They have access to the pre-launch administrative records that were loaded into the ship's archive at departure. I asked them to search for the deletion record. When files are removed from a database, the deletion event itself is logged in the system metadata. The file is gone but the fact of its removal is recorded."
"You found the deletion record."
"I found it. The maintenance access logs for the shipyard section that failedâthe section where David diedâwere deleted from the archive three days before the Exodus launched. The deletion was performed from a terminal in the engineering department. The authorization code used was a Tier 1 engineering credential."
Seven names. Tier 1 credentials. Three days before launch.
"Which credential?" Cross asked.
"The deletion log records the authorization level but not the individual code. Tier 1. That is all the metadata retained." Victor looked at Zara. "Someone with Tier 1 engineering access deleted the records of the maintenance failure that killed your husband three days before this ship left Earth. The same level of access required to build the mesh network."
The conduit hummed. Six people in a small room looking at the same picture from different angles, and the picture was this: someone had been planning this for years. Not months. Years. Before the ship launched. Before the sabotage. Before the entity's signal was detected. Someone with the access to delete records about a shipyard accident and the access to build a hidden nervous system inside the ship and the knowledge to design modifications that passed every diagnostic.
"Santos," she said. "The mesh network modifications. The code. Is it improvised or pre-written?"
He blinked. The question had not occurred to him and the answer came with the delay of a man reprocessing data through a new filter.
"Pre-written," he said slowly. "The firmware modifications in each of the forty-seven systems are too clean for field work. No debugging artifacts. No iteration marks. No version history. Each modification was installed as a finished product. As though it had been developed and tested elsewhere and deployed to the target system in a single operation."
"Developed and tested before launch."
"That is... yes. That is consistent with the code quality. These modifications were not developed on the ship. They were brought aboard ready to install."
Seven people. One of them had boarded the Exodus with a complete set of firmware modifications designed to convert the ship into a communication device. Had spent seven months installing them on a schedule. Had built a trigger in the navigation backup layer. Had adjusted that trigger during the memorial chaos.
Had planned all of it before leaving Earth.
The saboteur wasn't an infiltrator who'd decided to act after launch. Wasn't a crew member who'd been radicalized or recruited or broken by the journey.
The saboteur was an architect. Someone who'd designed the modifications the same way they'd designed the ship itselfâwith the patience and precision of a professional doing work they'd planned for years.
"We're not looking for someone who turned against the mission," Zara said.
The room was quiet.
"We're looking for someone who was never on the mission to begin with."
