Chapter 65: Overreach

Braun said it would work. That was the part Zara kept coming back to afterward—the colonel's confidence, delivered in his flat military cadence, stripped of hedging or caveat, the professional assessment of an engineer who understood the system he'd built.

"The real-time sensor feed operates independently of the encrypted data storage," Braun said. They were in Engineering Bay 2 at 0700—Zara, Santos, Braun, Hassan patched in via comm from the bridge. "The encryption protects the archived data. The live feed is unencrypted because the system was designed for autonomous operation—the monitoring protocols need immediate access to sensor input to adjust their response parameters. Intercepting the live feed does not require the command code. It requires a physical connection to the sensor bus at any of the thirty-one node locations."

"A physical connection," Santos said. "Meaning we tap into one of the nodes."

"Meaning we connect a diagnostic interface to the sensor bus junction inside any secondary structural support that contains a node. The junction is accessible through a maintenance panel on the interior surface of the lateral brace. Standard composite panel—four fasteners, no special tools."

Santos pulled up the structural diagrams. Found the nearest node—Deck 14, Section 8, a lateral brace in a maintenance corridor between the residential block and an equipment storage bay. Accessible. Quiet. Low traffic.

"The interface protocol?"

"I will provide the handshake sequence. The sensor bus uses a standard military diagnostic protocol—Fleet Command's equipment interoperability standards. Your diagnostic hardware should be compatible with adaptation."

Should be. The words registered, but Zara let them pass. Braun was the expert. Santos trusted the engineering. Hassan needed the data. And the approaching signal—or approaching entity, or approaching computation—was 226 days away and getting closer, and the difference between understanding it and not understanding it might be the difference between preparation and catastrophe.

"Do it," Zara said.

---

Santos assembled the tap at 0900. A diagnostic probe modified with the interface parameters Braun provided—frequency matching, handshake timing, authentication sequence. The probe was small enough to fit in a toolkit, inconspicuous enough to look like standard maintenance equipment. Santos carried it to Deck 14 himself, accompanied by Braun and a single engineering technician named Reeves who'd been cleared for the structural assessment and whose discretion Santos trusted because Reeves was the kind of person who didn't ask questions she hadn't been invited to ask.

The maintenance corridor was empty. Standard lighting. The environmental systems hummed their usual frequency. The lateral brace was visible as a structural column running from floor to ceiling—the composite surface smooth, grey, unremarkable, indistinguishable from every other structural member on the ship unless you knew that inside its carbon fiber matrix, electromagnetic signals carried surveillance data through a network built by people who'd left Earth behind and whose institutional authority had evaporated the moment the *Exodus* cleared orbit.

Santos removed the maintenance panel. Four fasteners, as Braun had described. Behind the panel, the interior surface of the composite brace—smooth, with a recessed junction port that looked like a standard diagnostic access point. Military spec. Clean. The kind of hardware that was designed to be found by the right people and ignored by everyone else.

"The sensor bus junction," Braun said. He pointed to the port with the precision of a man who'd installed identical ports in thirty-one locations across fifty decks and remembered each one. "Connect the probe here. The handshake will initiate automatically. The sensor feed will begin transmitting within four seconds of successful authentication."

Santos connected the probe. The diagnostic display lit—handshake initiating. Authentication sequence cycling through the military protocol, the probe's modified firmware translating Santos's hardware language into Braun's network language, two generations of engineering reaching across a gap of design philosophy to shake hands.

Authentication accepted. The sensor feed opened.

Data streamed onto the diagnostic display—a torrent of information from the nearest node's sensor package. Structural stress readings. Thermal profiles. Vibration measurements. Power distribution maps. And there, buried in the sensor telemetry like a heartbeat beneath medical monitors, the external signal data. The node's passive sensors detecting electromagnetic energy from outside the hull—the ambient signal environment, cosmic background, and layered over everything, the carrier wave components that Hassan had been tracking for weeks.

"I have it," Hassan said through the comm. Her voice was tight—the controlled urgency of a navigator receiving data she'd been waiting days for. "The node's external sensors are—actually, the resolution is remarkable. Much higher than our bridge sensors. I can see the carrier wave components individually, their phase relationships, the synchronization structure. Give me five minutes to characterize the—"

The lights in the maintenance corridor flickered.

Not a brownout. Not a power fluctuation. A flicker—a single, sharp interruption lasting less than a second, the kind of transient that happened when a system drew power unexpectedly from the local grid. Santos looked at the diagnostic display. The sensor feed was still streaming. The probe connection was stable. Nothing in the tap's power consumption should have caused a grid disturbance.

"Santos." Braun's voice changed. The flat military tone sharpened into something with an edge—not alarm, but attention. The difference between a sentinel at rest and a sentinel who'd heard something. "Disconnect the probe."

"The data is still—"

"Disconnect the probe now."

Santos pulled the probe. The sensor feed cut. The diagnostic display went dark. The maintenance corridor's lights returned to their steady state, the flicker forgotten by the environmental system as quickly as it had occurred.

But the flicker hadn't been forgotten by the grid.

---

The power monitoring log showed the event at 0917. A transient power draw of 3.2 watts from the Deck 14, Section 8 grid junction—duration 0.7 seconds, source identified as the secondary structural support containing Node 17.

The draw was small. Insignificant in the context of a ship that consumed megawatts per hour. But it was logged, because the power monitoring system logged everything, because the engineers who'd designed the ship's grid had understood that in a closed system with finite energy, every watt mattered and every anomaly deserved a record.

The log entry went into the standard monitoring database. The database was accessible to the engineering department, the command structure, the Council's energy oversight subcommittee, and—through the commercial systems allocation that Voss had described in the Council session—the Corporate Consortium's environmental monitoring team.

Santos found the log entry at 0930. He called Zara immediately.

"The tap triggered a response from the node. When we connected the diagnostic probe, the node drew additional power—briefly, less than a second. The draw was logged in the standard power monitoring database."

"Which is accessible to—"

"Everyone. Including Voss's consortium monitoring staff."

Zara's hand tightened on the comm. The grip that substituted for the words she couldn't say on an open channel, the physical expression of a captain processing the realization that a classified operation had just left a fingerprint in a public database.

"Can we delete the log entry?"

"The power monitoring log is append-only. Entries cannot be modified or removed without engineering administrator privileges, and the modification itself would be logged. Deleting the entry creates a bigger trail than the entry itself."

"What does the entry show?"

"A transient power draw from a secondary structural support. Location, magnitude, duration. The entry does not identify the cause—it doesn't say 'diagnostic probe connected to hidden surveillance node.' It says '3.2-watt anomalous draw from structural element DS-14-08-L3.' To anyone reading the log without context, it's a minor grid fluctuation. Unremarkable."

"To anyone reading the log with context?"

Santos paused. "To someone who knows about the secondary network—who knows that the structural supports contain embedded systems—the entry confirms that something in the secondary structure drew power in a way that the standard monitoring didn't predict. It's a data point. On its own, meaningless. Combined with other information—the structural assessment, the network discovery, the ongoing investigation—it's a thread."

"And if someone pulls the thread?"

"They find the node. The junction. The diagnostic port. And they start asking why the engineering department was accessing a hidden military surveillance node at 0917 on a Tuesday."

---

Cross delivered the damage assessment at 1100. Not to the bridge—to Zara's closet-office on Deck 1, because the assessment included the kind of projections that couldn't survive contact with a bridge crew that included junior officers whose discretion wasn't battle-tested.

"Voss's consortium monitoring team reviews the power logs daily. Standard protocol—they scan for anomalies that might indicate environmental system degradation in the sectors they monitor. The Deck 14 entry is in a section adjacent to the Faithful's residential blocks. It falls within their monitoring scope."

"When will they see it?"

"The daily review happens at 1400. Four hours from now."

"And when they see it?"

"They flag it as an anomalous draw. Standard procedure is to forward flagged anomalies to the engineering department for investigation. The engineering department—Santos—receives the flag and can provide an explanation. The explanation can be truthful—'maintenance-related grid test'—or vague—'transient fluctuation under investigation.' Either way, the consortium team has a record that they forwarded an anomaly and received a response."

"That's the best case."

"That's the best case if Voss's monitoring team treats it as routine. The worst case is that someone on the team—someone with enough technical knowledge to understand what a 3.2-watt draw from a secondary structural element means—connects it to the structural assessment findings. Voss knows about the dual networks. He learned about the military infrastructure in the briefing with you three weeks ago. If his technical staff flags an anomalous draw from a structural element that Voss knows contains hidden infrastructure—"

"He knows we're poking at it."

"He knows someone accessed the network. He doesn't know why. He doesn't know about the sensor data, the signals analysis, or the approaching entity. But he knows the command structure is interacting with the military surveillance system in ways that weren't part of the disclosed structural assessment. And that gives him a question to ask in the next Council session."

Zara stood. The closet-office didn't allow pacing. She stood because sitting meant accepting the dimensions of the space, and the problem she was facing didn't fit inside any space she currently occupied.

"What does Voss do with this?"

"He asks the engineering department to explain the anomaly. Publicly, in the committee, where the question creates a record and the answer—whatever it is—becomes institutional documentation. If Santos gives a vague answer, Voss pushes for specifics. If Santos gives a detailed answer, Voss has the details. Either way, the committee is now aware that the command structure accessed the secondary network for purposes that weren't disclosed through the committee's oversight process."

"The committee doesn't have oversight of the secondary network. It's a classified military system."

"The committee's expanded scope includes structural systems. Voss will argue that the secondary network, embedded in the structural supports, falls within the committee's jurisdiction. And he'll be technically correct, because the committee charter doesn't distinguish between documented and undocumented structural systems."

"He'll use this to expand the committee's authority."

"He'll use this to expand his authority. The committee is the mechanism. Voss is the operator." Cross set his datapad on the desk. The screen showed the power monitoring log—a single line entry, mundane, the kind of data that nobody looked at twice unless they were looking for something specific. "Captain, the entry itself is minor. A 3.2-watt fluctuation in a structural element. But in the context of Voss's ongoing push for institutional access—the consortium monitoring, the committee expansion, the Faithful's withdrawal—it's ammunition. Small-caliber, but ammunition."

"Can we get ahead of it?"

"We have three hours before the consortium's daily review. In those three hours, Santos can file a preemptive explanation in the engineering log—maintenance test, grid diagnostics, routine assessment of structural monitoring elements. The explanation provides cover. It's not a lie—the tap was a diagnostic action. But it's incomplete, and Voss will know it's incomplete, because Voss understands the difference between an explanation and a story."

Zara's comm buzzed. Wei. She answered.

"Zara, we have a pressure drop." Wei's voice carried the particular calm that meant the news was bad and he was managing his delivery. "Braun is requesting an immediate meeting. He says the tap triggered something in the network—not the power draw. Something else. The node we accessed has changed its monitoring state. Its power consumption has increased from 0.7 watts to 1.1 watts. Sustained. Not a spike. A step change."

"The node woke up."

"The node is processing. Braun says the diagnostic probe's authentication sequence was recognized by the network as an authorized access event. The node has shifted from passive monitoring to—" Wei paused. The pause of a man whose mining slang didn't include a term for what he was about to describe. "—to active interrogation. It's querying the other thirty nodes. Asking them for data. Compiling a status report."

"A status report for whom?"

"For whoever authenticated. For us. Braun says the network thinks an authorized operator has connected and is requesting a system-wide status update. The update is propagating through all thirty-one nodes. Every secondary structural support in the ship is now drawing 1.1 watts instead of 0.7."

"That's visible."

"Zara, that's very visible. Thirty-one nodes increasing power consumption simultaneously across all fifty decks. The grid monitoring system is going to flag thirty-one anomalous draws in the next routine scan. The consortium's daily review is going to see not one anomaly but thirty-one. And the pattern—simultaneous activation across the entire ship's secondary structure—is not something that can be explained by maintenance testing."

The closet-office was too small. The ship was too small. The distance between a diagnostic probe and a political crisis was three hours and thirty-one nodes and a power monitoring log that recorded everything and forgot nothing.

"Braun can stop it?"

"Braun says the status update will complete in approximately forty-five minutes. After completion, the nodes will return to baseline. The question is whether they return to 0.7 watts or stabilize at the new 1.1 level."

"If they don't return to baseline—"

"Then the network has permanently changed its operational state in response to our access. And the power increase is visible in every grid monitoring system on the ship. Permanently."

Zara closed the comm. Looked at Cross. Cross looked back with the expression of a security chief watching a contained situation become uncontained, the professional assessment of damage that was already done and couldn't be undone.

"Three options," she said. Her voice was compressed. Clipped. The captain's crisis voice, the one that dropped articles and shortened sentences because efficiency was the only response to a situation that had outgrown the time available to manage it. "One. Santos files the preemptive explanation before the consortium review. Covers the original anomaly. Doesn't cover thirty-one simultaneous draws."

"Correct."

"Two. We go to Walsh. Disclose the network access. Get ahead of the committee questions. Control the narrative."

"That puts the committee formally on notice that the command structure is conducting classified operations involving hidden infrastructure. Walsh protects you politically but can't protect you institutionally. The committee will demand oversight."

"Three. We go to Voss directly. Tell him what happened. Give him the information before he finds it himself. Take the political hit now instead of letting him weaponize the discovery."

Cross's jaw tightened. "Going to Voss means giving him leverage voluntarily. He'll want something in return. He always does."

"He'll want something in return regardless. The question is whether we negotiate from a position of disclosure or a position of discovery. If he finds it himself, we're defending. If we tell him first, we're managing."

"You're asking me to recommend between bad options."

"I'm telling you there aren't any good ones. Pick."

Cross picked up his datapad. Looked at the power log. Looked at the schematic showing thirty-one nodes drawing 1.1 watts across fifty decks, the military surveillance network waking up because someone had knocked on its door and the door had opened wider than intended.

"Walsh. Disclose to Walsh first. She's the Council chair. She's your most reliable ally. If Voss finds the anomalies before you've briefed Walsh, you've lost both the political cover and the institutional protection. Walsh gives you at least one of those."

"Walsh it is. Get her to my office in thirty minutes."

Cross left. Zara stood alone in the closet-office with its exposed conduit and its lubricant smell and the knowledge that she'd authorized a diagnostic tap that had woken up a military surveillance network, created thirty-one visible power anomalies across the entire ship, handed Voss a political weapon he hadn't asked for, and failed to get the sensor data Hassan needed because the probe had been connected for less than three minutes before Braun told them to pull it.

Three minutes. The data Hassan had captured in that window was a fragment—partial, incomplete, a glimpse through a keyhole that had closed before the eye could focus. Maybe enough to answer the question of whether the delay was spatial or computational. Probably not. And the cost of those three minutes was an institutional crisis that would reach the Council before the day ended and Voss before the week was out.

She'd overreached. The word was precise and she used it on herself without flinching because flinching was a luxury and the situation didn't offer luxuries. She'd wanted the sensor data badly enough to authorize a physical access that Braun had described as straightforward and Santos had executed competently and that had failed not because of incompetence but because a system built to respond to authorized access had done exactly what it was designed to do. The network had recognized an operator. It had woken up. And now its waking was visible to every monitoring system on the ship, including the ones controlled by a man whose political instincts would recognize the pattern before the engineering department finished writing its explanation.

The conduit overhead vibrated. Environmental systems. Recycled air. The mundane machinery of survival, carrying the ship's breath through corridors where thirty-one hidden nodes were drawing power they hadn't drawn yesterday, compiling a status report for an operator who hadn't meant to ask for one, answering a question that nobody had intended to pose.

Forty-five minutes until the update completed. Three hours until the consortium review. And somewhere in the gap between those deadlines, the institutional architecture of the *Exodus*'s governance was about to discover that its captain had been doing things with the ship's hidden infrastructure that the governance system didn't know about, hadn't authorized, and couldn't control.

She picked up the comm. Called Walsh.

"Councilwoman. I need thirty minutes of your time. My office. Now."

Walsh's response was immediate. The veteran politician's instinct for urgency, the recognition that a captain who said "now" meant something had already gone wrong.

"On my way."

Zara set down the comm. Pressed her palms against her eyes. The cybernetic eye powered down behind the pressure. Darkness. The brief, total darkness that was the only privacy a captain had—the space behind closed eyes, where the mistakes were still fresh and the consequences hadn't arrived yet.

When she opened her eyes, the office was the same. Small. Exposed conduit. Lubricant smell. And on her datapad, the engineering feed from Santos showing thirty-one nodes settling into their new power state: 1.1 watts. Sustained. The network that had been sleeping was awake, and the ship that had been singing was singing louder, and the captain who had authorized the tap was standing in a converted storage closet waiting for the Council chair to arrive so she could explain how a three-minute diagnostic test had turned a classified investigation into a political crisis.

Twenty-eight minutes until Walsh arrived. Forty-one minutes until the status update completed. Two hours and forty-seven minutes until the consortium review.

And somewhere, getting closer at 0.4 seconds per day, something was still listening.