Chapter 85: The Wrong Shape Again

Cross had three names.

He put them on Zara's desk at 0730 with the datapads stacked in order of likelihood—most probable at the top, least at the bottom, the ranking based on thirty-six hours of cross-referencing access logs against the methodology fingerprint Santos had identified in the hull resonance modifications.

"The methodology pattern shows a specific way of navigating the permission structure before making an unauthorized modification," he said. "The actor creates a brief window—ten to fourteen seconds—between accessing a legitimate maintenance function and then pivoting to the restricted layer beneath it. The pivot is fast enough to avoid the automated verification flag but requires knowing the flag's timing threshold. That knowledge narrows the pool significantly. Only people with engineering access who've also reviewed the network security architecture would know the flag threshold."

"How many people is that?"

"Forty-seven on the initial pull. When I added the timing constraint—the specific hours and authorization sequencing—three names remained."

Zara looked at the top datapad. Preet Kaur, forty-one, senior environmental systems engineer, Deck 3 residential. Tier 1. Clean record, seven months of documented competent work, no disciplinary flags, no complaints from supervisors or colleagues. Her access log showed eleven instances of the methodology-matching pattern over the past three months.

"Eleven," Zara said.

"That is what moved her to the top. The other two candidates show the pattern two times and four times respectively. Kaur's pattern repeats with a regularity that suggests habit rather than incident."

Zara set the datapad down. "Who is she?"

"Environmental systems—specifically, the atmospheric processing infrastructure for the upper decks. She designed the maintenance schedule for the hull-adjacent environmental controls. She has full access to the resonance parameter systems."

"The same systems where the hull modifications were implemented."

"Yes. Her technical knowledge is consistent with the modification methodology. Her access is correct. Her pattern is correct." Cross's voice had the particular flatness of a man who'd been right about suspects before and wrong about suspects before, and who was no longer confident about the ratio. "Captain, I want to be clear that the Kowalski situation has affected how I am presenting this. I am not leading with a recommendation. I am presenting what the data shows and asking you to assess the next step."

"What does the data show beyond the access pattern?"

"Her residential classification is Tier 1. She lives on Deck 3. Her maintenance authorization covers the hull-adjacent systems on Decks 1 through 6. She has professional access to the exact systems where the resonance modifications were implemented." He paused. "She also has a personal log that mentions the entity—personal notes, not official communications—that date from before the command structure's public disclosure. She was aware of the broadcast mechanism independently."

"Everyone in the engineering division who worked on the hull systems was potentially aware of the broadcast mechanism independently. Wendt designed it. His team built it."

"Her notes are more specific than general awareness. She describes the entity's position—the 14.7 degree bearing—in a personal log entry from month two. Before Hassan's analysis was published. Before Santos's assessment."

Zara sat with this. Thirty-seven names on Victor's list of dead, still in her head from this morning. Kowalski in the security office with his hands on the table, not a saboteur, a maintenance worker. The methodology that Cross had described—authorized access, legitimate credentials, behavior that looked routine because it was filed as routine.

"Let's talk to her," she said.

Cross nodded. Not the nod of a man who was sure—the nod of a man who was proceeding because proceeding was the job, and the job required proceeding even when the last time he'd proceeded he'd detained the wrong person.

---

They met Preet Kaur in her office on Deck 4.

Her office was small—the shared workspace of a senior engineer who'd been given a partial partition in the engineering section's open floor plan. Two monitors, both active with atmospheric processing data when they arrived. A personal plant on the corner of the desk—a small succulent in a recycled container, the kind of tiny environmental insistence that some passengers made to signal that the ship was a home and not just a vessel.

She was forty-one and looked it. Not in the exhausted way that most of the ship's personnel looked their ages after seven months of crisis—in the specific way of a person who'd been doing hard work for a long time and had achieved a settled relationship with the difficulty of it.

"Captain." She didn't stand. Her eyes moved between Zara and Cross with the assessment of someone who'd seen enough of the current week's events to recognize that this visit was not routine. "Security Chief. Should I be concerned about something?"

"We'd like to ask you some questions about your access logs," Cross said.

"Which ones."

The directness was jarring—not defensive, not the reflexive anxiety of a person who had something to hide. The flat acknowledgment of a person who'd been expecting this conversation and had decided the best approach was to accelerate it.

"The hull-adjacent environmental system accesses," Zara said. "Specifically, the pattern of access to the resonance parameter layer beneath the environmental controls. Eleven instances over the past three months."

Preet Kaur looked at her for a moment. Then she turned to her monitor, called up a data set, and rotated the screen toward them.

"I have been studying the entity's atmospheric specifications," she said. "Independently. Without authorization, which I am aware of." Her voice was steady—the delivery of someone presenting a confession they'd pre-organized. "I started in month two, when I noticed anomalous resonance patterns in the hull composite during a standard atmospheric system check. The anomalies corresponded to the 11.7-hour pulse that Wendt eventually published. I recognized the architecture—I built part of it. I knew what I was looking at before the public assessment was released."

She pulled up a folder. Three months of personal analysis—documentation, graphs, theoretical frameworks, the systematic work of an engineer applying her expertise to a problem she'd found and hadn't reported.

"Why didn't you report it?" Zara asked.

"Because the command structure had classified the assessment. Because I didn't know whether what I was seeing was a threat or a feature. Because I was—" She paused. A brief pause that had something behind it—not guilt, not fear. Something closer to the discomfort of a person who'd made a choice she wasn't certain was right. "I wanted to understand it myself first. Before I handed it to a process that might classify my analysis the same way it classified everything else."

"You accessed restricted system layers to run your analysis."

"Yes. The resonance parameter data I needed wasn't accessible through standard environmental monitoring protocols. I used the threshold window in the network security architecture—the gap between automated verification checks. I knew about the gap from the initial system design documentation." She looked at Cross. "I was not modifying the systems. I was reading them. Every access in my log was data retrieval, not data modification. You can verify that from the read-write records."

Cross was already pulling up the read-write logs on his datapad. His jaw worked—the physical processing of a security chief whose prime suspect was explaining themselves in a way that was both troubling and exculpatory at the same time.

Zara watched him run the verification. The thirty seconds of silence were quiet in a specific way—the silence of information being checked against a framework that the information might not fit.

"All read," Cross said. His voice was flat. "Eleven accesses, eleven read operations. No write operations."

Preet Kaur nodded. She'd known the logs would say that. She'd been waiting for them to check.

"The Deck 7 junction," Zara said. "The corridor 14-A terminal. Have you used it?"

"Never. My analysis work was conducted entirely through my office terminal. I didn't need physical access to remote terminals."

"The entity's bearing—14.7 degrees. You documented it in a personal log in month two."

"I calculated it from the resonance pattern timing and the hull composite's directional response characteristics. The calculation was approximate—my instruments were less precise than Hassan's analysis. But the bearing was consistent with what the structural assessment eventually published." She met Zara's gaze directly. "Captain, I am not the person who modified the navigation system. I understand why my access pattern looks suspicious. I used a method that requires the same knowledge as the navigation sabotage. I am the wrong shape."

The phrase landed in the office with a specific weight. *The wrong shape.* Not innocent—that word was too simple. The wrong shape for the space the investigation needed to fill.

Zara looked at Cross.

Cross looked at the read-write log. At Preet Kaur. At the atmospheric analysis on the screen—three months of independent research, unauthorized, careful, and completely separate from the navigation sabotage that had been the reason they were here.

"You will formalize your analysis and submit it to the review body," Zara said. "The entity data you've developed independently may be relevant to their assessment."

"I understand."

"Your unauthorized access to the restricted parameter layer is being flagged. Retroactive authorization is not being granted. Your engineering supervisor will be notified."

"Also understood."

Zara stood. Cross gathered his datapads.

"Captain," Preet Kaur said as they moved toward the door. "My analysis of the resonance patterns shows something the review body hasn't addressed yet. The entity's response packets aren't just environmental specifications. The data structure suggests the responses are building something. Incrementally. Each packet adds to a framework that started with the first response cycle." She turned back to her screen. "I think the entity is constructing something in the ship's network. Not modifying it. Constructing something new. Using the existing infrastructure as a foundation."

The succulent on the corner of her desk. The atmospheric monitoring data on both screens. Three months of unauthorized research by a woman who'd found a mystery in the hull architecture and decided to investigate it herself because the official channels had been closed.

"Submit the full analysis," Zara said.

---

She found Thomas in the Deck 8 corridor outside medical bay three.

She hadn't expected to find anyone there—it was between shift changes, the corridor carrying the quiet of a space between occupancies. But he was standing near the observation port, one of the small windows that faced out into the black, writing something on a datapad with the concentrated attention of a person in the middle of a thought they didn't want to interrupt.

She would have walked past.

He looked up.

"Captain Okafor." He said it the way someone says a name they've learned but haven't used yet—carefully, with the slight weight of a first application. He was mid-forties, lean, the kind of face that looked like it had been used for thinking rather than for anything else. "I'm Thomas Auber. Ship's historian."

"I know who you are." She'd seen his access logs—he was listed in the documentation division, authorized presence in most public-access areas. His name had appeared in the review body's observer request list. She hadn't met him.

"You're coming from medical," he said. It wasn't quite a question.

"Does that matter?"

"Not to anything I'm working on." He looked back at his datapad. "I was documenting the current period—I try to write down what I'm observing before I understand it, because once I understand something I can't write it the way it looked before. It changes the language." He paused. "This week has been—productive for that. In the worst possible way."

Despite herself: "What did you write?"

He showed her the datapad. Not the full text—just the last few lines, turned toward her so she could read them if she chose. *Six thousand people in one room, and they weren't angry. They were trying to understand something that the people in charge hadn't understood yet either, and they knew it, and they were patient about it in the specific way that patience comes when you have nowhere else to go and the people around you are in the same position.*

She looked at the words for a moment. Then at him.

"The patience won't last," she said.

"No," he agreed. "But it's there right now. I think it deserves to be recorded."

She walked on. He went back to writing.

It was three sentences. A historian observing the ship the way Kowalski had observed the atmospheric readings—quietly, after hours, paying attention to the thing that nobody had officially authorized attention for. But the words had named something true, and true things stuck.

---

Cross called at 1820.

"Captain. The navigation system access point. Corridor junction 22-C on Deck 14, the same terminal cluster that was flagged in Santos's analysis. It was accessed forty minutes ago."

"Who?"

"A maintenance supervisor. Rodrigo Ferreira, Tier 3, Deck 11 residential. His access was during an authorized maintenance window—he was scheduled for a routine check of the junction's network infrastructure. The access was logged, the work order was filed, everything was documented." Cross paused. "The timing was correct. The authorization was correct. The documentation was correct."

"What did he do with the access?"

"That is what Santos is analyzing. The access duration was four minutes longer than the documented task requires. Four minutes of unaccounted activity on a terminal that connects to the navigation system's backup parameter layer."

"The saboteur."

"Possibly. Or a supervisor whose routine work took longer than the estimated task time." His voice was careful. Precisely calibrated between two explanations that the data couldn't distinguish. "Captain, the methodology the saboteur uses is legitimate work. That is the problem. When they are at a terminal, they look like someone doing authorized maintenance. Because they are doing authorized maintenance—and something else. The four extra minutes could be the something else. Or it could be a slow afternoon."

The wrong shape. Or the right shape. Or a shape that looked right enough to arrest and wrong enough to ruin, the way Kowalski's shape had looked wrong enough to detain and right enough to authorize.

"Pull his full file. Don't approach him yet. Watch the terminal cluster."

"For how long?"

"Until we know what he built in those four minutes."

She closed the comm. The Deck 8 corridor was empty now. Thomas had gone back to wherever historians went when the day's observations were complete.

The ship hummed. The entity's next broadcast cycle was three hours away. Preet Kaur had said the entity was building something in the network—constructing, not modifying, using the existing infrastructure as a foundation. Seventeen dormant algorithms waiting in the walls.

And somewhere in this ship, a saboteur was also building something. Also using the existing infrastructure. Also working incrementally, carefully, behind the cover of authorized windows and legitimate credentials, adding four minutes here and eleven accesses there to something that hadn't revealed its shape yet.

The difference between them was intent, and intent was the thing that didn't show up on logs.

The investigation had been running for seven months and had caught one maintenance worker doing unauthorized overtime on scrubber diagnostics and one engineer doing unauthorized research on an alien entity. Cross's new methodology had produced Preet Kaur—three months of read operations and one plant and a sentence about the wrong shape.

Somewhere in the ship, the right shape was still walking around with valid credentials and filed work orders, and they were still three days away from knowing what it was building.