Quick Verification

Please complete the check below to continue reading. This helps us protect our content.

Loading verification...

The visual he'd taken from Harborwatch went to Rowan that night — a description detailed enough to run against the Association's internal staff directory, which Rowan had partial access to through the assessment system's administrative layer. The age range narrowed the candidate set to forty-three names in the compliance division. Physical build and movement pattern analysis eliminated thirty-seven of those.

Six remaining. Rowan sent the names at 0200 with a note: *Cross-reference against the Fenner network structure is not yet complete. These are candidates, not confirmations.*

He looked at the six names. Mid-level compliance staff, most of them. The kind of administrative function that was invisible by design. He didn't know any of them. They hadn't existed in his original timeline in any way that had reached him — a hunter's career didn't intersect much with administrative compliance until it had to, and in the original timeline his career had intersected with Crane's office only at the end, when it was already too late.

He started with the easiest cross-reference: public Association records. Which of the six had any logged connection to Fenner's consulting business, to the shell company registration, to the program partner network.

One name appeared in the program partner approval records. Not as a signer — as a reviewer. The approval paperwork for Fenner's mentorship program partner access had been reviewed by someone in the compliance division before approval. Standard administrative process. Except the reviewer was one of his six.

Her name was Dae Yeun. Twenty-seven, compliance analyst, four years in the division. The paperwork she'd reviewed was dated six weeks ago — approximately when Fenner had begun his expansion into the cohort talent identification operation.

He sent Rowan the name at 0230.

ROWAN: *Running the deeper cross-reference now. If she processed the approval and has downstream involvement — that's a conflict of interest violation. Documentation exists.* A pause. *This is something the Association's own ethics review process would have to investigate if it were presented to them.*

*Build the documentation package. Don't present it yet.*

ROWAN: *Understood. How long before you want to present.*

*When I know the full chain. Not yet.*

He put the phone down. The circuit work was waiting — he'd been doing it every evening, and the D-rank threshold was approximately two weeks away now. The architecture was at a point where he could feel the progress in the way the circuits settled, the reduced turbulence at the junction points. He did forty-five minutes.

At 0400 he slept.

---

Friday morning, Rowan sent a longer message.

ROWAN: *Dae Yeun is the Thursday contact. I've confirmed it through transit records and a second indirect cross-reference through the program partner communication logs. She's not just reviewing Fenner's paperwork — she's the active liaison between Fenner's operation and the Association's compliance infrastructure.* A pause. *If she's been made, she'll know within the next forty-eight hours.*

*She was almost certainly made.*

ROWAN: *Then she'll move to protect the chain.* A pause. *The most vulnerable link from her perspective is Holler. Holler is the visible black-market connection — his records would be the first thing an investigation would find. If she moves to protect the chain, she protects Holler by cutting him.*

*Cutting him how.*

ROWAN: *Either buying his silence definitively or dissolving his contract and letting him disappear. Either way, we lose the thread.*

He thought about this. Dae Yeun, twenty-seven, compliance analyst. She'd been at the Harborwatch meeting, she'd possibly seen him on the transit platform, she'd know that the Thursday routine had been watched.

If she was smart — and the network architecture suggested she was — she'd already begun damage control.

He messaged Rowan: *How long do we have before Holler is unreachable.*

ROWAN: *If she moves today — twenty-four hours. If she waits to assess whether the surveillance was real — forty-eight to seventy-two.*

He looked at the time. 0713. The mandatory training session was at 0900. Two hours.

"The Monday mentorship session," he said to himself, working through it. The pattern: Fenner had approached Fenra, Fenra had given a non-answer, Fenner's operation had continued regardless. The Thursday meeting at Harborwatch had been Dae Yeun maintaining the Holler relationship. After the Thursday meeting, Holler had delivered a case.

What was in the case?

He called Rowan.

"The case Holler passed to Dae Yeun at the meeting," he said, when Rowan answered. "What did the transit hub access records show for Thursday afternoon."

"Dae Yeun went through the transit hub at 1511. The case she had would have been in a standard carry-bag — the hub's security system logs bags over a certain size. She checked a bag of approximately sixty by forty centimeters at 1511." He was already pulling the data. "Exit was at 1523."

"That's twelve minutes. She transferred the case."

"To someone else who was also there." A pause. "The hub's access log shows four individuals entering within the twelve-minute window who had valid Association staff access codes. Three of them are regular users — their transit patterns are consistent going back weeks. The fourth accessed the hub at 1514 and exited at 1520."

"A six-minute window."

"Exactly the time needed for a handoff." He paused. "I don't have the fourth person's name. The access code matches an emergency transit authorization — a code that multiple individuals can use, not traceable to a specific person."

Which meant the end of the chain was still invisible.

He'd watched the Thursday meeting, followed Dae Yeun to the transit hub, possibly been made, and the case had still been transferred to someone he couldn't identify. The thread ran to a name he didn't have.

"The Fenner approach to Fenra," he said. "Was there a follow-up contact."

"No. After her second non-answer message Wednesday, Fenner didn't respond." A pause. "But there was activity in the partner communication system. Fenner sent two messages on Thursday afternoon — not to Fenra. To a different cohort member."

The timing. Thursday afternoon. The same afternoon as the Harborwatch meeting.

"Who."

"Park Sooha."

He went still.

"He approached Sooha on Thursday afternoon," Rowan said. "The message was similar in structure to the Fenra approach — 'specialized spatial analysis applications,' development opportunity, request for a meeting." A pause that carried weight in it. "She responded Thursday evening. She said yes."

He sat with this.

Thursday afternoon: he'd been at Harborwatch watching the Holler-Yeun meeting. He'd followed Yeun to the transit hub. He'd come back empty-handed and possibly exposed. Meanwhile, across the city, Fenner had pivoted from Fenra — who'd been giving non-answers — to Sooha, and Sooha had said yes.

He'd been in the wrong place.

He'd spent Thursday protecting Fenra from a threat that hadn't been pointed at Fenra on Thursday. The threat had moved, and he'd kept his position.

"When is Sooha's meeting with Fenner," he said.

"Saturday afternoon. Today." A pause. "It was arranged last night. She's meeting him at his office at 1400."

He looked at the time. 0724. Six hours and thirty-six minutes.

"Can I get to her before the meeting."

"You could message her through the Association's cohort system. She knows you from the advanced cohort — you were both in the assessment on Thursday, different groups, but she'd recognize the name." A pause. "The question is what you say."

What he could say: your class is being targeted for a strategic operation by someone with Association connections and you should not take the meeting. True, but unverifiable from her perspective, and the source was a cohort member she'd barely met.

What he could say: Aldric Fenner's development consulting operation is connected to parties who will use your class for purposes that aren't in your interest. Also true, also unverifiable without context.

What he could say: don't go. Which was the most direct and the least persuasive.

"Send her my contact information through the cohort system," he said. "Include a message. Keep it brief."

"What message."

He thought.

"Tell her I know something about Aldric Fenner's client structure that she should hear before the 1400 meeting. Ask if we can talk this morning."

"Done." He heard the keys. "Sent at 0729."

He waited.

At 0751, when he was already moving toward the mandatory training session, his phone buzzed.

Not Sooha. The cohort message system showed the message as delivered and read. No response.

At 0832, during the training session warm-up, another buzz.

SOOHA: *I've got the meeting at 1400. I'll hear him out and make my own decision. Thanks for the heads up.*

He looked at the message for three seconds, then put the phone away.

She wasn't going to cancel. She'd heard the warning, processed it as unsolicited caution from a near-stranger, and decided to proceed. Which was reasonable from her position. She had no reason to weight his warning heavily.

He'd warned the wrong person on Wednesday — spent the time and effort positioning around Fenra, who'd already been thinking clearly about what Fenner was offering. Fenra hadn't needed the warning. She'd been ahead of it.

Sooha had needed it. He'd given it to her too late and without enough context to be persuasive.

Dae Yeun had the network evidence he'd spent a week building and was probably destroying it right now. Sooha was going to take a meeting that would put her in Crane's talent acquisition network. And the person who'd received the case at the transit hub was still a name he didn't have.

The training session started. He ran it with the part of his attention that handled training work. The rest was doing the accounting.

---

After the session, he found Fenra at the equipment room.

She was doing something with the spatial perception array — mapping the room's density field, apparently, running her class through the equipment's feedback mechanism in a way the equipment probably hadn't been designed for.

"Sooha is going to take the meeting," he said.

She looked up. "I know. She told me this morning."

He waited.

"We talked after the assessment debrief on Thursday," Fenra said. "She mentioned getting a message from a development consultant. She was excited about it — the offer sounded genuine to her." She put down the calibration tool. "I told her what I knew. Which wasn't much. I didn't have your full briefing on Fenner's client structure at that point."

"What did she say."

"That she appreciated the heads up but she was going to make her own assessment." She looked at him. "She's twenty. She's been making her own decisions since she was fourteen. She doesn't trust caution from people she hasn't established context with."

He looked at the array.

"I should have gotten to her faster."

"Yes." Fenra picked up the calibration tool again. "You were focused on me. I didn't need the focus — I was already tracking Fenner. You spent Wednesday building context that I'd already built." She said it without judgment. Just the fact. "The resource you applied to me would have been better applied to mapping the full cohort for secondary targets."

He'd been protecting the person who was capable of protecting themselves. And the one who hadn't been in his field of view had said yes.

"What happens to her," he said.

"That depends on what Crane's network does with a Void-adjacent Spatial Analyst." She looked at the array. "Probably nothing immediately harmful. They'll build access, create obligations slowly, make it uncomfortable to leave later." She paused. "The boiling-water approach."

He knew the approach. He'd watched Dorian Vex use it on people for years before he understood what he was seeing.

"Can you reach her."

"She and I have a better standing than you and she do — we talked Thursday, I wasn't as forward about the warning as you were." Fenra kept her eyes on the array. "I can keep the channel open. See how the meeting goes. She'll tell me something about it — she's the type who needs to process out loud."

"Let me know what she says."

"Yes." She looked at him. "The Dae Yeun thread. You were almost made Thursday."

"Possibly."

"If you were made, the chain tightens. Holler becomes unreachable and Dae Yeun limits her exposure." She set the tool down. "Which means the documentation package Rowan is building loses its most accessible thread."

"I know."

"There may be another thread." She looked at the density field display on the array. "I can perceive the spatial signature of repeated activity in a location. The transit hub Dae Yeun used Thursday — if I go there at approximately the same time next Thursday, I can build a spatial history of who uses the hub at that hour." She looked at him. "Not who they are. But their unique spatial signature. If the same person appears two weeks in a row during the same window, I can track their movement out of the hub on the second occurrence."

He looked at her.

"That's not something the Association's training program teaches for your class at this stage," he said.

"No." She began packing the calibration tool. "But it's in Illen's paper."

He looked at her for a moment. Lena had been working from Illen's paper too.

"We'll talk Wednesday," he said.

"We will." She picked up her bag. "For what it's worth — you weren't wrong to focus on Marcus. His class is a larger long-term variable. You just underestimated the operational sophistication of the entity you were watching." She paused at the door. "Now you know what you're working against."

She left.

He stood in the equipment room for a moment. The density array humming to itself.

Sooha was going to a meeting at 1400. The documentation thread to Dae Yeun was probably already tightening. The end of the chain was still invisible.

He'd protected Fenra, who didn't need protecting. He'd been in a coffee shop watching the wrong meeting while the right meeting had been arranged across town. He'd followed a contact to a transit hub and come back with a description and a six-name list and one confirmed connection and no actionable next step.

He'd spent a week and come out behind.

He stood there with that.

Then he went to find a coffee and reviewed the alternative acquisition sources for the channel-density item he'd lost two weeks ago, because the D-rank threshold was two weeks away and that was the one thing he could still move forward.

He'd make a different mistake tomorrow. That was the only option.

He found the coffee and a second candidate source for the density item and wrote a message to Rowan about the transit hub approach Fenra had proposed and scheduled the Wednesday briefing and drank the coffee.

One corridor at a time.

He was still in the building.