She had been expecting him for three days.

She did not say this immediately. She said it after she had risen from her desk and walked to the inner room at the Archive building’s rear—not the main archive floor with its catalogued shelving, a smaller room Kai had not been shown before, its contents differently organised. Not by subject or date. By something else. He could see it in the way the folders were arranged on the cabinet’s shelves: not alphabetically, not chronologically. By a logic that was hers alone.

She had known for three days because the Archive’s oscillation monitoring equipment—older than the director’s instruments, built to different specifications, calibrated by the builders’ original documentation rather than Guild standard methodology—had been reading the Rift’s secondary encoded layer since the day after Stage 1 activated.

She had not sent a note. She had waited for him to come.

She carried four folders from the inner room and set them on the table.

They were labelled by city name. Vael’s Crossing. The Pale. Ren-Sarath. And one with a name she had written in a different hand—older, the Archive’s formal notation rather than her own—that Kai did not recognise.

She picked up the Vael’s Crossing folder and placed it on the table in front of him. She put the other three back on the shelf in the inner room. She closed the inner room’s door.

"The second Rift first," she said.

The Vael’s Crossing folder was thinner than the Kael’s Seat documentation had been.

That alone told him something. The Kael’s Seat builders had completed all five stages and documented each one thoroughly. The Vael’s Crossing builders had completed three stages and then stopped. Three stages of documentation instead of five.

"A separate group," Arveth said. She sat across from him while he opened the folder—the same position she had taken in every meeting, unhurried, letting him read at his own pace and adding words where they were needed. "Not the Kael’s Seat builders. A different team, working in parallel. They corresponded—there are letters in the Kael’s Seat documentation that reference the Vael’s Crossing work. The Kael’s Seat builders knew Stage 3 had been completed there. They did not know what happened after. The correspondence ends."

She looked at the table.

"The Archive has three theories about why the Vael’s Crossing builders disappeared. None of them are documented as fact. I will not share theories."

He read the folder.

Stage 1 in the zone system’s deep substrate, documented with the same architectural precision as Kael’s Seat’s records. Stage 2 connecting to Stage 1, built nine years later. Stage 3 in Vael’s Crossing’s outer zones, completed and documented, with a notation in the margin of the final Stage 3 entry: structural flaw identified at third junction, repair planned at Stage 4 commencement. They had known Stage 3 was imperfect. They had planned to fix it when they returned.

They had not returned.

Stage 4’s planned location was documented but unbuilt. Stage 5’s design was complete—the city connection specifications were identical in form to Kael’s Seat’s Stage 5, modified for Vael’s Crossing’s specific substrate geology—but it had never been executed. The chain ended at Stage 3.

The entity section was different from Kael’s Seat’s.

The Kael’s Seat builders had described their entity as ancient and still—something that had been in the layer below since before living memory, dormant at the surface of awareness, patient. The Vael’s Crossing builders described theirs differently. "Recently aware." Two words, but the builders had added a parenthetical that Arveth had underlined in the margin: estimated dormancy period significantly shorter than the Kael’s Seat entity’s. Cannot confirm without direct contact.

"A younger entity," Arveth said when he reached that section. "Or an entity that woke more recently. The builders’ estimate is rough. The documentation is incomplete." She paused. "What they did observe is that the Vael’s Crossing entity showed responses to the Stage 3 construction that the Kael’s Seat entity had not shown at its Stage 3. More active. More—" she chose the word carefully— "impatient."

He looked at the structural flaw notation in Stage 3’s final entry.

Third junction. He had no physical description of where the third junction was in Vael’s Crossing’s Stage 3—that would require reading the structure directly, which required going there. But the notation confirmed what the entity’s weight in zone 20 had told him: something in Vael’s Crossing’s chain was damaged and needed work before it could function.

"The repair method," he said.

Arveth looked at him steadily.

"Not documented. The builders noted the flaw. They planned to determine the repair method when they reached Stage 4. They had six months between Stage 3’s completion and their planned Stage 4 start date." She did not look away. "They did not use those six months to document a repair method. The Archive has the correspondence from that period. They were writing to each other about Stage 4’s design, not Stage 3’s repair. They may have assumed the repair would be obvious when they returned to it."

She waited.

"You are not a builder," she said. "You are a carrier. The builders’ tools were structural—they worked in substrate architecture with materials and techniques. Your tools are sovereign-class output and path-layer interaction. Whatever the repair method is, it is probably not what the builders would have used."

She looked at the folder.

"You will need to find the method yourself."

He walked out of the Archive building into the late afternoon.

Mira was outside. She had been at the eastern district while he met with Arveth, and had come to meet him when the vault pair had signalled—not a directed signal, the device responding to the proximity of the Vael’s Crossing folder’s documentation in a way she had not been able to explain when he asked her about it later. The vault pair read road network architecture at any proximity. The folder’s contents described road network architecture. The device had found them relevant.

She held the shells when he came out.

They were warm.

Not the intermittent pulse from two days ago. Not the full glow of the activated chain. A baseline warmth—the warmth of a device that was running in receive mode, picking up something distant.

"It’s trying to connect," she said. She looked east—the direction of Vael’s Crossing, 900 kilometres away. "Not through our chain. There’s no completed chain to connect through. Through the substrate layer directly. The same way our entity pressed upward through the zones before the chain was open."

She held the shells.

"The Vael’s Crossing entity doesn’t know there’s a carrier. It doesn’t know there’s a completed chain anywhere in the world. It’s pressing upward the same way ours did—without a channel, without a direction, just the fundamental drive to reach the surface layer it was built to manage." She looked at the shells’ warmth. "The vault pair reads that pressure from 900 kilometres away through the substrate layer. It’s been doing this for fourteen months."

She looked at him.

Not urgency in her voice—she was not a person who communicated urgency through tone. But the precision was there. The careful weight she gave words when the words needed to carry more than their surface meaning.

"Fourteen months," she said. "Of casualties. Of hunters going into zones without knowing what they were facing. Of a branch director running without sleep trying to solve something with tools that were never built for it."

She set the shells against her chest.

"We need to go."

He looked at the Archive building’s stone face. At the eastern district’s glow visible above the roofline to the right. At the Vael’s Crossing folder under his arm.

He had a damaged Stage 3 with no documented repair method.

He had King-grade path material accumulating toward the next body rank threshold.

He had six people who had crossed a world together and were still intact.

He had the entity’s continuous ambient read through the sovereign seed—real-time surface-layer data from a managed Rift, which no carrier had possessed in six centuries and which might tell him things about an unmanaged Rift’s condition by comparison.

He had enough.

Not everything. Enough.

"Not yet," he said. "King Body first. Then we go."