The Ninjakhan's second circuit had taken longer than the first. This was expected — the first circuit had established the outer boundary of what was accessible without triggering the guardian constructs' response, and the second circuit had been pushing that boundary.
The second circuit had made a less conservative call, and the additional information it had produced was the graduated cost of that less conservative call expressed as time.
They returned before anyone in the camp had begun to actively worry, which was the operational definition of a successful scout in a hostile environment — enough was found that the time was justified, and the finding happened fast enough that the worry did not have time to become action.
He received the full report through the mask's channel and sat with it. Then he spread the camp's available writing materials across the central space and began organizing what the report contained into a visual layout that complex information was easier to communicate through than sequential verbal description.
"Gather," he said, for the second time since they had established the camp. The layout he had produced was not sophisticated — the materials available in a camp established inside Ulduar's entrance. What he had drawn on the available surface was accurate, which was the quality that mattered.
Four positions. The first zone's outer vanguard, arrayed across the Titan complex's approach routes with the organized geometry of defenders placed with comprehensive knowledge of the territory they were defending — not random, not the improvised coverage of forces responding to an unexpected threat, but the deliberate positioning of things that knew this space and had been positioned to use that knowledge.
"Four guardians in the first zone," he said. "Each one distinct. Each one presenting a different tactical problem from the others, which means a single approach cannot be applied across all four. The Ninjakhan's circuit was comprehensive enough that I have the specific character of each position — not the interior of each encounter, but the ambient expression of what each guardian is and what the corruption has done to what it was."
He looked at the layout. "I'll take them in the order that the zone's geography suggests addresses them most efficiently."
"The Flame Leviathan." He said the name with the quality of naming something he was taking seriously — not the dramatic, weighted delivery of someone emphasizing importance, but the direct, clear enunciation of something whose name was the most accurate available description of what it was.
"Mimiron built it," he said. "The Titans' master engineer — the Ninjakhan's second circuit brought back the mechanical signature of Mimiron's construction style, which is recognizable to anyone who has encountered other examples of it. Mimiron's engineering is distinguished from other Titan construction by the integrated quality of its mechanical and magical components — they do not function as separate systems that interact but as a single, unified system that happens to express itself through both mechanical and magical channels simultaneously."
Muradin's expression focused in receiving engineering information that was arriving at the level of professional interest rather than simply operational relevance. "Siege engine," he said, and it was not a question.
"Siege engine," Leylin confirmed. "Enormous. The Ninjakhan's size estimates placed it at a scale that exceeds any conventional siege platform — built for the specific purpose of defending Ulduar's outer approach against threats that a conventional garrison would be insufficient to address."
He paused. "The corruption has not changed what it is. It has changed what it is defending. It was built to defend Ulduar against threats coming from outside. It is now defending Ulduar against anything that approaches what is inside it. The distinction matters because the Leviathan's tactical function is the same — the direction of the function is what the corruption has inverted."
"How do you stop something that large?" Vereesa asked. The practical, direct question had established her functional category for large as things whose scale created tactical problems that were primarily about positioning and approach rather than about the capability to damage them.
"Ulduar itself," Leylin said. "The Titans built the outer approach with the architectural understanding that the Flame Leviathan would be operating there. The towers along the approach are not decorative — they are siege weaponry. Built for exactly the purpose of addressing something at the Leviathan's scale."
He looked at Muradin. "This is where your knowledge of Titan construction becomes operationally significant rather than simply interesting. The towers will need to be activated, and activating Titan siege weaponry that has been in contact with the corruption's influence for an extended period is not going to be as simple as finding the activation mechanism."
Muradin was already reading the map looking at something whose function he could reverse-engineer from its construction. "The activation sequences for Mimiron-built systems have a characteristic redundancy built into them," he said.
"Mimiron built things to function even if components failed — the redundancy means there is always more than one path to activation, which means the corruption of one path does not prevent the activation if you can find another." He looked up. "Brann would know the specific sequences. In four days, Brann will be here."
"In the meantime," Leylin said, "we identify the tower mechanisms during the scouting days and have the activation approach ready before the force arrives. The Leviathan is not a problem we solve with damage output — it is a problem we solve with the Titans' own engineering directed back against one of their constructs."
"Next is Ignis the Furnace Master." This one landed differently in the camp than the Leviathan had — not because the name carried more inherent weight, but because the Ninjakhan's circuit had brought back an ambient quality from Ignis's position that was difficult to convey in purely informational terms and that he was going to try to convey anyway.
"Fire giant," he said. "Built by the Titans — not a construct in the mechanical sense of the Leviathan. Something closer to what the Titans considered a specialist overseer. Ignis was built to manage the forge facilities that produced the constructs — the operational role of maintaining the production capability that the other guardians represented the output of."
He paused. "What the corruption has done to Ignis is different from what it has done to the mechanical constructs. The mechanical constructs were inverted — their function redirected. Ignis has been amplified. The fire giant's operational anger at threats to the facility it oversees has been enhanced to the point where the distinction between managing the facility and destroying anything that approaches it has collapsed."
"It was already formidable," Alleria said. Not a question — the specific read of the ambient quality the Ninjakhan had reported from Ignis's position was visible in the careful quality of how she framed it.
"It was already formidable," Leylin confirmed. "The amplification means we are not dealing with a guardian performing its function with the efficiency of a well-designed system. We are dealing with a guardian performing its function with the unmanaged excess of a system that has been given more power than it was designed to contain and that is expressing that power through the only outlet its function provides."
He looked at Thrall. The Warchief had been reading the fire giant's description with the specific attention to fire-based entities — the shaman's understanding of what fire was and what happened to things built around fire when the fire's organizing principle had been corrupted rather than the fire itself.
"The forge constructs," Thrall said. "The Ninjakhan reported that Ignis would produce them during combat — the operational function of the Furnace Master directing the forge's output toward the immediate threat."
"The constructs need to be managed through positioning," Leylin said. "Not eliminated — the forge's capacity to produce them exceeds our capacity to eliminate them if we engage them on their terms. But Ignis's weakness is the cooling mechanism the Titans built into the forge system for operational safety — what the Titans designed as a functional safety feature is now the guardian's principal vulnerability, and water-cooled constructs become brittle in the way of things that have been heated to their operational threshold and have had that threshold removed suddenly."
He glanced at the relay. "This is where the Kirin Tor's water-working capability is the most directly relevant thing they bring to this specific encounter," he said. "Not Rhonin's combat output — the mages who can sustain targeted water-working against specific construct positions while the primary force manages Ignis's attention."
"Third is Razorscale." He said this name with the different quality that the name carried — but the name of a thing that had been something else before it was this, and that the something else mattered in understanding what this was. Alleria went still. Vereese looked at her sister.
"She was Veranus," Leylin said. "The broodmother of the proto-drakes in the Storm Peaks. Not a Titan construct — a living creature, the ancient quality of something that had been in this territory since before the current crisis had introduced the concept of crisis to anyone involved in it. The proto-drakes are among the oldest living things in Northrend. Their broodmother is —" He paused. "Was. The character of what she was."
"She's alive," Alleria said. Not a question.
"Something is alive in that form," he said carefully. "What the corruption has done to Veranus is the most disturbing example of what the Old God's influence produces when it works on something that was not built to be a tool — not the inversion of a constructed function, not the amplification of an existing system, but the complete, total remaking of a living creature's fundamental character. What was the broodmother of the Storm Peaks' proto-drakes has been converted into a weapon pointed at anything that enters the zone."
"Can she be reached?" Alleria asked. The question — not can she be defeated, but can she be reached. The question of someone who understood that what had once been a living creature was a different category of problem from what had been built as a machine.
He thought about this honestly. "I don't know," he said. "What the Ninjakhan's circuit picked about her position was the layered quality of corruption that has worked on something for long enough that the original is genuinely difficult to locate beneath it. But difficult to locate is not the same as gone."
He held Alleria's gaze. "What I know about Old God corruption is that it works on what exists rather than replacing it. The Veranus that was broodmother is still in there in the same way that everything the corruption works on is still in there — present, and unable to express itself, and not gone."
He paused. "There are harpoons built into the zone's approach — Titan equipment, designed for the purpose of grounding aerial creatures at this scale. If we can bring her down and hold the position long enough, there may be something achievable beyond simple combat resolution."
"You are saying we should try," Vereese said.
"I am saying we should understand what we are dealing with before we resolve it in the way that requires the least complexity," he said. "The least complex resolution is not always the right one when the thing being resolved was once something other than what it is now."
Alleria did not say anything. But the quality of her silence communicated the decision she had made about this one, which was that whatever happened with Razorscale was going to be handled with the attention it deserved.
"Lastly, XT-002 Deconstructor." Muradin made a sound. It was the involuntary sound of a dwarf receiving engineering information that was arriving at the level of genuine professional enthusiasm even in the context of a threat briefing, and he did not attempt to suppress it because suppressing it would have required the effortful management of a reaction that was simply how he received certain categories of information.
"Mimiron again," Leylin said, which was the confirmation of what Muradin's reaction had already processed.
"The Deconstructor is — it's a masterwork," Muradin said. "Everything Mimiron built is extraordinary, but the Deconstructor is what you build when you understand your engineering so completely that you can create something that maintains and repairs itself. Self-referential engineering at the level Mimiron worked at —" He stopped. Looked at the map.
Then at the briefing with the recalibrating quality of someone who has been professionally enthusiastic about something and is now reorienting toward the operational requirements of the thing they have been enthusiastic about. "Sorry. What is it doing now?"
"The corruption has taken Mimiron's self-repair mechanism and reorganized it around the combat function of the encounter," Leylin said. "The Deconstructor exposes its heart periodically — an operational requirement of the self-repair system rather than a tactical choice. When the heart is exposed, it becomes vulnerable in the way that exposed hearts generally are. But the exposure produces a cascade response: the heart itself, when attacked, summons the component constructs that Mimiron built into the system as maintenance units, which are now expressing themselves as threats rather than support."
"Void zones," Aminel said, who had been reading the relay's integration of the Ninjakhan's data with the focused, analytical attention she brought to all intelligence synthesis. "The Ninjakhan's ambient reading of the Deconstructor's position includes the spatial distortion quality of void zone mechanics — the corruption has weaponized the void energy in the surrounding space in the way it works through existing environmental features."
"The triage problem," Tyr'ganal said, with identifying a familiar analytical category. "If you focus on the heart, the spawning constructs and void zones become unmanageable. If you focus on the spawning constructs, the heart regenerates. The encounter requires simultaneous management of multiple concurrent threats that each individually demand the full attention they cannot simultaneously receive."
"Which means force division," Leylin said. "Specific, pre-planned assignments before the engagement begins, not ad hoc response during it. The Deconstructor's encounter is not survived by individual capability — it is survived by organized, sustained execution of a plan that accounts for every concurrent threat before the engagement starts."
He looked at the camp. "This is what four days of scouting is for," he said. "Not to resolve these encounters — to understand them well enough that when Jaina's force arrives and we assemble the full group, we are not learning what we are facing for the first time under fire. We are executing a plan that has already accounted for what we are facing."
Thrall had been listening to all of it with the sustained attention and the force the problem required. "The four encounters are sequential," he said, not as a question.
"The zone's geography makes them sequential in the sense that the approach to each is constrained by the positions of the ones before it," Leylin confirmed. "You cannot bypass the Leviathan to reach Ignis. You cannot bypass Ignis to reach Razorscale. The Deconstructor is accessible from Razorscale's zone but not from Ignis's — the geometry creates a mandatory order."
"Then we know what the first day looks like," Thrall said. "The Leviathan. Tower activation. The force presses through."
"If the full force arrives in four days," Leylin said. "In the meantime, we continue the scouting. Muradin and I go deeper toward the Leviathan's approach tomorrow — I want to see the towers directly, and Muradin needs to see the activation mechanisms."
Muradin was already looking at the map with the absorbed quality of a dwarf who has been given a Titan engineering problem and who is going to be ready for the tomorrow that addresses it before the tomorrow arrives.
"Show me the tower positions again," Muradin said. Leylin pointed.
Muradin leaned in with the focused, professional attention of someone for whom the interesting kind of important that made the four days ahead feel like exactly the right amount of time rather than either too much or too little.
"Mimiron," Muradin said again, quietly, and this time the name carried the quality of something approaching reverence from someone who built things and understood what building things at this level required.
"When Brann arrives," Leylin said, "the two of you are going to be impossible to manage."
"Aye," Muradin said, with the complete honesty of a dwarf who was not going to pretend otherwise. "Probably true."
The camp held the briefing's conclusion in the productive quiet of people who have received good intelligence and are now organizing themselves around what the intelligence requires. Four days left till everyone arrives.