Chapter 243: Chapter 243 – The Second Source
The pool recovered in stages.
Day one of the eastward travel: fifty-five percent rising to sixty-five as Adaptive Recovery worked steadily without the lateral stage construction competing for pool capacity. Day two: seventy-eight. Day three: functional—not full, full took longer, but functional, which meant Dragon Mode at depth without rationing and the sovereign seed running the five-node integration without the friction of reduced capacity.
He noticed the difference the moment it crossed the functional threshold. Eight days of sustained high-output work had recalibrated his sense of what the sovereign seed felt like under load. Full capacity felt different after that—lighter, the way taking off a heavy coat after wearing it long enough to forget it was there felt lighter.
Eight days at that output level and he’d forgotten what operating at full capacity felt like. He hadn’t liked forgetting that.
He filed the observation and walked east.
Soren was designing equipment.
He had been designing since the first morning of travel, his notebook open continuously, the specifications developing across three pages by the time they stopped on day two. He showed Kai on the afternoon of the second day without introduction—no preamble, just the notebook extended.
The design was for a passive substrate pressure reader. Not a path-layer instrument—every Guild monitoring tool was built for path-layer work. This was designed for the substrate’s deep layer: the pressure field the Source Point integration could read directly through the carrier function. The instrument would not require a carrier to operate. It would detect the deep pressure’s frequency signature through a specifically tuned resonance array that Soren had spec’d to the frequency parameters the Source Point’s transmission had established.
It would let any trained operator monitor substrate pressure directly. No carrier function required.
Kai looked at the design. At the three pages of specifications. At the part where Soren had already worked out the manufacturing requirements and estimated a build timeline.
He took eight days of data in circumstances that would have sent most hunters home after day one, and he turned it into a tool that makes the carrier function’s work reproducible. That’s just who Soren is.
"It’ll take time to build," Kai said.
"Yes," Soren said. He turned to the next page and kept drawing.
On the evening of the third day, Neral sat across from Kai at camp and opened the Kael’s Seat archive document for the first time since the eastern travel had begun.
Not to a section Kai had seen. To the end.
"I held this back," Neral said. Not apologetically—factually. "Not because I was concealing it. Because I didn’t understand it until the bypass channels became readable through the first Source Point’s integration." He set the document on the ground between them. "The archive text distinguishes between what it calls the western record and the eastern record. I had assumed those were two names for the same Source Point. They’re not."
He pointed at the relevant section.
"The western record—which is the Source Point we visited—contains the reason the network exists. The why. The eastern record contains something different. The document describes it as—" he read the translation he had made in the margin— "the account of what was there before the network."
He looked at Kai.
"The designer built both. They knew a carrier would need both. The western record first—to understand the function. The eastern record second—to understand what the function is for."
Kai looked at the document. The designer had prepared this for a specific sequence. Not just ’find the Source Point.’ Find the western one first. Then go east for the rest of it.
The designer left nothing to chance. They knew exactly what a carrier would be doing and in what order. Either they had done this before or they understood the carrier function well enough to predict it precisely. He wasn’t sure which option was more unsettling.
Day four. The bypass channels did something new.
He had been reading the second Source Point’s westward transmission since Ren-Sarath—the signal growing stronger as they moved east, the quality of it sharpening from a distant grammar into something more legible. He had been receiving it. What he had not been doing was sending.
On the morning of the fourth day, the bypass channels began carrying a signal eastward. Not from him—from the Architect, through the coordination layer, through the bypass channels as a relay toward the second Source Point.
He asked through the coordination layer: what are you sending?
The Architect communicated: that the carrier was coming.
"Does it already know?"
Yes. The second Source Point had been tracking the carrier’s location through the bypass channels since the first Source Point integration. It knew Kai had found the western record. It had been updating its read of his position continuously.
Of course it has. It built a transmitter inside the network’s own relay system. It has access to everything the relay carries. In retrospect that’s obvious.
He was starting to notice that a lot of things became obvious in retrospect. That was probably fine. The alternative was knowing everything in advance, and he had yet to encounter anything that suggested that was available to him.
He walked. The bypass channels carried the Architect’s message east. The second Source Point’s transmission came west. The signal, as they moved toward each other, was resolving from grammar into quality.
It felt like an invitation. Not broadcast widely the way the first Source Point had broadcast—this was addressed. Specifically. To a carrier who had received the western record and was now capable of receiving what came next.
That’s either an honour or a warning. Given how this work has gone so far: probably both.
That evening he sat at camp and felt what had changed in the function over the past year.
He had been going east. Then west to address the breach. Then east again. At some point the direction had stopped being travel and had become the work itself. Not movement toward a destination. The carrier function in motion—which was, apparently, what the carrier function looked like when it was running correctly.
He thought about the first day in Kael’s Seat with a D-Rank badge. He had not known what the function was or that he had one. He had known there was something in the zones that the Guild’s classification system didn’t have a category for. Everything since had been the process of finding out what that thing was.
He still doesn’t know all of it. The not-knowing feels different now, though. At the start it was the not-knowing of someone who doesn’t have enough information. Now it’s the not-knowing of someone mid-way through a job that isn’t finished yet. Those are different shapes.
He looked at the group. Neral writing. Soren speccing his instrument. The older man making tea with the specific efficiency of someone who had been making tea in difficult places for a long time. Mira reading the vault pair’s five-node output. Liora watching the eastern horizon.
He had crossed a world with these people. He would keep crossing it.
He closed his eyes and let the sovereign seed run.
