Chapter 273: Chapter 273 – Five Points
The first descent on the second entity cost eighty-one percent.
He surfaced with nineteen remaining and sat at the gorge rim and did the arithmetic without Soren needing to ask. One segment. Five anchor points held simultaneously across a vertical depth range four times what the three-point horizontal grammar had required. The source had shown him the band positions clearly enough the night before—the descent itself wasn’t a failure. The segment was in place. But the carrier function holding five distinct depth positions against the layered substrate’s pressure differential between bands was a different order of draw from anything the first chain had required.
Eighty-one percent for segment one. The three-point horizontal opened at seventy-one. Ten points higher for two additional anchor nodes and a vertical geometry. Soren will want the exact figure. File it: five-point vertical, first segment, eighty-one percent. New high-water mark.
Soren had the vertical monitor running throughout the descent. He showed Kai the readings before speaking.
"The entity conducted through the first segment within four minutes of it setting. The three-point chain took nine minutes at the same stage." He looked at the data. "The vertical architecture is better at accepting chain infrastructure than the horizontal architecture was. Forty years of stable stratified management work—the substrate below is extremely receptive. The geometry cost is high on your end. The entity’s end is smoother."
He ran the cost projection without being asked.
"Estimated total segments: fifteen. First four at above eighty percent draw. Then a steeper drop than the first chain—the entity’s substrate acceptance rate is faster. Segments five through nine in the forty-to-fifty range. Ten through fifteen at standard or below." He looked up. "Fifteen days minimum. Possibly twelve if the acceptance rate accelerates faster than projected."
Fifteen segments. Three more than the first chain, offset by faster substrate acceptance after the initial drop. Longer build, cheaper finish. The entity’s forty years of stable management work makes the second half easier than the first chain’s second half was. Total cost roughly comparable. Time longer. File it.
He rested through midday. The pool was at sixty-three percent by the time he ate.
He was considering a second descent in the afternoon when the creature came out of the gorge.
It came up the rock face from below—not from the treeline the way the previous creatures had approached, but vertically, from the gorge itself. He felt it in the passive read before it reached the rim. Four nodes. He had been reading two-node and three-node eastern fauna for two weeks. Four was new.
He activated Dragon Predator Mode at formation-layer depth and read before it cleared the rim.
Spine, lower thorax, upper thorax, skull. Four-node cascade—each node fed the next in sequence, the cycle longer and more powerful than the three-node highland creature by a significant margin. The skull discharge at the top of a four-node cascade would be stronger than anything he had read so far. The creature was smaller than the three-node beast—built for the gorge environment, compact, four limbs adapted for vertical movement on rock. But the energy output per size was higher.
Four-node cascade. Spine feeds thorax-low, feeds thorax-high, feeds skull. Discharge at the end of four accumulations. Don’t let it complete the cascade. Interrupt at thorax-low, before the energy has built further than the first node. Sixty-three percent pool. Manageable if the fight stays short.
It cleared the rim and oriented immediately. Faster read than the previous creatures—the gorge fauna had developed better substrate sensitivity, living in the layered rock where the formation-layer energy was closer to the surface. It knew his position before it had line of sight.
He activated Impact Frame as it crossed the distance between them. The gorge creature was lighter than the three-node beast but the four-node cascade gave the strike a different character—the energy discharged partially on impact rather than after. The frame caught it but the discharge component hit through the frame at the edges.
Partial discharge on contact. New behaviour. The four-node creature doesn’t wait for the cascade to complete before striking—it discharges mid-cycle. That changes the read. Interrupt needs to be earlier than thorax-low. Interrupt at spine, before the cycle initiates.
Piercing Authority at the spinal node on the second approach, before the creature had completed its first-node charge. The cycle didn’t initiate. The creature’s movement stuttered—without the spinal charge, the cascade had no starting point.
He followed immediately.
Rending Strike at the lower thorax node while the cascade was interrupted. Disrupting the second node while the first was suppressed meant the energy had nowhere to route.
The creature shook. Reoriented. Tried to initiate the cascade from the lower thorax directly, skipping the damaged spinal node.
Adaptive. It’s trying to start the cascade from the second node. Smart. The cascade is weaker without the spine feeding it first, but it’s still functional. Three-node cascade from the thorax-low. Read the new cycle rhythm.
Predatory Burst Step disengaging, creating distance to read the adapted cycle.
The lower thorax feeding upper thorax, feeding skull. The energy build was slower and the eventual discharge would be smaller without the spinal node’s contribution. But it was building. He had four seconds before it reached the upper thorax.
Piercing Authority at the lower thorax before the energy transferred. Second spinal-equivalent interruption on the backup cycle. The creature’s energy collapsed.
Rending Strike at the upper thorax node. The creature went down.
He stood at the gorge rim and read the pool.
Forty-one percent remaining. Twenty-two percent drawn in the fight. Four-node cascade creature, gorge-adapted, mid-cycle discharge capability. Required: spine interrupt before cascade initiates, or thorax interrupt on the backup cycle if adaptive response triggers. That’s the pattern. It will apply to whatever comes next that uses the same architecture.
Soren was reading his instruments.
"The partial discharge on impact registered on the vertical monitor," he said. He showed Kai the readings. "The energy that hit through your frame—the discharge component—it came from the formation layer. The gorge fauna are more directly connected to the formation-layer energy than the highland creatures. Living in the exposed stratified rock rather than above it." He made a notation. "Four nodes, mid-cycle discharge, formation-layer direct connection. This is a more advanced energy architecture than the surface creatures. I need a separate classification tier."
He was already writing the framework revision.
Mira had the vault pair extended.
"The entity tracked the fight through the formation layer," she said. "The gorge creature—the entity read its energy signature throughout. When it went down, the entity’s signal changed. Not alarm. Something more like acknowledgment." She looked at the shells. "I don’t think this was the first time the entity has watched something like this happen above it."
Forty years in the gorge. The four-node creatures have been living in this formation layer the whole time. The entity has been managing its Rift below them for four decades—it knows their signatures, their cycles, probably their hunting patterns. It wasn’t watching a new event. It was watching the carrier handle something it had been observing for a long time.
The pool had recovered fully by mid-afternoon. He descended again.
Second segment. The anchor geometry was fractionally easier to hold than the first—the substrate had begun accepting the five-point vertical pattern the same way the first chain’s substrate had begun accepting the three-point horizontal. Faster than expected.
Seventy-four percent draw.
Three percent cheaper than the first segment. Steeper initial drop than the first chain’s two-percent between segments one and two. Soren’s projection of faster acceptance was correct.
He surfaced at the end of the afternoon with two segments complete and twenty-six percent remaining.
Two segments in two sessions. One day. First chain took one segment per day for the first four. The Emperor Body’s higher ceiling makes a second session viable on the same day without full recovery between. New variable. The second chain builds faster than the first not just because the entity’s substrate is receptive but because the carrier function has more total capacity to draw from.
He didn’t tell Soren the second-session draw figure until after he had eaten.
"Seventy-four percent for the second," Soren said, already revising. "Down from eighty-one. Seven percent between segments one and two—the first chain showed no improvement in the same window. And you ran two sessions in one day." He looked at his projection table. "I need to revise the timeline. Fifteen days assumed one segment per day. At two sessions where pool permits, and with this acceptance rate, I project eleven days to completion."
He paused.
"Possibly ten."
Ten days. First chain took nine. Second chain one day longer despite having fifteen segments instead of twelve, because the Emperor Body pool makes double sessions viable. The adapted grammar cost is higher but the ceiling is higher too. The numbers balance. That’s actually a cleaner build rate than the first chain when measured by total segments-per-day.
Night at the gorge rim. The source steady below. Nine signals in the vault pair, the second entity conducting through two segments with the clean precision of something that had been waiting forty years for correctly-fitted infrastructure.
He looked at the gorge walls. The stratified bands were visible as lighter and darker lines in the rock face—forty-year-old management work running through the exact geological layers he had anchored the chain to. The entity had built its architecture into what was available. He had built the chain into what the entity had built.
Five anchor points. Vertical. Fifteen segments total. Second session already viable. The second chain is a different problem from the first in every technical dimension—different geometry, different depth range, different acceptance dynamic. But the principle is the same: read what’s actually there. Build to it.
He set the second descent data aside and let the pool recover through the night.
Tomorrow: two more sessions.
