The terrain shifted back toward compressed highland rock on day nine.

The alluvial basin gave way to the same character of geology that had produced the first entity’s Rift—hard, dense, the substrate’s path-energy concentrated vertically rather than conducting laterally. The formation-layer passive read changed quality with the geology the way it had changed throughout the eastern survey: different rock, different read. The substrate here was older than the alluvial basin and deeper in its compression.

The northeast entity’s presence grew stronger with each day.

Not the gradual approach quality of the first two entities—those had been readable at close range, their signature strengthening as the group closed the distance. This one had been present since day eight and it grew slowly and consistently, not because it was broadcasting more strongly as they approached but because the substrate between them was conducting its presence outward. The difference was subtle and took two days to register as a distinct quality: the first two entities sat at their Rifts and were felt when you came near them. This one extended itself through the substrate in all directions, the way a sound carried through still air.

Not broadcasting. Conducting. The first entity used the chain to communicate. The second entity used the chain and the formation layer. This one is using the substrate itself as an active medium. Sixty-plus years in compressed rock and it has learned to move through the rock the way the river-bed creature moved through alluvial stone. Different mechanism. Same principle.

Day eleven. Three creatures.

They came from below simultaneously—substrate-pulse type, the same ventral architecture as the river-crossing creature, but smaller and faster in the compressed rock’s different conductivity. The formation-layer passive read had been tracking them for four minutes before they broke the surface. He’d had time to read all three discharge cycles, map their relative positions, and assign a sequence.

Three. First time. Three separate discharge cycles, three separate reset windows, three separate ventral lines to target. In open substrate he can track all three simultaneously through the passive read. That’s the advantage. In the old surface-reading days he’d have had to fight three at once. At formation-layer depth he can see all three before the fight starts and pick the order.

He activated Dragon Predator Mode at formation-layer depth and held all three signatures simultaneously. Left flank. Right flank. Centre-rear.

Left flank first—closest to discharge peak. He moved before it surfaced, positioning for the reset window while the other two were still mid-cycle.

Impact Frame on the left creature’s surfacing strike, timing the frame to the discharge rather than the physical contact. He felt the discharge conduct through the ground at his feet rather than through his body—the substrate around him absorbed the discharge rather than concentrating it at the contact point.

Piercing Authority at the ventral node during the left creature’s reset. Cycle interrupted. One down.

Right flank was at discharge peak now. He didn’t engage directly—he let it surface and discharge into the ground, stepped clear of the conduction radius, and read the reset while moving toward centre-rear.

Rending Strike at the centre-rear creature’s lateral node before it reached discharge. Cycle broken at the lateral transfer point before the energy reached dorsal. Centre-rear down in one strike.

Piercing Authority at the right creature’s ventral line during its reset. Third cycle interrupted. All three down in under four minutes from first surface contact.

Four minutes for three. Three separate fights in sequence rather than simultaneously. The formation-layer read made it sequential rather than concurrent. Total pool draw: less than the single gorge-creature fight that cost twenty-two percent. Read depth makes three easier than one if you have the intelligence before contact.

Soren had been running his instruments throughout.

"I tracked all three pulse signatures from before the surface break," he said. He was already writing. "You fought them in the order they reached discharge peak. Left, then centre-rear’s cycle before it could discharge, then right during reset." He looked at the data. "You read the combat order from substrate data four minutes before the fight started."

He made a notation.

"Formation-layer depth in conductive substrate gives pre-contact strategic read of multi-creature engagements. Previous record was single-creature pre-contact read. This is a different capability class." He looked at Kai. "I’m adding this to the fauna combat section. Specifically: formation-layer read at Emperor Body depth in conductive geology provides engagement sequencing intelligence for groups. Not just timing—sequencing."

That’s accurate. File it. At this depth in this substrate, a group fight is just several single fights with known order. The complexity isn’t in the fighting. It’s in having the read depth to see all of them before any of them arrive.

Day fourteen. They reached the Rift.

The northeast entity’s presence was immediate and total.

Not the first entity’s alert attention from depth. Not the second entity’s patient stratified weight. Something that was already at the surface and had been for a long time, so thoroughly integrated with the compressed rock above it that the distinction between entity and substrate was genuinely unclear in the formation-layer read. Sixty-plus years of active presence in this rock. It hadn’t been waiting below the Rift. It had been growing into the rock around the Rift until the rock and the entity were the same thing.

And it knew they were here.

It had known they were coming for at least six days. Probably more.

He held the offering posture. Formality first—the first and second entities had responded to the offering posture as the correct protocol for establishing contact intent. Whatever this entity knew about carrier infrastructure, it should respond to the same approach.

The response came immediately.

Not readiness. Not agreement. Not the patient certainty of the second entity’s forty years. Something that translated most precisely as: yes, I know, I have been ready, I built something for you, come and see what I built.

He held the carrier function at full depth and read below the Rift.

The formation-layer passive read at Emperor Body depth showed him the substrate structure below the Rift in more detail than any previous entity site. And what it showed was not only the entity’s Rift management architecture—the sophisticated sixty-year-old management framework he had expected from the substrate memory the second entity had communicated. Below the management architecture, at the depth where the carrier function built chain infrastructure, there was something else.

Rough. Imprecise at the edges. Built from below rather than from above, using entity-class path-energy rather than carrier-function sovereign output. Not the clean crystallised grammar of the builders’ ancient network or the carrier-function chains already completed.

But it was there. And it was in the right positions.

The entity built anchor points. Not carrier grammar—it doesn’t have sovereign output, it can’t produce the precise crystallised path-energy the carrier function uses. But it has been managing a Rift for sixty years and it understood the geometry. It looked at where chain infrastructure should sit relative to its own architecture and it built something in those positions. Rough. Entity-class. But oriented correctly.

Sixty years of trying to build the other half of something before it knew what the other half looked like. It built toward where it thought the connection should be. 𝙧𝙚𝙚𝔀𝒆𝓫𝓷𝙤𝓿𝒆𝙡.𝒄𝙤𝓶

Mira was reading.

"Twelve signals," she said. Quiet. "At vault pair direct range—not through the source substrate layer. It came through the formation layer directly." She held the shells. "Since day eight the signal has been strengthening, but I thought it was proximity. It wasn’t only proximity." She looked at the Rift. "It’s been increasing because it’s been pushing itself closer to the surface layer. Learning the vault pair’s read depth and meeting it."

She turned the shells slowly.

"The first entity learned to broadcast in nine days. The second in three days. This entity is already broadcasting before the chain exists. Through the rock, at vault pair range, from day eight." She held the shells. "It’s been doing a version of this for a long time. It’s been trying to connect to something for sixty years. This is the first time it found something that connected back."

He sat with the carrier function open above the Rift and let the passive read map what the entity had built below.

Six anchor point positions. Placed over six decades of management work, adjusted incrementally as the entity developed better understanding of where the chain architecture needed to sit. Not five, not three—six, which was neither the standard grammar’s five-point radial nor either of the previous non-standard chains’ geometries. The entity had arrived at six through its own analysis of what would hold the connection stable given its specific Rift geometry.

The positions were right. The construction was rough. The carrier function would need to build proper chain grammar into the entity’s anchor points rather than building anchor points from scratch—cleaning the entity-built structure and replacing it with the correct grammar while keeping the geometry the entity had solved for.

Third chain. Third variant. First entity: three-point asymmetric horizontal, built from scratch into workaround pressure substrate. Second entity: five-point vertical, built from scratch into stratified bands. Third entity: six-point hybrid, built into existing entity-constructed scaffold. Three completely different problems. The western sequence taught him the substrate variants. The eastern sequence is teaching him the entity variants.

Neral opened the documentation.

"Adapted Infrastructure—Case Three," he said. He didn’t look up from the page. "Hybrid chain build: carrier function grammar integrated into entity-built anchor scaffold. Sixty years of entity-constructed positioning. Six anchor points. Entity-active cooperation throughout." He wrote. "This is a new case because the entity is not a passive recipient of carrier function infrastructure. It is a collaborator who has already done significant preparatory work."

He looked at Kai.

"Document everything about how the entity-built scaffold interacts with the carrier grammar. Future carriers will encounter entities that have been waiting long enough to build their own approach. They need to know this is possible and what it looks like when it happens."

The entity communicated once more before he closed the carrier function for the night.

Not readiness or patience. The quality of something that had spent sixty years building toward a connection and was now watching the other side arrive.

Tomorrow.

He closed the carrier function and slept.