The probe data took four days to fully analyze.
Sera's team worked in shifts. Three analysts on the behavioral data. Two on the architectural patterns. Park Somi and Chen Wei on the absorbed-species code fragments. Yara on the Null's native architecture.
Nox worked on all of it, because the Compiler let him read dimensional code in a way that no analytical framework could replicate. The probe's five fragments were raw data, unfiltered, captured at the machine-code level of another dimension's architecture. Translating that into something the analysts could work with required his perception and their methodology.
On the second day, Park Somi found something in the absorbed-species patterns that stopped the lab.
"The tactical units aren't just organized," she said. "They're specialized."
She displayed the pattern analysis on the main screen. Seven absorbed-species types, each assigned to a distinct tactical function within the Null's assault formation.
"Type one: boundary dissolution. These patterns are optimized for breaking through dimensional barriers. They match the attack code from the three-point assault's gateway vector."
"Type two: area denial. These patterns spread and hold territory. Once they breach a barrier, they fill the space and prevent the defender from reclosing the breach."
"Type three: targeted destruction. These patterns home in on specific architectural nodes and dismantle them."
She went through all seven. Each one a different weapon, each one built from the biology of a dead species that the Null had consumed and repurposed. A toolkit of invasion assembled from the corpses of civilizations.
"Type three concerns me most," Park Somi said. "Targeted destruction patterns. They home in on specific architectural nodes."
"The bridge's physical anchor," Nox said.
"The bridge's physical anchor. The lease protocol's routing hub. The evolutionary defense's iteration engine. The resonance defense's calibration array. Any critical node in our architecture."
"How do they target?"
"They read the architecture. The patterns contain a scanning function that identifies high-value nodes by analyzing energy flow density. The more energy flowing through a node, the higher priority it becomes."
"The bridge's anchor has the highest energy flow density in the entire defense architecture."
"By a factor of twelve."
The anchor would be the Null's primary target within seconds of a breach. The targeted destruction patterns would home in on it like guided missiles.
"Can we mask the energy flow?" Chen Wei asked. "Reduce the anchor's signature?"
"The anchor IS the energy flow. The bridge functions because dimensional energy routes through that point. Masking it would mean shutting down the bridge."
"Then we defend the anchor specifically."
"We defend everything specifically. The Null's assault formation is designed to dismantle a defense architecture piece by piece. Every layer we protect, they have a pattern designed to counter."
---
On the third day, Yara found something worse.
She'd been deep in the Null's native code -- the underlying architecture that wasn't borrowed from consumed species but was the Null's own. Her Compiler processed dimensional code with an aggressive fluency that sometimes outpaced her judgment but never outpaced her perception. She saw things in the code that took Nox twice as long to find.
"It's been studying us," she said.
She stood at the display wall with the kind of stillness that meant she was angry. Yara was never still unless something had gotten under her skin.
"The probe captured twenty layers of the Null's outer architecture. Layer eighteen is an analysis buffer. A processing space where the Null stores and examines data."
"What kind of data?"
"Our data." She pulled up the fragment. "The three-point attack wasn't just a capability probe. The Null sent scanning functions through each attack vector. While we were busy defending, the Null was reading us."
The analysis buffer contained structured data about the alliance's defense architecture. Not complete. The Null's scanning had been interrupted by the successful defense. But what it had captured was enough to reconstruct a partial map of the bridge's defensive systems.
"It has the evolutionary defense's iteration algorithm," Yara said. "Partial capture. Maybe sixty percent of the full algorithm. Enough to understand how the defense adapts to new patterns."
"If it understands the adaptation algorithm--"
"It can predict how the defense will adapt. Design attack patterns that the evolutionary defense will converge on, then switch to a pattern that exploits the convergence. A feint at the code level."
"An adversarial attack on the machine learning," Sera said. She'd been quiet, reading the data. Now she spoke with the measured precision of someone who'd identified the exact nature of a threat. "The evolutionary defense uses a genetic algorithm. Genetic algorithms are vulnerable to adversarial input. If the attacker knows the fitness function, it can design inputs that cause the algorithm to converge on a local minimum instead of the global optimum."
"In plain language," Chunwei said.
"The Null can trick our defense into adapting in the wrong direction. The defense thinks it's improving. Actually, the Null is leading it into a trap."
"How much of the adaptation algorithm does it have?"
"Sixty percent. Enough to partially predict. Not enough for a complete adversarial model." Yara paused. "But the Null learns fast. If it gets another look during the next attack, it'll complete the capture."
The room processed this. The evolutionary defense -- the first line of defense, the genetic algorithm that had held against every attack so far -- was compromised. Not broken. But the Null understood how it worked and was developing countermeasures.
"What about the resonance defense?" Nox asked.
"Separate capture. Less complete. Maybe thirty percent of the calibration array's logic. The resonance defense is simpler in structure, which makes it harder to exploit -- fewer parameters to manipulate. But the Null is working on it."
"How do you know it's working on it?"
"Because layer eighteen isn't static. The analysis buffer was active when the probe read it. The Null was processing the captured data in real-time. Updating models. Running simulations. It hasn't stopped analyzing us since the three-point attack."
---
On the fourth day, they found the worst thing.
Nox was cross-referencing the Null's analysis buffer with its native code when he noticed a pattern. A specific data structure in the buffer that didn't match the captured defense data. Something else the Null had been studying.
He traced the data structure through three layers of the Null's architecture. What he found made him sit back in his chair and stare at the display for thirty seconds without blinking.
"It knows about the Compiler."
The briefing room went silent.
"Layer seventeen of the Null's outer architecture contains a categorization schema for the entities it has encountered. Species classifications. Dimensional entities. Defense systems. Subsection four of the schema is labeled in the Null's native syntax. Translated, the label reads: 'code-modifying entities.'"
"Code-modifying entities," Park Somi repeated.
"There are two entries. Entry one: the Spirit Plane's central intelligence. The Null has been aware of the central intelligence for millennia. Entry two is new. Added after the three-point attack." He pulled up the translated data. "Entry two: 'human_compiler. Classification: code_editor. Capability: dimensional_architecture_modification. Threat_level: maximum. Priority: primary_target OR primary_asset.'"
Primary target or primary asset.
The Null had identified the Compiler capability. It had classified human Compiler users as the highest-priority entities in the alliance. And it had assigned two possible responses: destroy or capture.
"The Null doesn't just want to break the bridge," Nox said. "It wants to understand the Compiler. A species that can edit dimensional code is either the biggest threat to the Null's expansion or the most valuable tool it could absorb."
"If the Null captured a Compiler user--" Jin Seong started.
"If the Null absorbed a Compiler user's capabilities, it would gain the ability to edit dimensional code from the inside. It could rewrite the Spirit Plane's defense systems. Dismantle the bridge from within. Modify the lease protocol. It could turn every defensive tool we've built into a weapon."
"That's not going to happen," Yara said.
"No. It's not. Because we're going to make sure it can't."
Nox looked at the data one more time. The Null's analysis buffer. Its categorization schema. Its cold, systematic evaluation of everything it had encountered. The Null didn't hate. It didn't fear. It assessed, categorized, and optimized. A system designed for consumption, doing what it was designed to do.
And it had identified the Compiler as the most important variable in the conflict.
---
Nox spent an hour composing a message to Warm Current.
The inter-dimensional relay carried his query through the network. A request for historical data: had the Null ever specifically targeted code-editing capabilities in its previous conflicts? Had it ever attempted to capture rather than destroy?
Warm Current's response arrived in twenty minutes. Fast.
```
SOURCE: node(warm_current) → relay → node(spirit_plane) + entity(nox_renn)
— type: intelligence
— content: "yes. cold_light's dimension contained entities with partial code perception. not editors. readers. the null prioritized their capture. absorbed their perception capability. used it to accelerate its analysis of cold_light's defensive architecture."
— supplemental: "cold_light fell within three major assault cycles after the null absorbed code-perception entities. correlation: strong."
— warning: "the null learns from what it consumes. if it consumes a compiler, it does not merely gain editing capability. it gains understanding of how editing works. of how your defenses are constructed. of how the bridge functions at the code level."
— tone: urgent. fearful.
```
The message confirmed the worst-case scenario. The Null had done this before. It had targeted code-perception entities in Cold Light's dimension, absorbed them, and used their capabilities to dismantle Cold Light's defenses from the inside.
Cold Light had fallen.
If the Null captured a human Compiler, the same strategy would apply. Absorption. Analysis. Dismantlement. The bridge's defenses, written in code that only Compilers understood, would become transparent to the Null. Every defense algorithm. Every protocol. Every weakness.
Nox shared Warm Current's intelligence with Sera. She read it twice. Then closed her notebook and looked at him.
"Protecting the Compiler team is the single highest priority in the defense plan," she said.
"I know."
"Higher than the bridge itself. The bridge can be rebuilt. If the Null absorbs Compiler capability, no rebuilt bridge would hold."
---
That evening, Nox briefed the full team.
The briefing was uncomfortable. He laid out all four days of analysis without softening the conclusions. The specialized tactical units. The captured defense data. The adversarial attack capability against the evolutionary defense. The Null's knowledge of the Compiler.
"Our defenses are partially compromised," he said. "The Null has captured enough data to develop countermeasures against both the evolutionary and resonance defense systems. The predicted assault will deploy those countermeasures along with nine times the three-point attack's energy."
"The four-minute estimate," Sera said.
"Is now optimistic. With adversarial countermeasures against the evolutionary defense, the adaptation algorithm will converge on false solutions. The defense will think it's working while the Null's real attack bypasses it."
"Estimate with countermeasures?"
"Two minutes. Maybe less."
Two minutes. The bridge would hold for two minutes against the Null's full assault with its current defenses.
Mira stood in the back of the room. She'd listened to the entire briefing without speaking. Her new Weavers stood behind her, twelve faces processing the information that the enemy they'd been told to fight understood their defenses and was building counters.
"Two minutes," Mira said. "In the old academy exercises, I used to tell students that any engagement lasting more than two minutes meant you'd failed at positioning. Two minutes is an eternity when someone's trying to kill you."
"This isn't an academy exercise."
"No. It's worse. In academy exercises, the students who failed could try again." She looked at Nox with the expression she'd worn since the day he met her: a woman who'd lost everyone once and would do anything to prevent it happening again. "What do you need?"
"Time. Three weeks to rebuild the defense architecture. New algorithms that the Null hasn't captured. New defense layers it hasn't analyzed. And a way to protect the Compiler team from targeted capture."
"The physical defense is my responsibility. I'll have the perimeter team ready."
"The perimeter team is twelve civilians with three months of training."
"Thirteen," she corrected. "I'm included."
Nox started to argue. Mira's damaged Spirit Core, her D-rank capacity, the risk of putting an instructor with diminished power on the front line.
She read his face. "Don't. I've made my choices. These are my students and this is the line. You build the code defense. I'll build the wall."
Officer Han stood behind her. The retired bus driver with the B-rank barrier. He nodded once. The nod of a man who'd driven the same route for thirty years and understood that reliability was its own form of strength.
"The wall," Han said. "We'll hold it."
Nox looked at the team. The Compilers and analysts who would rebuild the code. The Weavers who would fight the physical battle. Mira's civilians who would stand at the perimeter. All of them looking at the same data, the same numbers, the same two-minute estimate.
None of them talking about whether to fight. Only about how.
"Three weeks," Nox said. "We rebuild everything."
The clock started.
