The bruising had darkened overnight into a broad band across his left side that ran from the hip bone to the lower shoulder. It was not dangerous. It was thorough.
He pressed two fingers against the worst section of it, felt the tissue react, and decided that zone work was not happening today.
That was the assessnt. No argunt with it.
The Adaptive Recovery had been running through the night and had done what it could. The deepest tissue bruising needed ti that no skill could replace. Two days, probably. Maybe three before he could take a full impact on that side without the pain affecting his movent decisions.
He did not plan to waste the two days.
Sael’s note arrived with the morning al delivery, tucked between the bread and a small folded docunt that was the standard voluntary protocol check-in reminder for the day after tomorrow.
The note was on the director’s personal paper. Short. Handwritten in the clean, economical script of soone who had written notes for twenty years and had long since stopped wasting words.
The Rift’s oscillation changed tempo last evening for approximately eight minutes. The monitoring equipnt logged it at 19:40. I assu you noticed. If there is anything you are ready to share, I would find it useful. If not, the protocol continues as scheduled. — V.
I assu you noticed.
Not a demand. Not alarm. A quiet acknowledgent that things were happening and he was in the position of knowing more about so of them than the director did, and the director was patient enough to wait for the share rather than press for it.
He folded the note and put it in his coat.
He would visit the Division this afternoon.
He spent the morning reading the triple core.
Not studying it in the abstract way he had studied the zone maps and the Archive records. Reading it with the Path Compatibility Analysis active, the way the system had been trained by twelve days of dual-channel absorption to process multi-expression material.
The core sat on the table. It was smaller than he had expected for what it contained—roughly the size of a large coin, dense and cold, with a surface that seed to exist in two states at once: visible and slightly not-visible, the Shadow component’s suppression still active even in extracted material. The Storm component made it emit a faint static that he could feel in the fingertips if he held it too long. The Beast component was the reason it stayed whole instead of fragnting under the tension of the other two.
The analysis returned a result he had not expected.
Path Compatibility Analysis — triple core assessnt:
Storm-type content: 34% of total material
Shadow-type content: 31% of total material
Beast-type content: 35% of total material
Integration stability: high — expressions are mutually reinforcing at extraction
Current usability: partial — direct devour of remaining material will feed all three active channels
Fusion potential: high — Storm-Shadow interface layer is compatible with Hunter’s Instinct substrate
Long-term note: full utilisation requires Dragon-line pool at 80% capacity
Fusion potential.
The Storm-Shadow interface layer in the core was compatible with Hunter’s Instinct’s substrate. He had not known that was possible. The Hunter’s Instinct fusion had combined Predator Senses and Threat Reading into a unified environntal-and-opponent read. If the Storm-Shadow interface layer could be added to that substrate, the resulting skill would extend the environntal read into path-space—not just physical space.
He could not do that now. Dragon-line pool needed to be at eighty percent, and it was at seventy-one. But the core would keep. It was stable in extraction. He put it back in the protective case and set it beside the extended file on the shelf.
In nine days, roughly. Maybe less if the Dragon-line pool kept growing at its current rate.
He took the smaller portion of the Mantle Cat material—the fragnts that the system had already processed into absorbed energy residue during the three-channel devour, leaving behind a secondary set of path-crystallised traces that could be sold as raw material even after the main core had been retained—to the private buyer side of the exchange.
The buyer was the sa specialist he had used before. Beast Path, mixed-expression licence.
The man picked up the traces and looked at them for a long ti without speaking.
"Triple expression," he said, finally. He was not asking. He was confirming sothing he would not have predicted this morning.
"Yes."
The buyer set the traces on the asuring pad. The device ran its assessnt twice before producing a number. He looked at the number and then at Kai with the specific expression of soone recalibrating an assumption.
"Zone nine?"
"Yes."
A pause. The buyer moved to a ledger behind his counter and checked sothing. Ca back. "This is the first triple-expression Elite material to co through this exchange in fourteen months. The last one ca from a C-Rank team of four in zone fourteen." He set the traces down and nad a price.
It was higher than anything Kai had received from the exchange before.
He accepted it and signed the transfer form.
The buyer was already taking the traces to the back room. Over his shoulder: "If you have more, I’ll pay the sa rate. No grade confirmation hold on triple-expression—it’s distinctive enough that I don’t need the Division stamp."
Kai left the exchange.
The director was at his desk.
Kai sat in the chair without being asked and told him in four sentences: the Mantle Cat, zone nine, triple expression at B-Rank adjacent, the three-channel devour. He included the system’s confirmation of multi-path assimilation candidate but did not explain what the term ant. The director would understand it.
The director listened without expression until Kai stopped.
Then he was silent for a mont.
"The Rift’s tempo change lasted eight minutes," he said. "The oscillation increased in amplitude during that period before settling. The road network oriented toward zone nine at 19:42 and returned to baseline at 19:51." He looked at Kai. "The monitoring equipnt recorded the event as anomalous but within the voluntary protocol’s expected variance range."
"Voss will see it," Kai said.
"Voss has already seen it. He sent an inquiry this morning." The director picked up a docunt from his right stack and set it on the desk. An incoming ssage, the Council seal on the outside. "I have not responded yet. I wanted to speak with you first."
Kai looked at the docunt.
"Tell him it was consistent with the voluntary protocol’s monitoring period," he said. "Which it is."
The director looked at him for a mont. Not uncertain. Checking whether Kai had considered the full implication. Then he nodded once.
"The assimilation candidate confirmation," the director said. "When you are ready to discuss it in full, I would like that conversation."
"Not today," Kai said.
"No," the director agreed. "Not today."
Soren was at the mission board when Kai walked past on his way back.
He looked at Kai without turning from the board. Then he turned.
"Zone nine monitoring logged a B-Rank adjacent elimination at 19:38 yesterday," he said. His voice was the sa register he used for all information delivery: factual, no comntary. "The kill was attributed to a D-Rank hunter on a reconnaissance permit. No combat contract on file for zone nine." He paused. "The system flagged it as a logging error because D-Rank hunters cannot legally engage B-Rank adjacent creatures solo."
"I know," Kai said.
"The error will sit in the administrative queue until soone reviews it," Soren continued. "Probably three to five days. When it gets reviewed, soone will want to understand how the kill happened." He looked at Kai. "The monitoring log has your permit number."
Kai said nothing.
Soren looked at the board for a mont. Then: "I pulled the zone nine monitoring report at seven this morning. Before the administrative queue flagged it." He turned back to the board. "You’re welco."
Kai looked at the back of his head.
Soren was not asking for anything. He had done sothing useful and was not performing having done it. That was his register.
"Thank you," Kai said.
Soren nodded at the board. The conversation was over.
He was walking back through the main street when the Dragon-line pool crossed another threshold.
No dramatic event. He had taken no material today, done no zone work. The pool was still processing the absorption from yesterday—the three-channel devour had been so large that the secondary integration was still running, the Dragon-line substrate filing the Storm and Shadow components into their appropriate reservoirs with the careful organisation of a system that had never held this kind of material before and was taking its ti.
The passive Dragon Predator Mode activation that followed lasted three seconds.
He had stopped to read a route sign at the intersection of two streets. During those three seconds, two hunters who were passing in the opposite direction both turned their heads. Not sharply. Not looking for the source. The specific half-turn of people who felt sothing in their path-awareness and were checking whether it required attention.
One of them was C-Rank Storm. The other was Silver B-Rank Stone.
Both looked at Kai.
Neither of them knew what they had felt. It was not threatening. It was not a sovereign pressure event. It was sothing else entirely—the Dragon-line substrate’s ambient field, which at seventy-three percent pool capacity had reached a strength that path-sensitive hunters could detect without having the frawork to classify it.
The system noted it.
Dragon-line pool: 73%
Passive Dragon Mode ambient field: detectable to B-Rank and above path-sensitive hunters at 15–20 tre range
Note: ambient field is not classified in Guild’s monitoring frawork
Note: distinct from sovereign pressure events — different signature class
Both hunters had already looked away and continued walking.
Neither would file a report about a feeling they had no category for.
That was good. That was also temporary. At higher pool capacities, the ambient field would beco stronger. At so threshold it would beco classifiable, which ant it would beco logged.
The ssage from Dorath ca in the evening.
Not spoken—written, on the small formal card that hunters used for professional communications they wanted on record. The mission board had a drop service for this.
He read it at the front desk of the lodging house.
The lineage house team from zone 11 has filed a formal query with Guild administration asking for identification of the D-Rank hunter who eliminated the zone 9 B-Rank adjacent creature yesterday.
The query was logged this afternoon. Guild administration’s initial response was that no D-Rank hunter holds a valid permit for B-Rank adjacent solo elimination.
The lineage team’s second query, filed one hour later: if no D-Rank hunter holds such a permit, how was the kill produced and who is responsible for it?
Guild administration has no answer on file. The query is escalating to the permit review board.
Thought you should know. — D.
He folded the card.
He had known this was coming. The zone monitoring had his permit number. The kill was logged. The lineage house team had been in the adjacent zone during the ti window and had felt the Rift’s tempo change and drawn the correct conclusion about its source.
The Guild’s records said it was impossible.
Which was true. Under the Guild’s current classification frawork, a D-Rank hunter should not be able to produce a B-Rank adjacent elimination solo. The frawork had been built on the assumption that guild rank tracked combat capacity closely enough to make the two synonymous.
His file said D-Rank.
The zone said otherwise.
The permit review board would want to reconcile the two. The reconciliation would require either revising his rank upward—which he had not applied for and the appraisal board had not recomnded—or classifying the kill as an anomaly attributable to circumstances rather than to him.
Both answers were wrong.
The correct answer was that his guild rank and his actual capacity had stopped describing the sa person soti in the last month, and the gap between them was now large enough to produce docunted impossibilities.
He put the card in his coat alongside the director’s note and the voluntary protocol reminder and the extended file and everything else the city had been handing him.
Three days until the permit review board received the query.
He had three days to decide whether to let the process run or get ahead of it.
User Comments
0 comments from readers