The D-rank threshold assessment was scheduled for 0900 Friday. He'd asked Rowan to push it to 0900 specifically — early enough that the channels were settled from the morning circuit work but not fatigued from an afternoon session. The technician from the E-rank assessment was available at that time. She'd said she was specifically interested in the follow-up data.
He arrived at 0853. She was already at the equipment.
"Four months since the E-rank," she said, scanning the readout as he settled into the assessment chair. "The improvement rate has been—" She checked the number. Looked at it twice. "Significant."
"Consistent training approach."
"The technique integration work." She remembered. "The partial execution methodology." She was already running the junction efficiency analysis. "Yield me a moment."
He gave her the moment. The assessment equipment was reading the channel architecture and building the map — the density distribution, the junction efficiency ratings, the flow pattern at the critical threshold markers.
At 0912, she turned the screen toward him.
The threshold number: 100.7% of D-rank requirement.
"Above threshold," she said. "As of the last three days at minimum — the architecture would have crossed the threshold line between Tuesday and Thursday based on the trajectory." She looked at the secondary readout. "The junction efficiency is at a level I'm going to need to document separately. This is the highest E-to-D transition efficiency rating I've processed in four years of certification work."
"I'll take that as confirmation."
"It's confirmation." She printed the certification. "Kael Ashford, D-rank, certified as of Friday at 0914." She looked at him before handing it over. "The S-rank technique integration work — once you're at a density level where you can execute more of the fragment range—"
"I know."
"The acceleration will compound." She handed the certification across. "Whatever you're building toward, you're on a pace to get there." She paused. "I'd be interested to see the C-rank transition when it happens."
"I'll come back."
He took the certification and left.
---
The paired assessment exercise was at 1400 in the mandatory training facility. He was there at 1350, sat in the assessment observation area, and watched the pairs move through their exercises.
Fenra and Marcus were paired fourth. He'd known they would be — Castellan's pairing methodology ran class-complement analysis, and the anomaly in both class types (undocumented interaction potential between Void Perceiver and Soulbrand Resonator) would flag them for priority pairing. Castellan was building documentation that the Association's research division wanted. She'd prioritize the pairs that generated the most interesting data.
They came out to the assessment floor at 1437.
The exercise format: two awakeners, one shared objective, the evaluators watching how they negotiate the division of capability and how their class abilities interact. The objective Castellan had set for this pair was spatial — map an obscured section of the facility's sub-basement layout without entering it.
Fenra's Void Perceiver class could perceive the spatial density of the section without line of sight. Marcus's Soulbrand Resonator could — theoretically, if the application extended in this direction — read the channel signatures of any living entities in the space and provide a different layer of information.
They stood at the access corridor and looked at each other.
"I'll take the spatial scan first," Fenra said. "Give me two minutes to build a density map. Then tell me what you're reading."
Marcus nodded.
She closed her eyes. Not theatrical — the class didn't require visual input, but reducing external stimulus helped early-stage practitioners focus the perception bandwidth. He'd seen this in other Void-adjacent classes over the years. Eyes closed, posture slightly stilled, the quality of attention going inward and then outward in a different direction.
Two minutes passed. She opened her eyes.
"Six rooms. The primary corridor runs east-west, approximately forty meters. Four rooms off the north face, two off the south. The two south-facing rooms have higher material density — storage, probably. One of the north-facing rooms has a significantly lower density zone in its southeast corner." She paused. "Something was removed recently. The density map has a discontinuity there."
Marcus had been watching her with a focus that had the quality of someone running a parallel process. "Three people in the section," he said, before she finished. "Two in the first north-facing room, together, approximately eight meters into the corridor. One in the corridor itself, approximately twenty-two meters east of the access point. Moving slowly."
"Moving east or west."
"East. Toward the end of the corridor." He paused. "The one in the corridor has an unusual channel signature. Not awakened — the structure is different. More like—" He stopped. "I don't have a reference category for it."
Castellan, observing from the assessment station, made a note. Something substantial — he could tell from the amount of movement on her tablet.
"Combine the data," Castellan said from the station. "You have a spatial map and a personnel read. What does the combined picture tell you."
Fenra and Marcus looked at each other. A brief negotiation — not verbal.
"The person in the corridor," Fenra said, "is in the section of the density map with the discontinuity. The removed-material zone." She looked at Marcus.
"They're not moving toward the rooms. They're moving toward the east end of the corridor." He paused. "The corridor ends in a room — the east terminus."
"Not a room. The density reads as a wall there. No room." Fenra looked at the access point. "But they're moving toward it."
Castellan looked up from the tablet. "The east corridor terminates in what appears to be a wall from the density map. It's actually a concealed door — the material is dense but there's a frame structure behind it. Standard concealment construction." She paused. "That's the kind of sub-map detail a density perception can miss if it's reading aggregate density rather than structural composition." She looked at Fenra. "Did you get the frame structure."
Fenra's expression went carefully neutral. "No."
"The aggregate reading doesn't resolve fine structural detail at this range." Castellan made another note. "Marcus — the person in the corridor. What's the resolution on their channel signature."
"At twenty-two meters, I have a clear read on the signature type but not the specific individual. If they came closer—"
"Don't proceed. This is the data point I needed." She looked at her tablet. "Two class types with fundamentally different perception modalities, working from the same objective, producing complementary information sets. The combined output exceeds what either class can produce individually." She looked at them. "That's the documentation I was looking for."
Marcus looked at Fenra.
"The concealed door," he said, low enough that it was directed at her rather than the room. "Did you know."
"I suspected. The density anomaly suggested structure. I didn't want to over-read it." She paused. "You knew someone was moving toward a dead end."
"I didn't know it was a dead end."
A beat.
"We'd have gotten there together," Fenra said.
He was watching from the observation area and thinking about this: two people with different perception capabilities, neither complete alone, building toward a picture that was more accurate than either could produce independently. He'd been doing this with Rowan for months — Kael's knowledge providing direction, Rowan's analysis providing depth. The combination working better than either alone.
Marcus and Fenra had found a complementary alignment in forty minutes.
He'd had a different analysis of Marcus's class development trajectory. He revised it now.
---
After the exercise, Marcus found him in the observation area.
"She let me read her," he said. Not accusing — just noting.
"Did you ask."
"No. I told her I was doing a suppression exercise and asked if the passive read was bothering her. She said it wasn't." He paused. "She was an interesting subject."
"What did you read."
He looked at the empty assessment floor. "A Void Perceiver perception channel is different from standard channel architecture. The perception function uses a lateral branching structure that most classes don't have — the branches extend outward in the direction of perception range." He paused. "When she's actively using the class, the branches are live. When she's not, they pull back but don't fully retract." He looked at his hands. "I could tell, through the whole exercise, when she was actively scanning versus when she was processing what she'd already scanned."
"That's useful information for a team context."
"Yes." He paused. "What she sees when she scans — I can potentially read the signature of what her branches are oriented toward, if the density is high enough." He said this carefully, like someone who was aware of how it sounded. "Not what she's perceiving. But the direction and focus of the perception."
"You could read a Void Perceiver's perception focus."
"In theory. I haven't tested it deliberately." He looked at his hands. "I'm trying to build the ethical framework as I go. For everything this class can do, I'm trying to figure out what it should do."
"How's that going."
"Slowly." He looked at the floor. "The Church would have given me a framework. The Association training program is trying to build one for a class that doesn't exist in their curriculum. You—" He paused. "You give me information about the regulatory boundaries. That's useful. But the framework I actually need is the one that tells me what kind of person I want to be, not just what the code permits."
Kael looked at him.
In the original timeline, Marcus had been given the framework by the Church and then abandoned it when the resentment became stronger than the training. The framework had been external — it hadn't rooted.
This Marcus was building from the question rather than from the rules. That was different.
"What kind of person do you want to be," he said.
Marcus thought about it. Actually thought — not reaching for a prepared answer.
"One where the ability is useful without being the most important thing about me," he said. "In the healing class pathway, I would have spent years learning to see damage and repair it. The framework there was service — the ability in service of the patient." He paused. "The Soulbrand Resonator doesn't have a service framework. It has an influence capability. That's a different center of gravity."
"The framework you build will reflect what you center."
"Yes." He looked at the assessment floor. "I know." He paused. "The mentorship program. Is it supposed to include conversations like this."
"The program's stated purpose is skill development support." Kael looked at him. "Conversations like this are skill development."
"That's a generous definition."
"Frameworks are skills."
Marcus almost smiled. Not quite — but he was getting closer to it. "All right," he said. "Then I'll see you Monday."
He walked away. Kael watched him go and thought about the Church's healer training, the years of curriculum that had produced a man with a framework he hadn't chosen, that the resentment had eroded from outside in.
This version of Marcus was building his own, from scratch, from a question.
It might hold better.
---
Fenra's transit hub observation on Thursday had produced one result: the Thursday meeting had not occurred.
She'd been at the hub at the right time with the spatial perception running. No one matching the movement signature from the Harborwatch meeting had appeared in the relevant window. The Thursday protocol had been changed.
He'd expected this. Rowan had said the protocol would change within forty-eight hours of a possible exposure. It had changed, which confirmed that either Dae Yeun had noticed the Thursday surveillance or had decided to pause the Holler meeting schedule as a precaution.
Either way, the direct thread was closed. The documentation package was at its current state — confirmed connection, incomplete chain, one missing link.
He sent Rowan: *Assess how long before the Thursday meetings resume, if they do.*
ROWAN: *If they believe they were surveilled and the surveillance source hasn't been identified — they'll wait. Could be weeks. Could be longer.* A pause. *The documentation package as-is — the connection to Dae Yeun through the approval records, the Fenner network structure — is enough for an internal ethics review. Not enough to definitively expose Crane without the client chain closed.*
*How much of the client chain do we need.*
ROWAN: *One more confirmed link between the Fenner-Yeun-Holler network and Crane's office directly. The current evidence shows Association-adjacent involvement through a compliance analyst. That's corruption of a support function — minor. The link to Crane's office makes it a Director-level issue.* A pause. *One more link.*
*We'll wait for the Thursday meetings to resume. Then Fenra can track.*
ROWAN: *That could take weeks.*
*I know.* He looked at the D-rank certification on his desk. *We have time.*
The D-rank certification. Four months and change since the morning before the Awakening. He'd been E-rank for three weeks and D-rank as of today. C-rank in three months at current pace. The channel architecture was solid enough that the trajectory was reliable rather than optimistic.
He'd been S-rank when he died. He was D-rank now. The distance between those two points was still the whole story.
But D-rank was real. The certification was in his hand. Rowan had updated the projection.
He texted Rowan: *D-rank certified this morning.*
ROWAN: *I know. The Association's database updated at 0916. I've revised the projection.* A pause. *C-rank in eleven weeks at current pace. The mandatory training program is providing better architecture support than I'd anticipated. Castellan's approach is unusually well-calibrated for your development pattern.*
*She's working from what she can observe.*
ROWAN: *She's working from excellent observational skills and a long experience base. The result is better than what the standard program would provide.* A pause that felt like the digital equivalent of clearing a throat. *Kael. I want to flag something I've been tracking for the past week.*
*What.*
ROWAN: *Dorian Vex's network activity. I've been monitoring the Association's public social registry for first-year cohort members — it tracks voluntary guild affiliation, study groups, cohort connection registrations. Dorian has been building connections in the cohort at a rate approximately twice the median.* A pause. *He doesn't have a class yet. He awakens in approximately three and a half months. But he's already building the social architecture that will become useful the moment he has something to offer.*
*He knows he's going to have something to offer.*
ROWAN: *He's always known. In the original timeline, the pattern would have been the same — build the network before the class, so the class drops into a structure that's already positioned to use it.* A pause. *He attended two of the Association's first-year cohort events last week. Both events included members of the advanced cohort.* A longer pause. *Kael. He was at the event where Sooha met Fenner for an introduction to the broader talent development network.*
He went still.
*They were in the same room.*
ROWAN: *Yes. The introduction event Fenner hosted Thursday evening at his office. Dorian was listed as a guest — Fenner's partner registration shows him as a 'cohort network observer,' which is a category that allows non-awakened cohort members to attend Association-partner events.*
*Fenner invited Dorian.*
ROWAN: *Or Dorian was already known to Fenner and received a standard invitation. I can't tell which direction the connection runs.* A pause. *But if Dorian is in contact with Fenner, and Fenner is working for Crane's network — Dorian is building toward Crane's infrastructure before he even awakens.*
He looked at the D-rank certification in his hand.
In the original timeline, Dorian had built his alliance with Crane after he'd become a Shadow Assassin, after he had something to offer. It had taken two years.
This timeline: he was sixteen years old and already building toward the same infrastructure, faster, with no class yet.
Because Kael had changed things. Because the mandatory enrollment had created events that had created Fenner's operation that had created a talent network event that Dorian had attended.
Another chain from his own actions. Another divergence he hadn't anticipated.
He put the certification down.
*When is the next talent network event.*
ROWAN: *Two weeks. Fenner's office, same format.* A pause. *Sooha will be there. Dorian's invitation is presumably standing.* A longer pause. *Kael. If Dorian and Sooha form a connection through Crane's talent network before either of them has full context for what the network is—*
*I know.*
He looked at the certification.
D-rank. The first floor of the building. He was in the building.
*Two weeks,* he sent back. *Give me the event details.*
ROWAN: *Sent.*
He picked up the certification and put it in the folder with the E-rank documentation. Stack of papers that represented four and a half months of systematic rebuilding, layer by layer, the architecture that had been S-rank and was rebuilding itself one certification at a time.
He was in the building.
Dorian was in the building too.
And the building had more floors than either of them could see from here.
He'd see the next one when he got there.
