Chapter 99: Seventy Percent

Vasquez called at 0900 with good news, which should have been the warning.

"Eighteen hours," she said. "The beacon's secondary broadcast layer is almost fully isolated. I've severed four of the six communication pathways between the trigger and the MX frequency output. The remaining two are deep in the firmware and require a sequential extraction to avoid cross-contamination with the primary trigger function. Eighteen hours and the beacon goes dark."

"And the primary trigger?"

"Still active. The threshold is seventy percent. We're at—" She checked. "Sixty-nine point nine five. Captain, we're close. But the degradation rate has been stable at point-one percent per day. That gives us twelve to eighteen hours of margin before the threshold. Tight, but workable."

Twelve to eighteen hours of margin. Vasquez needed eighteen hours. The math was razor-thin. The kind of engineering timeline that worked on paper and collapsed in practice because practice included the thousand small variables that paper didn't account for.

Hassan's update came at 0930. The verification work was producing results.

"The entity's atmospheric data for HD 40307 g," Hassan said. Her voice had the measured tone she used when she was being careful with good news, as if good news required more caution than bad. "Actually, I've completed the cross-reference against our pre-launch spectroscopic surveys of the HD 40307 system. The entity's atmospheric composition profile matches our existing observations within the margin of error for spectroscopic analysis at forty-two light-years. But it extends them. The entity's data includes measurements our surveys couldn't make—subsurface geological stability, magnetic field strength, atmospheric pressure at sea level equivalent. These measurements are internally consistent and physically plausible."

"Does the planet work?"

"The data suggests it could support human colonization. The atmospheric composition is within breathable range with supplemental systems during the adaptation period. The surface gravity is one-point-two-eight Earth standard—higher than ideal, but manageable. The radiation environment is within habitable parameters." She paused. "I cannot confirm habitability conclusively without direct observation. But the data is—Captain, the data is encouraging. If the entity's measurements are accurate, HD 40307 g is significantly more viable than Kepler-442b."

Two pieces of good news before 1000. The beacon nearly disabled. The planet looking viable. Twelve hours of margin.

At 1047, Santos's hardening team ran a firmware validation sequence on the primary navigation core.

The sequence was standard. Part of the hardening protocol—a diagnostic check that verified the integrity of the navigation firmware before the next layer of protection was applied. Santos had run identical sequences four times in the past week without incident. The diagnostic was passive. It read the firmware and reported its state without modifying anything.

The diagnostic ran. The firmware responded. And inside the firmware, in a section that Santos's team had already hardened, a piece of code that had been dormant for seven months recognized the diagnostic pattern and interpreted it as a trigger condition.

Not the seventy-percent trigger. A different trigger. A secondary failsafe buried so deep in the firmware that Santos's hardening passes had treated it as native code. It had been there since before launch, installed not during the seven-month modification campaign but during the ship's original construction, by the person who'd written the navigation firmware in the first place.

The failsafe activated. It introduced a controlled degradation pulse into the primary navigation system—a microsurge that dropped system integrity by 0.1 percent in a single event.

Navigation hit 70.05 percent.

The primary trigger fired.

---

The bridge alarm was a sound Zara had heard in drills but never in operation—the navigation integrity warning, a three-tone alert that the designers had made unpleasant enough to guarantee attention and loud enough to carry through bulkheads. It filled the bridge at 1047 and did not stop.

Hassan was at her station. Her hands had gone still on the console. Not typing, not reaching for controls. Just still. Her eyes moved across the readouts and her mouth was slightly open and she was somewhere else—inside the numbers, inside whatever the numbers were telling her.

"Navigation backup layer is active," she said. Her voice was fast but controlled. "The trigger has fired. The backup layer is feeding modified position data into the primary navigation system. The modified data is—actually, the modified data is consistent with a position offset of approximately two-point-three degrees from our actual heading. The course correction systems are responding to the false data. They're adjusting our heading."

"The ship is turning," Jimmy said from communications. His voice was steady but his hands were gripping the edge of his console.

"The ship is making a course correction based on false position data. The correction is small—two-point-three degrees—but it's active and continuing." Hassan's fingers began moving again, fast. "Santos, I need you to isolate the backup layer from the course correction system. Cut the data feed."

Santos's voice came through the engineering comm. "Working. The backup layer's output is routed through three redundant pathways to course correction. I'm cutting pathway one now—" A pause. "Pathway one severed. The backup layer has rerouted through pathway two. It's self-repairing."

"Cut pathway two."

"Cutting—done. Rerouting to pathway three. This code is—" His voice tightened. "Captain, this code is military-grade adaptive. It's rewriting its own routing in real time. Every pathway I cut, it builds a new one."

Zara was on the bridge in forty seconds. She'd been in the corridor outside her office when the alarm sounded and had covered the distance at a pace that wasn't running but wasn't walking. She arrived to find the bridge crew at their stations, the navigation display showing the ship's heading as a line that was slowly, steadily bending.

"Status," she said.

"Course deviation: zero-point-four degrees and increasing," Hassan said. "Rate of deviation: approximately zero-point-one degrees per minute. The backup layer is feeding the course correction system a continuous stream of adjusted position data. Santos has cut two of three primary pathways. The backup layer rebuilt both."

"Santos. Kill it."

"I am trying to kill it." Santos's voice through the comm was flat. The voice of an engineer who was losing a fight with code that was better than his defenses. "The backup layer was designed by someone who anticipated exactly this response. Every isolation technique I apply, the code routes around. I need to shut down the entire backup navigation system to stop the data feed, which means losing our backup navigation capability entirely."

"Do it."

"Shutting down backup navigation." A pause. Console sounds. Then: "Backup navigation is offline. The course correction feed should be—"

The deviation line on the navigation display stopped bending. Hassan confirmed: "Course correction input from backup layer has ceased. We are holding at a deviation of zero-point-seven degrees from original heading."

Seven-tenths of a degree. A small number. Over the remaining distance to Kepler-442b, it meant missing the target by millions of kilometers. Over the distance to HD 40307 g, it meant nothing, because they weren't headed there.

"Can we correct back to original heading?" Zara asked.

"Yes," Hassan said. "Manual course correction. Twelve minutes to calculate, four minutes to execute. We'll be back on heading within—"

The mesh network activated.

Not the gradual activation they'd been tracking—the node-by-node expansion of the parallel infrastructure over seven months. This was a simultaneous power-up of all fifty-six active nodes at once, the mesh network going from passive monitoring to active operation in a single coordinated event. Every modified system on the ship surged with data traffic. The MX broadcast array jumped to full amplification. The secondary power feeds across forty-seven original nodes and nine new ones routed maximum power to the navigation interface pathway.

Hassan's console lit up across every display. "The mesh network is active. Full operational mode. Fifty-six nodes online. The mesh network is—it's attempting to access the primary navigation system through its independent pathway. Write access. It's trying to input course correction data."

"Block it."

"I can block the access at the navigation system's input filter. Blocking now." Her hands moved. "Blocked. The mesh network is rerouting. Trying a secondary access pathway through the sensor integration layer. Blocking. Blocked. Third pathway through the power distribution monitoring interface. Blocking—"

"Hassan."

"I can keep blocking but there are—" She counted under her breath. "Fourteen possible access pathways through the mesh network's connections to navigation-adjacent systems. I'm blocking them one at a time. The mesh network is trying them in sequence. When it runs out of fourteen, it will start combining pathways, using relay routes through intermediate systems. The number of possible combinations is—" She stopped. "Large."

"How long can you hold?"

"If I do nothing else, I can hold for approximately four to six hours by manually blocking each access attempt as it comes. The mesh network is fast but not instantaneous. Each reroute takes it thirty to ninety seconds to establish." She looked at Zara. "But if I'm doing this, I'm not doing anything else. No verification work. No entity communication analysis. Nothing."

Santos's voice from engineering: "Captain. The partial beacon. It fired when the trigger activated. Vasquez had isolated four of six pathways. Two remained active. The beacon broadcast on the entity's frequency with approximately thirty percent of its designed signal strength. Degraded data. Incomplete position information. But the entity received something."

The entity received something. And now, forty-three minutes after the trigger fired, the mesh network had gone active. Not because it had reached sixty-six nodes. Because the entity had received the partial beacon and decided not to wait.

"Broadcast cycle 37," Jimmy said from communications. "Incoming. The cycle timing is wrong—it's been less than two hours since cycle 36. The entity is broadcasting out of sequence."

"Hassan can't decode it," Zara said. "She's blocking the mesh network."

"I can decode it," Jimmy said. His voice was quiet but his posture was the straightest she'd seen it—the young man deciding what shape to hold himself in during a moment he'd describe for the rest of his life. "I've been studying Hassan's framework. I'm not as fast. But I can read the structure."

"Do it."

Jimmy worked for eleven minutes while Hassan blocked mesh network access attempts and Santos fought to contain the backup layer's attempts to reactivate through secondary systems and the ship held at its seven-tenths-of-a-degree deviation with the course correction system receiving contradictory inputs from three different sources.

"Cycle 37," Jimmy said. "One component. Addressed to the mesh network. The entity is ordering the mesh network to prioritize navigation access. Override all other functions. Dedicate full processing capacity to establishing write access to the primary navigation system." He paused. "And there's a data payload. The entity is sending course correction parameters. It's sending the mesh network the exact heading change required to redirect us to HD 40307 g."

Three inputs fighting for control of the ship's course. Santos's hardening trying to maintain the original heading. The backup layer's false parameters trying to introduce a deviation. And the mesh network, with fifty-six nodes and growing, trying to turn the Exodus toward a planet that an alien intelligence said could save them.

"Hassan, how long before the mesh network gets through?"

"Four to six hours if I keep blocking manually. Less if the entity sends additional bypass instructions. Less if the saboteur completes additional nodes." She looked at her console. "Captain, the mesh network's processing speed is increasing. The entity is optimizing its routing algorithms in real time. My four-to-six-hour estimate may be—actually, it may be closer to two to three hours."

Two to three hours.

Wei stood beside her at the center of the bridge. He'd arrived three minutes after the alarm and had said nothing since, standing with his hands behind his back and his face in the careful composure that she'd learned to read as his version of controlled alarm.

"Zara," he said. Quiet. Just her name.

She looked at the navigation display. Three competing inputs. The ship's course shown as a probability cone rather than a line, the cone widening with each passing minute as the competing inputs made the actual trajectory increasingly uncertain.

Two million people sleeping, working, arguing, grieving, living their lives inside these walls. Not knowing that the floor under their feet was the deck of a ship that was being pulled in three directions by three different ideas of where it should go.

Hassan blocked another access attempt. Santos reported the backup layer had found a fourth pathway. Jimmy monitored the entity's broadcast frequency for cycle 38.

The navigation display flickered. The probability cone shifted.

Zara stood at the center of the bridge and looked at the display and knew that the seventy-two hours the Council had voted for were gone. The decision was here. Now. On this bridge, in this hour, with incomplete data and inadequate time and two million lives and a voice from the void that said it was trying to save them.

She could shut down the mesh network. Sever every secondary channel, kill every node, cut the entity off from the ship's systems entirely. It would take hours and it would mean losing the entity's navigation data, the HD 40307 g coordinates, the alternative to Kepler-442b. It would mean continuing toward a planet that couldn't sustain them, with degraded navigation, with no backup system, with the knowledge that they'd been offered something and turned it down.

Or she could let the mesh network through. Accept the entity's course correction. Turn the Exodus toward HD 40307 g on the word of an intelligence they'd never seen, trusting a design they hadn't authorized, surrendering control of the ship's destination to something that existed at 14.7 degrees off the bow and had been waiting for this moment since before they launched.

Both options were wrong. Both options were the only ones available. And the time to choose between them was measured in hours, not days.

"Captain," Hassan said. "The mesh network just established a partial connection through pathway seven. I'm blocking it, but the connection was active for three seconds. Three seconds of write access. The mesh network input a partial course correction before I severed it."

The navigation display updated. The probability cone narrowed slightly in one direction. Toward HD 40307 g.

Three seconds. A partial correction. The entity had used three seconds of access to nudge the ship's heading.

Wei's hand on her arm. The brief touch.

"Zara. The pressure drop has arrived."

She stood at the center of the bridge and did not decide.

Not yet.