Chapter 26: Fallout

Gareth spent four hours on Monday mapping fragment conflicts.

He called it "channel compatibility analysis," which was the technical term, and he did it in the integration ring with every crystal active and Ren's monitoring equipment capturing data at the finest resolution the borrowed device allowed. Damien sat in the center and activated fragments in pairs while Gareth watched the oscilloscope and Ren watched the channel monitor and both of them compared notes with the specific concentration of specialists encountering a problem they'd been waiting to find.

"The Chronomancer/Tracker Prime conflict is class-family based," Gareth said after the first hour. He was making notes in a physical notebook. The handwriting was precise and old-fashioned. "Time-adjacent mana and spatial-trace mana generate interference because they're both operating in the meta-physical layer—the layer above standard elemental types. They don't conflict in the same channel. They conflict in output."

"Two different frequencies hitting the same receiver," Damien said.

"The receiver being your external mana field. Yes." He made another note. "The conflict doesn't degrade the fragments themselves. It degrades the usable output when both are active simultaneously. Like two conversations happening in the same room—you can hear both, but neither is as clear as one alone."

"How many pairs have this type of conflict?"

"We've found three in the first hour. Chronomancer and Tracker Prime. Dream Walker and Psion—both operate in the consciousness layer, similar interference pattern. And the Dimension Walker and Space Mage."

"Three confirmed."

"Three found in one hour of testing. I estimate eight to twelve total when we complete the map." Gareth set his pen down. "This is why I told you that Gareth's third Shifter—the one who reached a hundred and twelve fragments before the conflicts began—was smarter than you. She'd done this analysis at thirty fragments. She'd mapped her full conflict landscape before adding new ones."

"I didn't know to do it."

"No. You didn't." He picked up his pen. "That's not criticism. That's gap identification. You didn't know, and now you know, and we address it." He turned to Ren. "The conflict pairs—when both fragments in a conflict pair are active simultaneously, is there any mana system damage?"

"Based on the readings I'm seeing, no structural damage," Ren said. "The interference is at the output level, not the channel level. Like electrical noise in a circuit—unpleasant and disruptive, but not damaging." He considered. "Unless the interference is sustained at high intensity under stress. Then I'd want to run more tests."

"We'll run more tests," Gareth said. He looked at Damien. "The practical implication is that your designated fragment loads need to be designed with conflict pairs in mind. If you include Chronomancer in a load, you don't include Tracker Prime. If you include Psion, you don't include Dream Walker."

"The ten-fragment load rule becomes more significant."

"Considerably. Ten fragments without conflict pairs requires knowing which pairs conflict. Which is why we're spending four hours doing this today." He looked at his notebook. "Forty-seven pairs tested. Eleven remaining. Let's continue."

---

The complete conflict map took until three PM.

Ten conflict pairs confirmed. Of Damien's seventy-five fragments, twenty-six were involved in conflict relationships with at least one other fragment. No fragment was involved in more than two conflict pairs—it was a partial mesh rather than a full network of incompatibilities.

"The good news," Gareth said, when the map was complete, "is that none of the conflict pairs involve your primary combat fragments. Warrior, Rogue, Scout, Fire Mage, Earth Mage—clean. No confirmed conflicts."

"The bad news?"

"Five of your detection fragments are involved in conflict pairs. The meta-physical layer fragments—Chronomancer, Psion, Dream Walker, Dimension Walker, Space Mage. These are the rare classes you absorbed specifically for their unique capability profiles, and three of them conflict with each other." He looked at the map. "Running more than one at a time was always reducing your effective capability. You didn't know you were doing it."

"How much reduction?"

"The Chronomancer/Tracker Prime conflict was approximately forty percent degradation to each. The Psion/Dream Walker is more severe—sixty percent. You've been using both in certain dungeon approaches."

"I use them sequentially, not simultaneously."

"You shift between them during a run, yes. But the channel residue from one active fragment persists for thirty to sixty seconds after deactivation. If you shift from Psion to Dream Walker within that window—"

"They've been conflicting without my knowing."

"For every run where you've used both in sequence." Gareth closed his notebook. "This changes your dungeon approach protocols. The load design has to account for conflict windows, not just conflict pairs."

Maya, who had been listening from the bench, was making notes. The specific expression she wore when information was reorganizing her existing frameworks—not discomfort, precisely, but the visible process of structural adjustment.

"The hundred-fragment plan," she said. "Acquiring twenty-five more fragments without adding new conflict pairs."

"Difficult. The fragments that remain most useful to absorb at this stage are rare and unusual classes—exactly the classes most likely to operate in the meta-physical layer where conflicts concentrate." Gareth looked at her. "The acquisition plan doesn't stop. But the selection process becomes more sophisticated."

"We screen for conflict compatibility before absorbing."

"Before approaching a dungeon with a target entity. If the entity's class operates in a conflict-prone layer and we can't identify a clean integration position in Damien's network—we don't absorb."

"We skip dungeons," Damien said.

"We prioritize dungeons based on fragment compatibility rather than fragment rarity." Gareth stood. "You have seventy-five fragments. Twenty-five more to the threshold. Not every available dungeon is worth running for every available fragment."

It was a different kind of discipline than the one he'd been applying. Not more fragments, better fragments. Quality of integration rather than quantity of absorption.

"The Void Walker class," he said. "From the Ninth District dungeon we didn't clear."

"What's its mana layer?"

"Dimensional boundary manipulation. Similar layer to the Dimension Walker and Space Mage."

"Both of which are already in your network. Both of which are already in conflict pairs." Gareth raised an eyebrow. "Was the Void Walker on your priority list specifically because of its rarity?"

He didn't answer. The answer was obvious.

"Yes," Gareth said. "You've been prioritizing rarity without screening for compatibility. The Void Walker would likely add a third conflict to the dimensional layer." He looked at the conflict map. "Which doesn't mean you don't absorb it. It means you absorb it with full awareness of the integration cost and the operational limitations that follow."

Damien looked at the conflict map spread across Gareth's training floor. Ten pairs. Twenty-six fragments in conflict relationships with others in his network. He'd been operating at less than maximum effectiveness in certain scenarios for months without knowing it.

"Fragments are always beneficial," he said.

"What?"

"Something I assumed." He looked at the map. "I was wrong."

Gareth looked at him. The assessment expression.

"Yes," the old man said. "You were."

---

Wells called at five PM with a detailed account of the subcommittee enforcement action and what she'd done about it.

"The subcommittee acted under an emergency security authority that I was unaware they'd invoked. It requires only a majority vote of the subcommittee—not the full board—and it doesn't require departmental notification for the initial action." Her voice was level but the underlying temperature was different. Carefully contained heat. "I've filed a procedural objection. The emergency authority is being reviewed."

"What does reviewed mean in practice?" Maya asked.

"It means the board will address the procedural question at its next session. That session is in thirty days."

"Thirty days for a review of whether the subcommittee can run enforcement operations without informing your department," Maya said.

"Yes."

"During which thirty days, they retain the authority to run additional operations."

"Yes." Wells paused. "I'm working to restrict the scope of that authority through alternative channels. I cannot guarantee the outcome." Another pause. "The Rael Vander situation—his subcommittee retainer was not in any system I have access to. It was a classified contract under the emergency security authority the subcommittee invoked. I should have detected it. I didn't."

"We should have taken two days to verify," Maya said.

"Yes. But the subcommittee constructed the scenario specifically to create pressure for a faster decision. Rael's approach at the market, the urgency around the monitoring window—" Wells's voice had the quality of someone describing an operation they found tactically admirable and personally infuriating. "It was well-designed. I'd expect nothing less from the member who chairs the Safety and Oversight subcommittee. He spent fifteen years in field intelligence before moving to regulatory roles."

"Who is he?" Damien asked.

"Director Navar. He's been on the board for twelve years. He voted against my appointment." She said it without bitterness, just information. "He believes multi-class awakeners represent an existential category error in the awakener system, not just a regulatory challenge. He's been building toward this authority for two years."

"He wants elimination, not management."

"He wants a system that cannot produce anomalies he can't classify." Her voice was precise. "That's a different thing from elimination. He'd settle for classification and control. But if classification and control are unavailable—" She left it incomplete. "I'm working within the board structure to limit his scope. The current constraint is that I'm doing it from a compromised position—my department's Field Operations breach is still fresh."

"Voss's mole," Damien said.

"Former mole. But the breach was recent and the board's institutional trust in my judgment is reduced." A long pause. "I want to be clear about something. The procedural protection I'm providing is real. It's also limited by my department's current credibility and the scope of the emergency authority the subcommittee is operating under. I cannot guarantee that a second enforcement operation won't happen before the board review."

"We'll act accordingly," Maya said.

The call ended. Maya sat with the information for thirty seconds—a long time for her, usually.

"We need to move operations," she said. "The subcommittee has confirmed that they can monitor our movement patterns and deploy field teams against us without Wells knowing in advance. That means any location they've observed us using consistently is compromised."

"The warehouse," Tomas said.

"Gareth's warehouse is registered to Gareth. It's not in our operational footprint—the Association knows about the training sessions, but the subcommittee's emergency authority is focused on dungeon operations, not training." She was running through the list. "The food market is compromised—that's how they found Damien for Rael. My apartment has been in the Association's monitoring file since the first debrief. Damien's apartment is too."

"How many safe locations do we actually have?" Nessa asked.

"Three that the subcommittee hasn't observed." She named them. A storage facility in the Fifth District. A contact's private residence in the Sixth. An unregistered commercial space in the Second that Yuki had provided access to four weeks ago. "The food market is the only daily pattern that got them proximity access. We move the routine stops."

It took two hours to update the operational protocols. During those two hours, Damien ran another dungeon.

Not solo. Not off-plan. He sent the check-in texts first, designated his fragment load, confirmed the conflict pairs were accounted for. Maya had asked, during the protocol update, whether the dungeon run was urgent.

"The Kellmore dungeon," he said. "Voss's management transfer was confirmed this morning."

She looked at him.

"The Architecture Mage fragment," he said. "We cleared the dungeon twice and left empty-handed. The entity is no longer hostile. If we run it tonight while the subcommittee is processing the fallout from their Ninth District operation—"

"Tonight's the lowest-probability enforcement window," she said. She was running the calculation visibly. "Go. Full team. I'll run the approach analysis."

---

The Kellmore dungeon was different.

They'd entered twice before and left twice with injuries and no fragment. The third entry was different because the entity inside was different—not enhanced, not hostile, returned to its original classification by Voss's transfer.

A-rank suppression field. But passive. Reduced. The entity wasn't projecting it aggressively. It was maintaining its environmental presence without deploying it as a weapon.

The twelve-corner room on the second floor—the trap room—was still configured as it had been. But the corner nodes were dim. Not charged.

"It's not engaging," Tomas said.

"It can," Damien said. His Geomancer fragment was reading the room's architecture. The structural load capacity was still there. The node charging mechanism was intact. But the entity wasn't using it. "The transfer changed the operational parameters. It still has the ability. It's choosing not to use it."

"Why?"

He thought about the class. Architecture Mage. A class that built. That redesigned spaces. That created environments with intention. The entity had spent six weeks building the Kellmore dungeon into a precision defensive structure.

And now that structure was passive.

Maybe the building was more important than the defending.

He shifted to Bard. The communication attempt from the Tracker Prime had worked—different entity, different class, but the pattern of mana-language communication had been productive before.

He expressed toward the entity what the Tracker Prime's pattern had communicated: *I see you*.

The response was different from the Tracker Prime. The Architecture Mage wasn't a hunter. Its mana language was structural—not movement patterns, but geometry. The response came as a configuration of the twelve-corner room, a subtle rearrangement of the node positions, too small to change the room's defensive function but precise enough to communicate something.

A welcome pattern. The geometry of a door opened.

He walked through the second floor. Through the boss chamber approach. Through the defensive architecture the entity had spent six weeks building.

The entity waited in the center of its architecture. And offered its fragment.

[Fragment 76: Architecture Mage (Legendary-Rare)]

[Retained: Spatial Restructuring +10%, Environmental Intention 10%, Structural Cognition 10%]

Structural Cognition. The ability to understand the purpose behind a constructed space—not just its physical properties, but the intention of whoever built it. Applied to dungeons, to buildings, to any environment that had been designed rather than grown: an understanding of what the builder was trying to achieve.

Applied to people: a form of empathy specific to what they were building.

He stood in the twelve-corner room with seventy-six fragments and the complete architecture the entity had created around him, and he understood, for a moment, what every room he'd ever fought in had been trying to be.

"Seventy-six," he said.

Twenty-four to go.

The room was quiet. The entity's mana dissipated slowly, the way that architectural intention dissipated when the architect was gone—not immediately, but gradually, the purpose fading back into the materials that had expressed it.

They exited clean. No Association vehicles. No Purity Movement presence. The Sixth District evening indifferent and ongoing.

"The conflict map," Maya said, in the car. "The Architecture Mage operates in the structural-spatial layer. Any conflicts with existing fragments?"

"The Geomancer and Earth Mage are structural but physical-layer, not spatial." He checked the pattern. "The Dimension Walker and Space Mage are spatial but dimensional-layer. The Architecture Mage operates at the intersection—" He ran the check as Gareth had taught him, feeling for the interference signatures between the new fragment and its potential conflict partners. "No clean conflicts. Slight interference with Dimension Walker at high simultaneous output. Acceptable."

"Good," she said.

The fragment settled. Twenty-four more. And a conflict map that told him something he should have known from the beginning: having more wasn't the same as being more. The difference between the two was understanding what you actually had.