Chapter 255: Chapter 255 – The Fourth Gap
Working with the source was different from working alone in a specific way he hadn’t anticipated.
Not easier. The pool cost per segment held steady—the degraded contacts in the water-eroded substrate were genuinely harder to work with than intact ancient stages, and no amount of guidance changed the physical cost of building through worn material. But faster. The source knew every degraded contact surface in the substrate the way someone knew their own house in the dark: by placement and feel, without needing to stop and check. He set the anchor. The source showed him the path. He built.
There was a specific quality to work done with someone who knew the terrain. Less decision time. More movement. The gap between starting a segment and setting it was shorter because none of that time went to navigation.
Four segments on the first day. Better than any first day in the western builds.
Days two through four.
The ancient network’s assistance activated on the second day as it had in every dense-network build, the original stages recognising the compatible grammar and beginning to reinforce the new construction. In the water-eroded substrate the assistance was less powerful than in the mountain build—the existing ancient stages were worn at their edges, and worn stages had less structural capacity to contribute. But it was present, and combined with the source’s active navigation it was enough.
What the source added in the degraded substrate was not available from the ancient network’s assistance alone: the knowledge of which worn contacts were stable enough to build through and which needed to be routed around entirely. In the western build without source collaboration he would have had to test each contact. With the source guiding, he routed around unstable contacts immediately, without the testing, without the cost of approaching a contact that wouldn’t hold.
The pool recovered faster between sessions than in any previous build. Sessions ended faster. The efficient recovery compounded—he was starting each new session at higher pool levels than the previous build’s equivalent day, which meant he could run longer before each surface break.
On day four he built six segments.
Day five. The eighteenth segment set.
The water-carved gap was longer than the previous corridors—the geological process that had worn the substrate had worked across a wider area than geological pressure or deliberate clearing had. Eighteen segments for full coverage, against twelve in the dense highland corridor and fourteen in the mountain. The source’s workaround routing through this region had been the most complex of the four western paths, routing through the longest indirect channels to avoid the degraded substrate.
He felt the eighteenth segment integrate and the routing change simultaneously—the source’s workaround pressure through this region beginning to redirect to the direct path.
He surfaced.
The Vael’s Crossing entity’s conducted pattern was different in the sovereign seed.
Not as immediately as Ren-Sarath had been different—the Vael’s Crossing entity had been in a recovery mode since the chain’s completion eighteen months ago, its deep pressure slowly declining from six centuries of unmanaged accumulation. Its load was already trending downward. This change was a step in that trend: the source’s workaround routing through Vael’s Crossing’s substrate, which had been adding to the entity’s load on top of the Rift’s own pressure, had cleared.
The entity was managing its Rift and nothing else.
It would recover faster now.
Neral was closing the documentation.
He had been working through the build continuously. The degraded-contact variant was the most technically complex to document—the source’s active guidance required an entirely new section the documentation hadn’t had before, describing how the active coordination worked and what it replaced in the carrier’s solo approach. He had written it while watching, asking Kai specific questions between sessions and recording the answers.
Now he was writing the section header on the final page.
"Four builds," he said. "Four substrate variants. Open substrate, dense network, compressed metamorphic, degraded contacts. The western sequence is documented." He looked at the volume of notes—four separate build records plus the grammar documentation plus the pool management tables. "Whatever the eastern builds require, the foundation is here. Future carriers have the complete western record."
He set his pen down.
"The carrier is ready for the east," he said.
He said it the way he documented things: as a factual assessment. Not encouragement. An evaluation. Kai heard it and noted it and found he agreed.
He stood in the water-carved basin.
All four western gaps running. The source’s workaround routing through the western hemisphere clearing as the direct paths opened. The entities lighter than they had been. The system running closer to the designer’s intended throughput than it had at any point in its history.
He had been working since arriving in this world. He had built toward this for over a year without always knowing what he was building toward. He knew now.
He knew what the east required. He knew what he could do. The gap between those two things was not zero. It had never been zero. It had always closed.
He read the substrate map through the Source Point integration.
The eastern substrate was clearer now than it had been before the fourth western gap’s completion. Not in location—the four eastern gaps’ positions hadn’t changed. In character. The source’s direct routing through the western hemisphere had reduced the interference in the substrate map’s read. He could distinguish features in the eastern substrate that had been obscured by the workaround routing’s pressure patterns.
Three of the four eastern gaps he could now read with reasonable clarity. Dense ancient network, different substrate composition from the western highlands, the source moving more actively in those regions.
The fourth eastern gap was different.
Not a cleared corridor or a mountain gorge or a water-carved basin. A fault line. A geological fault running approximately two hundred kilometres through the eastern substrate, the ancient network on both sides dense and intact, but the fault itself absent of staging—the designer had cleared it deliberately, leaving the fault zone free of ancient network construction.
The fault was active. He could read its movement through Dragon Mode even at this distance—the deep substrate on either side of the fault line shifting relative to each other at the slow continuous rate of geological time.
Building a lateral stage through an active geological fault meant building in substrate that moved.
He had never done that.
The source communicated with the quality of a navigator pointing at something on a map. It had been routing pressure around this fault for geological time. It knew how the fault moved. It knew what was stable in the fault zone and what wasn’t. It had been waiting to show the carrier the route through.
A geological fault. Moving substrate. Of course the eastern sequence covered the things the western sequence hadn’t.
He turned to the group.
"There’s a fault line in the eastern sequence. Active. We’ll need to build through moving substrate." He looked at Neral. "Fifth build type."
Neral opened a new notebook.
