Santos hated working with her.
He hated the way she touched the firmware interfaces with familiarity, the way her fingers found menu options he'd spent weeks searching for, the way she navigated the navigation architecture like a woman walking through her own house. Because it was her house. She'd built it. Every pathway, every redundancy loop, every firmware module that Santos had been painstakingly mapping since the cascadeâVance had designed them eleven years ago and carried the blueprints in her head.
She was faster than him. That was the part he hated most.
"The backup fragment from Sector 7 is corrupted at the header level," Vance said. She was at the software analysis station, the one she'd organized by function during her years as chief scientist, the station where everything had a label and every label was in her handwriting. "The corruption pattern is consistent with a power surge during the cascade. The data payload is intact. We can extract it by writing a custom header parser that ignores the damaged fields and reads directly from the data offset."
Santos looked at his own analysis of the same backup fragment. He'd spent three days determining that it was corrupted and two more days concluding that the corruption was unrecoverable. Vance had reached the same diagnosis and proposed a solution in four minutes.
"Show me the data offset," he said.
She pulled up the fragment's binary structure. The headerâthe section of code that told the system what the fragment contained and how to use itâwas garbled. Random characters where organized data should have been. But below the header, the payload data was clean. Rows of hexadecimal values representing navigation calibration parameters, intact and readable if you knew where the data started.
"The standard parser reads from the header," Vance said. "The header is destroyed, so the parser throws an error and marks the fragment as unrecoverable. But the data offset is fixed. It's always 256 bytes from the fragment start. Hardcoded during the original design." She looked at him. "I hardcoded it because I wanted a recovery pathway that didn't depend on the header being intact. The header was always the most vulnerable component."
She'd built the recovery pathway before the ship launched. Before the sabotage. Before the cascade. She'd designed the navigation system to be recoverable from exactly the kind of damage that her own actions had caused.
Santos wanted to ask her whether that was conscience or insurance. He didn't ask. He opened a development terminal and started writing the custom header parser.
"I can write it faster," Vance said.
"I'm sure you can."
They worked in silence for twenty minutes. Santos wrote the parser. Vance reviewed his code as he wrote it, not by looking at his screen but by listening to his keystrokes and inferring the command structure from the rhythm of his typing. When he finished, she pointed to line 47.
"Off by one. The offset is 256 bytes, not 255. Zero-indexed arrays."
He fixed the error. Ran the parser. The backup fragment's data payload extracted cleanly: 4,800 lines of navigation calibration parameters that had been locked behind a damaged header for two weeks.
"That's the inertial reference data for the port-side sensor cluster," Vance said. "With this fragment and the three others we recovered yesterday, we have approximately forty percent of the calibration dataset for the primary navigation sensors. Enough to begin preliminary alignment."
Forty percent. Santos ran the calculation against his rebuild timeline. The original estimate was six months at forty percent capacity. With the recovered fragments and Vance's knowledge of the architecture, he'd already compressed the timeline to four months. Maybe three and a half if the remaining backup sectors yielded similar results.
Cross's predictions had been accurate. Vance was cutting the rebuild time in half.
"The remaining fragments are in Sectors 12 through 18," Santos said. "The cascade damage was heaviest in the aft sections of the navigation core. Those sectors may have lost data payload as well as headers."
"Sectors 12 through 14 are likely recoverable. The power surge pattern during the cascade propagated bow to stern, which means the aft sectors received the surge last and with diminished intensity. Sectors 15 through 18 are less certain." Vance pulled up the cascade damage mapâher damage map, the one with the red ink annotations that she'd been maintaining since the first day of aftermath. "I need access to the physical navigation core to assess the storage media. Some of the data may be recoverable from the hardware itself, even if the software interface shows it as destroyed."
"You want to go to the navigation core."
"I want to examine the storage media. The navigation core is a room, Eduardo. Not a weapon."
Santos stared at the cascade damage map. The red ink was Vance's handwritingâthe same precise block letters that labeled every instrument in her lab. She'd annotated the map with failure timestamps, component identifiers, and repair notes. The annotations were detailed, accurate, and useful. He'd been referencing them for two weeks.
"I'll schedule an escort," he said. "Cross will assign a security officer."
"Acceptable."
They returned to the firmware. Two people working on the same system from opposite ends of the same bench, not looking at each other, not speaking except to exchange data, rebuilding the thing that one of them had destroyed and the other had failed to protect.
---
The agricultural ring's growing bays occupied a cylindrical section of the ship that rotated at 2.1 RPM to generate artificial gravity for the crops. The rotation was essentialâplants grown in microgravity produced malformed root systems and reduced yields. The ring's centripetal force provided 0.4g, enough for viable agriculture, and the growing bays inside the ring produced approximately sixty percent of the ship's fresh food.
The cascade had damaged the ring's thermal regulation system. Three of the twelve growing bays had experienced temperature excursionsâBay 4 reaching 52 degrees Celsius for eleven minutes, Bay 7 hitting 48 degrees for twenty-three minutes, Bay 9 fluctuating between 15 and 44 degrees for over an hour. The heat had killed crops. The temperature fluctuations had stressed root systems. The overall agricultural capacity was reduced by approximately sixteen percent, and the repair timeline for the thermal system was three months.
Sixteen percent sounded manageable until you calculated what it meant for two million people. The reduction translated to approximately 900 fewer calories per person per day from fresh food sources. The deficit was currently being covered by the ship's dry storesâprotein concentrates, freeze-dried grains, preserved legumesâbut the dry stores were a finite reserve intended for emergencies, not baseline nutrition.
Chief Agronomist Osei walked the damaged bays with Santos and a thermal engineering team. Osei was fifty-three, Ghanaian, a woman whose career had spanned three agricultural universities and two failed terraforming projects before the Exodus recruited her to feed a city in a can. She'd kept the ring running through seven months of flight, managing crop rotations, pest control, water allocation, and the constant minor crises of industrial agriculture in a rotating cylinder.
The cascade was not a minor crisis.
"Bay 4 is a total loss," Osei said. She stood among the blackened remains of what had been three thousand square meters of soybean plants. The heat had cooked them. The stalks were brown and brittle, the leaves curled into dry husks, the pods shriveled. The soil beneath them had baked to a crust that cracked under her boots. "The thermal excursion destroyed the crops and the soil microbiome. We cannot replant until the soil is reconstituted. That requires reintroduction of bacterial cultures from our reserve stock, three weeks of conditioning, and stable thermal control."
"The thermal control modules from the Consortium warehouse," Santos said. "I have the replacement components. My team can install the new system in Bay 4 within five days."
"Five days for installation. Three weeks for soil reconstitution. Two weeks for germination and initial growth. Bay 4 returns to minimal production in approximately forty days. Full production in sixty."
Sixty days for one bay. Three damaged bays. The timelines overlapped but not completelyârepair teams could work on one bay while the soil conditioned in another.
"Total timeline to restore full agricultural capacity?" Santos asked.
Osei did the math the way agronomists did math: with variables that included weather (artificial, in this case), soil chemistry, plant biology, and the fact that twelve growing bays were supposed to feed two million people and three of them were broken.
"Ninety days. Best case. If the thermal control modules work as specified, if the soil cultures take, if the replacement seed stock germinates at expected rates." She looked at the dead bay. "If any of those conditions fail, longer."
"Ninety days."
"During which the food deficit continues. The dry stores will cover sixty days at current consumption rates. After sixty days, we begin rationing."
Santos wrote the number on his tablet. Sixty days to rationing. Ninety days to full agricultural recovery. A thirty-day gap where the ship's food supply would be insufficient for its population.
"I'll prioritize Bay 4," he said. "The thermal team starts today. Osei, begin soil reconstitution prep. We'll work in parallel."
"We will need additional water allocation for the reconstitution process. The bacterial cultures require a specific moisture gradient in the soil. Current water allocation to the agricultural ring was reduced by fifteen percent after the cascade to support medical and residential needs."
"I'll talk to the water systems division."
"Talk to them today. Every day of delay on water allocation is a day added to the reconstitution timeline."
Santos left Bay 4 with a list of dependencies that branched in every direction. Thermal modules from the Consortium warehouse required power grid modifications that required Santos's engineers who were also working on the navigation rebuild. Water allocation required negotiation with the residential council who were already angry about reduced shower time. Soil reconstitution required bacterial cultures that were stored in a frozen reserve on Deck 12 that had experienced intermittent power during the cascade.
Everything connected to everything else, and every connection ran through his team, and his team was forty people trying to do the work of two hundred.
---
Zara found Thomas in the archive room at 2200.
He was sitting at the terminal with his glasses on the desk and his fingers on the keyboard, hunched forward like someone whose body had forgotten it had functions beyond reading. The screen showed census dataânames, numbers, locationsâcross-referenced against the ship's original passenger manifest.
"The 214," Zara said.
Thomas leaned back. Put his glasses on. The archive room was small and dim and smelled like the inside of an old library, despite containing no books. The smell was Thomas's doingâhe'd found a way to adjust the room's air recycler to produce a scent profile that he claimed helped him concentrate. Zara suspected it helped him remember a world where knowledge lived on paper.
"I've been building their profile," he said. "They're not random. They're disproportionately technical workers, disproportionately Earther-affiliated, and they migrated within forty-eight hours of the cascade. Before the political developments. Before the framework."
"Cross briefed me on the security assessment."
"This isn't a security assessment. This is demographics." He turned the screen toward her. "Zara, sixty percent of the 214 are people who maintain critical ship systems. Water, power, environmental. If they stay off-grid permanently, the ship loses a meaningful fraction of its maintenance capability."
"We can't force them back."
"No. But you can give them a reason to come back." He pulled up a second dataset. "I found something else. Twelve of the 214 have active maintenance certifications that are required for their ship functions. Without them performing their assigned roles, the maintenance schedules for the water recycling plant on Decks 42 through 45 are running at sixty percent staffing. The plant hasn't failed yet because the automated systems are covering the gap. But the automated systems need periodic manual calibration."
"How long before the gap matters?"
"The water plant's calibration schedule runs on a thirty-day cycle. The last manual calibration was seventeen days ago. In thirteen days, the automated systems will begin drifting outside tolerance. The water quality for Decks 30 through 50 will degrade. Not immediately dangerous, but noticeable. Taste changes. Mineral content shifts. The kind of decline that people notice and talk about."
Thirteen days. Another timeline. Another cliff.
"What do you recommend?"
Thomas took his glasses off again. Cleaned them on his shirt. Stalling, and not hiding it.
"Talk to them. Not through Cross. Not through the Council. You, personally. Go down to Deck 44, walk into their school, and ask them what they need." He put the glasses back on. "They left because they lost trust. You don't rebuild trust through governance structures. You rebuild it by showing up."
Zara leaned against the archive room's doorframe. The corridor outside was emptyâthe 2200 hour meant most of Deck 5 was moving toward sleep. The ship hummed around them. The sound was different here than on the bridge, deeper, more resonant, the sound of a machine built to carry people across light-years and now carrying them through damage it was never supposed to sustain.
"You're advising me on politics now."
"I'm advising you on people. There's a difference, and the difference is that politics can be negotiated from a distance. People can't." He closed the census data on his screen. "Zara. When's the last time you slept in our quarters?"
The question landed in the space between the professional and the personal. Thomas lived in that spaceâthe historian who slept beside the captain, the man who knew where the archive met the bedroom.
"Three nights ago."
"It's been five."
"I've been in the closet-office."
"I know where you've been." He stood up. The archive room was small enough that standing brought him close to her, close enough that she could see the lines around his eyes and the gray in his stubble that hadn't been there seven months ago. "The ship needs you awake and functional. I need you present. Those two things overlap more than you think."
She didn't answer immediately. The conduit behind the wall hummed its one note.
"I'll come tonight," she said.
"You'll come now. The census data will be there tomorrow. The pharmaceutical timeline will be the same. The agricultural ring will not repair itself faster because you stayed up reviewing the schedule."
She looked at the terminal. The census data. The 214 names. The thirteen-day timeline for water calibration. The list of problems that grew every time she looked at it.
"Now," Thomas said.
She let him close the terminal. Followed him out of the archive room. The corridor was quiet. Their footsteps echoed in a pattern that sounded, for a moment, like two people walking in the same direction on purpose.
