Chapter 115: Recalculation

Viktor spent four hours recalculating.

He worked from the monitoring station beside Thessaly's platform, Maya's secondary harmonic feeding him real-time data while his stylus covered page after page of structural analysis. Marcus watched through the relay as Viktor methodically dismantled every projection he'd built since the team returned from the deep layers—every timeline, every degradation estimate, every assessment of what was possible and when.

The process was surgical. Viktor started with the boundary pressure model and replaced the Architect's linear projection with the exponential curve from the foundation data stream. The change propagated through every dependent calculation like a crack spreading through glass. Each corrected number changed three others. Each of those changed three more.

At 1630, he stopped writing. Set his stylus down. Looked at the page. Looked at Thessaly. Picked up the stylus, checked three numbers, confirmed what he already knew.

"The stabilization timeline," he said. "My initial estimate was four to seven days before Thessaly's architecture reaches critical failure. That estimate used the Architect's linear model for boundary pressure as a baseline for the degradation rate." He turned the tablet toward the relay camera. The numbers on the screen were clean, precise, and wrong. "The linear model understates the pressure on Thessaly's architecture. The exponential curve means the boundary is pushing harder against the buffer zone than the linear model predicted. The buffer zone transmits that pressure to its living core. Thessaly is degrading faster than my estimate because the pressure on her is greater than I calculated."

"How much faster?" Marcus asked.

"Critical failure in approximately forty-eight hours from now. Not four to seven days."

Forty-eight hours. The room took the number and held it like something sharp.

"My stabilization method—the secondary harmonic reinforcement through Maya's continuous contact—was calibrated for the linear degradation rate. At that rate, the reinforcement could maintain Thessaly's architecture indefinitely. At the corrected rate, the reinforcement slows the degradation but cannot match it. The gap between reinforcement and degradation is approximately seven percent." Viktor's jaw clicked. The grinding sound of teeth against teeth. "Seven percent does not sound significant. But compounded over the corrected timeline, Thessaly's architecture reaches a point of no return in—" He checked. "Thirty hours."

"Thirty hours," Lucas repeated.

"Thirty hours until the degradation exceeds any stabilization method available to us. After that point, architectural failure becomes irreversible regardless of intervention."

Marcus did the math without wanting to. Kael's estimate for full network activation: eighteen to twenty-four hours. Viktor's new deadline for Thessaly: thirty hours. The gap between network activation and point of no return was six to twelve hours. Narrow. Not impossible, but a margin measured in hours when every variable was an estimate built on other estimates.

"Your stabilization plan," Marcus said. "It was the foundation of everything. Keep Thessaly alive long enough to understand the network, make a decision about the acceleration, prepare for the anchor path. That plan assumed days."

"That plan assumed days." Viktor set the stylus down. Left it down. "We have spent the last twenty-four hours operating as though we had a week. We did not have a week. We had two days, and one of them is gone."

One day wasted. One day of holding the gradient, mapping the network, debating the Witness's deception, circling the decision Marcus wouldn't make—all of it done on a timeline that didn't exist. They'd been running from a deadline they thought was distant, and the real deadline had been sitting behind them the entire time.

"Viktor," Marcus said. "Is there a faster stabilization method?"

"I have explored every option available with our current architecture. The secondary harmonic is the most effective." Viktor picked at the cuticle on his thumb. Drew blood. Didn't stop. "There may be options I have not considered. My analysis has been based on the Architect's structural models. Those models are now confirmed to use compromised data. It is possible that a different approach—one not derived from the Architect's framework—could be more effective." He looked at Thessaly. "It is also possible that no stabilization method is sufficient. The degradation may be a feature of the Sixth's design. The system may require the living core to reach critical failure for the activation to complete."

"Like a chrysalis," Kael said from the perimeter station. "The caterpillar dissolves before the butterfly forms. Thessaly's architecture is dissolving to make room for whatever the activated network creates."

"That is a metaphor," Viktor said. "Not analysis."

"It is both."

---

Marcus called a strategy session at 1700.

The full team: Viktor and Maya at Thessaly's station, relayed through the secondary harmonic. Kael at the perimeter, between-dimension sensing still running. Dara at the fracture wall monitoring feed, her tablet tracking the cluster's continued ninety-second probing cycles. Lucas in person, standing against the wall with his arms crossed and his expression set to the particular flatness that meant he'd been waiting for this meeting to happen.

"Status," Marcus said.

Dara first. "The cluster has completed forty-seven probe cycles against the fracture wall's new configuration. The organic growth is responding autonomously to each probe. Fracture wall integrity holds at seventy-seven percent. The cluster has not escalated beyond probing. My estimate for first serious assault: six to eight hours."

Kael. "Eighteen nodes active in the Sixth's network. Activation rate increasing. Full activation in fourteen to twenty hours." He paused. "The Harvester has consumed approximately four percent of the buffer zone's outer architecture since yesterday. The density gradient is holding but the consumption is constant. At current rate, the buffer zone reaches minimum viable architecture for acceleration in approximately five days."

Viktor through the relay. "Thessaly: thirty hours to point of no return. The activation download is sixty percent complete. Her architecture is attempting to run the startup sequence in parallel with the download, which is accelerating the degradation."

Maya through the relay. "The Witness is agitated. The five walkers are attempting to communicate continuously. They want to tell us about the Sixth's hidden construction. The thing Thessaly mentioned before she went under. But the channel bandwidth—I can't receive their full transmission while maintaining Thessaly's stabilization. I'm getting fragments."

"What kind of fragments?" Marcus asked.

"Warnings. The Sixth built something that the Witness calls—" Maya's harmonic flickered. "The translation is imprecise. They call it 'the override.' Or 'the precedence.' Something that supersedes other architectures. They're scared of it because they don't know what it does, only that the Sixth embedded it in the acceleration network and they cannot access or modify it."

An override built into the acceleration. Something the Sixth embedded that nobody—not the Architect, not the Witness, not even Thessaly—fully understood. Something that activated with the network.

"Fourteen to twenty hours before it goes live," Lucas said. "Whatever it is."

"Whatever it is," Marcus confirmed.

Lucas pushed off the wall. "Then let me lay out the operational picture as it stands." He moved to the display, positioned himself beside the network map. "We have four converging timelines. One: network activation in fourteen to twenty hours. Two: Thessaly's point of no return in thirty hours. Three: cluster assault on the fracture wall in six to eight hours. Four: Harvester consumption reduces the buffer zone below viability in five days." He looked at Marcus. "Timeline one and two overlap. The network activates around the same time Thessaly hits critical. If you are going to control the acceleration—the anchor path—you need to be committed and connected before the network goes fully active. Which means you need to decide within fourteen hours."

"And timeline three," Dara added, "means the cluster hits the fracture wall tonight. During the window when Marcus is supposed to be deciding about the anchor path. During the window when Maya is maintaining Thessaly's stabilization. During the window when I need every resource available on the wall and half our resources are committed to the buffer zone."

Everything at once. Every crisis on the same clock.

"There's also the override," Kael said. Quiet. Direct. "Whatever the Sixth built into the network activates with the network. In fourteen to twenty hours, something none of us understand goes live inside the acceleration infrastructure. If Marcus commits to the anchor path and the override does something unexpected—"

"He's locked in," Lucas finished. "Seven years locked into a system with an unknown variable embedded in its core."

Marcus looked at his hands. The gate-sense hummed through them. The interface connection pulsing, the buffer zone a constant pressure in his awareness, the Harvester's consumption a cold absence at the edges. Thessaly's architecture degrading through the link, each lost node a small death in his peripheral sense.

Fourteen hours to decide. Thirty hours until Thessaly passed the point where decisions mattered. Six hours until the cluster hit the wall. Five days until the Harvester ate too much. And somewhere in the Sixth's network, an override that nobody could explain waiting to activate.

He closed his hands. Opened them. Closed them again.

"We need more information," he said. "About the override. Maya—can you get more from the Witness if I take over Thessaly's stabilization through the interface?"

"You would have to drop the density gradient," Viktor said.

"For how long?"

"However long it takes Maya to receive the full Witness transmission. An hour. Perhaps two."

Two hours without the gradient. The Harvester consuming freely. The buffer zone shrinking, each consumed section making the acceleration less viable, reducing the margin between possible and catastrophic.

Marcus calculated. Five days to minimum viability. Two hours of free consumption reduced that by—he pressed the interface, felt the Harvester's rate, did the math through the gate-sense—approximately three hours of total viability. Five days minus three hours. Negligible in isolation. Not negligible if other things went wrong.

Everything was going to go wrong. The last twenty-four hours had proven that every estimate they made was optimistic and every plan they built collapsed under the weight of information they didn't have until it was too late.

"Do it," Marcus said. "Maya drops Thessaly's stabilization. I take over through the interface. Maya receives the Witness transmission. Then we switch back."

"And the gradient?" Viktor asked.

Marcus looked at the buffer zone through the gate-sense. At the cold absence eating its edges. At the architecture the Sixth had built to save everyone, slowly being consumed by the thing it was supposed to be saved from.

"The gradient goes dark," he said. "Two hours. We accept the loss."

He reached for the interface. Shifted the Gate Authority from density manipulation to structural reinforcement. The gradient collapsed. The Harvester's consumption accelerated.

And somewhere in the buffer zone's outer edges, the sound of architecture being eaten grew louder by one degree that no instrument could measure but Marcus's gate-sense registered as clearly as a scream.