He went to the Rift Archive before the Division.
The Archive was on the ground floor of the Guild’s administrative building, two streets from the registration hall, marked by a plain door with a reader’s mark rather than the Guild seal. Not a restricted space—any registered hunter could enter. The collection inside was the Guild’s public record of Rift zone classifications, creature catalogues, path material grade histories, and mission outco data going back four generations.
He spent an hour there.
What he was looking for was not in the creature catalogues or the mission records. It was in the zone classification histories—specifically the reclassification events. Every few decades a zone would shift designation, usually upward, because the ambient Rift energy in it had strengthened or a new creature sub-type had established territory. The Archive recorded these reclassifications with brief explanatory notes.
Zone eleven had been reclassified twice in the last forty years.
Zone eight had been reclassified once, twelve years ago.
Zone fourteen had been reclassified six years ago—upward from C-Rank to B-Rank adjacent, which was a significant jump. The Archive note attributed it to a structural shift in the Rift’s boundary layer in that section of the valley.
He noted that and kept reading.
The natural Class 3 Rift at Kael’s Seat had not been reclassified in the Archive’s four-generation record. It had been designated Class 3 before the Archive existed, and the designation had not changed. But the note attached to its entry, added six years ago around the sa ti as zone fourteen’s reclassification, read:
Boundary layer activity: elevated. Monitoring status: active. Origin of activity: under investigation. See Division file 11-CC for full assessnt.
Six years ago.
He looked at the date again.
The zone fourteen reclassification and the Class 3 boundary activity had happened in the sa quarter. The Archive note said the origin was under investigation. He did not have access to Division file 11-CC.
He noted that too and closed the reading terminal.
The director’s office was a fifteen-minute walk east.
***
Sael showed him in without delay.
The director was at his desk with two docunts open in front of him and a third folded at his right hand. He looked up when Kai ca in, registered the ti—earlier than he had probably expected—and gestured at the chair across the desk without comnt.
Kai sat.
The director looked at him with the calm, reading attention he always used. Then he picked up the folded docunt—not a paper docunt, a bound report, the Division’s internal format—and set it on the desk between them.
"Your zone adaptation rate across four D-Rank entries," he said. "Averaged against the Division’s full monitoring database for all carriers recorded since the archive was established." He tapped the report once. "Yours is faster by a factor of nine."
Kai looked at the report without picking it up.
Factor of nine.
The fastest rate on record before his was thirty-two seconds. His was thirty-eight on the first entry. He had not asured the subsequent ones, but the trend was clear: with each entry the baseline settled faster, the zone pressure registered as less foreign, the body’s calibration process completed in less ti because there was less calibration required.
He was not adapting to the zones.
He had already adapted to sothing similar before. The zones were asking him to recognise what he already carried.
"Zone fourteen," he said.
The director’s expression shifted fractionally. Not surprise. The particular quality of soone whose hypothesis had just been confird from an unexpected direction.
"You went to the Archive."
"Yes."
The director was quiet for a mont. Then he reached into the drawer and placed a second docunt beside the report. Thicker. Different binding. The Division seal on the cover and below it: File 11-CC.
He had brought it already.
He had known Kai would read the Archive note and ask about it.
***
The file was denser than the extended record. More technical language, more data tables. He read it as fast as comprehension allowed, which was faster than most people read because he had spent years processing information quickly in situations where slow reading was a disadvantage.
The core of it was this:
Six years ago, the Rift’s boundary layer at Kael’s Seat had begun exhibiting micro-oscillations—small, rhythmic fluctuations in the perability of the boundary between zone and world. Not dangerous. Not destabilising. But consistent, regular, and increasing in amplitude over the monitoring period. The Division’s hypothesis, laid out across forty pages of asurent data and theoretical frawork, was that the Class 3 Rift was responding to sothing.
The file used the word anticipating.
The oscillations had the structure of a biological response—not random fluctuation but a pattern more consistent with a system checking readiness than with random environntal change. The Division could not identify what the Rift was anticipating because the precedent for a Rift exhibiting anticipatory behaviour existed in only one prior case.
The Incident.
Two hundred and seventeen years ago, the records from the period imdiately before Kael’s arrival in the city showed the sa oscillation pattern in what remained of the pre-Incident monitoring data. The Rift had been exhibiting the sa rhythmic boundary fluctuations for an estimated forty days before Kael arrived.
Kai set the file down.
He looked at the director.
The director looked back with the steady, patient attention he had used in every eting. Not performing calm. Actually calm, in the way of soone who had spent years arriving at an understanding that was frightening and had had ti to make his peace with the frightening part.
"The Rift has been oscillating for six years," Kai said.
"Yes."
"You don’t know what it’s anticipating."
The director was quiet for one mont. "I had a hypothesis for six years that I could not test," he said. "Maret’s report arrived from the highland trail eight months ago."
Kai sat with that.
The Rift had started oscillating six years ago. Maret had found him eight months ago. The Division had been watching the oscillation for six years waiting for sothing to arrive that would explain it.
He had arrived.
"What does it do," he said. "When the carrier gets close."
"In the Incident, it restructured," the director said. "The boundary layer moved and the zone classifications around it shifted. Zone fourteen’s reclassification six years ago—the one you found in the Archive—was a minor version of that restructuring. It happened before you arrived. The Rift did not need the carrier present to begin the process."
He folded his hands.
"It needed to be anticipating one."
***
Kai looked at the man across the desk. Twenty years at this Division. Two centuries of incomplete records. A Rift that had been checking its readiness for six years.
"Are you afraid of what happens when the carrier gets close to it?" he asked.
The director considered the question the way he considered everything: without rushing it.
"I am careful of it," he said finally. "Which is not the sa thing. Fear wants distance. Care wants understanding." He looked at the file. "I have spent twenty years wanting to understand the Incident. I will not close the distance faster than the data recomnds. But I will not prevent the distance from closing either."
He t Kai’s eyes.
"You are not Kael. You have arrived in this city with more deliberate control than he had, and with a system that is more developed than what the records describe him carrying. Whatever happens when you approach the Rift will not be the sa as what happened in the Incident."
He paused.
"It will be sothing new."
The word settled in the room the way important words settled—not loudly, but with weight.
Kai stood. He picked up the note Sael had left—the one he had brought in his coat—and set it on the desk beside File 11-CC.
"I’ll read the full file," he said. "When I’m ready."
The director nodded.
That was the eting.
***
Soren was waiting on the street outside the Division building.
Kai stopped.
Soren looked at the building behind him with the expression of a man who had done the calculation of where Kai had gone and arrived at the correct answer. He did not ask about the eting. He said: "The C-zone support tier contracts open at noon."
They walked together toward the mission board.
The city moved around them in its full mid-morning energy. Hunters going to and from the entry stations, the mission board, the material exchange. Flag colours above the buildings. The Rift’s glow at the edge of the eastern district, its deep pulse unchanged by anything that had happened in the director’s office.
Soren said, without looking at him: "My brother took eleven months to confirm Predator Body. He had three generations of Steel Path bloodline behind him."
Kai did not answer.
"I’ve been D-Rank for nine months," Soren continued. "I’ll make C-Rank by the end of this cycle if the next zone contracts go the way the last month has gone." He paused. "I thought D-Rank was the slowest part. Everyone says it is."
"It usually is," Kai said.
"Not for you."
Soren let that sit without demanding a response. Then he said: "When you make C-Rank, I want to be in the zone for it."
It was not a request exactly. More a statent of intention.
Kai looked at him. "You’ll have made it first."
Soren almost smiled. The almost was all the expression he allowed. "Then I’ll be in the zone from the other side of the rank line and it will still be interesting."
They reached the mission board building and went in.
***
He stood at the board for a while after filing the C-zone support tier registration for Dorath’s team.
The board was a different thing to him now than it had been on the first morning in the city. Then it had been a system to decode—types, grades, tiers, permit requirents. Now it was a landscape he could read. He knew which zone contracts produced what material grades. He knew which creature types created which kinds of fights. He knew what Dorath’s team could handle and where adding his output changed the shape of a mission. He knew what the board’s notes section ant when it said irregular zone activity and what it ant when it said elevated creature density near centre.
He had been in this city for less than three weeks.
The system ran an update while he was standing there.
Frawork loading: 83%
Evolution Points: 271
Active fusions: Impact Fra / Predatory Burst Step / Adaptive Recovery
Body rank: Predator Body
Guild rank: D-Rank
C-zone support tier: registered
Skill fusion candidates: 2 remaining — next available after sufficient path material accumulation
Next threshold: 90% frawork — path compatibility analysis unlocks
Path compatibility analysis.
A new function he had not seen listed before. It would unlock at ninety percent frawork loading. He did not know yet what it did. The system had not shown him a description.
He looked at the board for another mont.
The next missions would take him into C-zone support work. Better material. Harder creatures. More EP per kill. The frawork would advance faster from genuine D-zone and C-zone adjacent pressure than it had from E-zone work. The hold on evolution point spending would reduce further. The remaining fusion candidates would beco clearer as the path system continued loading.
Everything was moving in the sa direction at the sa ti.
That was what it felt like when a plan was working.
He left the board and walked out into the city, which was full of hunters doing the sa kind of work at the sa kind of pace, none of them knowing what the Rift at the east end of the valley had been doing for six years, none of them knowing what the man with the D-Rank badge and the three active fusions and the Predator Body and the monitoring flag and the director’s careful attention was going to do next.
He was beginning to understand that the most dangerous thing about him was not any single ability or fusion or accumulated trait.
It was the fact that he was still learning.
And he had not yet begun to go fast.
User Comments
0 comments from readers