They started coding at 0530.
Nox and Yara in the Root Directory, side by side in the bounded protocol's shared workspace. Two Compilers operating on the same architecture. The staging area the Spirit Plane had created sat at the bridge's terminus like an empty function waiting to be filled. Beyond it, dimensional space pressed against the boundary -- not hostile, not friendly, just absent. The void between realities, where the rules of the Spirit Plane ended and nothing replaced them.
The Plane's central intelligence hovered at the edges of the workspace. Not interfering. Monitoring. Ready to sever the extension if anything went wrong. A system administrator watching a live deployment with a hand on the kill switch.
"Standard bridge architecture first," Nox said. "We build from what works and modify as we go."
"That won't work and you know it," Yara said.
She was right. He knew it. But starting from the known was how he coded. The systematic approach. Build the foundation, test it, extend it. Twelve years of backend development had wired him to think in layers. Base layer first. Everything else stacked on top.
Yara coded differently. She started from the edge.
"The void doesn't follow Spirit Plane rules," she said. Her Compiler was already probing the dimensional space beyond the staging area, reading the absence of architecture where the bridge's code ended. "Look at this. No energy gradient. No code substrate. No execution environment. It's like trying to run a program without an operating system."
Nox looked. She was right again. The dimensional void was raw potential. Not empty -- empty implied that something should be there and wasn't. The void was pre-architectural. A space that existed before code, before energy patterns, before the structures that made computation possible. Like the blank state of a hard drive before the first format.
"We need to bring our own environment," Nox said.
"Or adapt to not having one."
They argued for six minutes. Nox wanted to extend the Spirit Plane's code substrate into the void, building a pathway that carried its own execution environment. A tunnel with its own atmosphere. Structurally sound. Predictable. Slow.
Yara wanted to write code that ran natively in the void. No substrate. No execution environment. Code that compiled against nothing and produced output through raw dimensional interaction.
"That's not how code works," Nox said.
"That's how code works in your experience. Your experience is twelve years of systems with rules. The void doesn't have rules. Stop trying to bring them."
The Spirit Plane's intelligence shifted in the background. A subtle realignment of processing attention. Listening. Evaluating. The Plane had opinions about the debate but expressed them through resource allocation rather than words -- it made more raw energy available to Yara's workspace, which Nox read as a vote of confidence in her approach.
"Fine," he said. "Hybrid. My architecture for the base connection to the bridge. Your code for the void-facing interface. We build an adapter layer between them."
"An adapter layer." She almost laughed. "You're writing a compatibility shim between reality and nothing."
"I've written worse."
---
The base connection took two hours.
Nox coded it methodically. A structural pathway branching from the bridge's main architecture, routed through the staging area, anchored at both ends with redundant failover connections. If the extension was severed, the bridge side would seal clean. No bleed. No residual access. The Spirit Plane's one-second severance capability built into every joint.
The code was conservative. Over-engineered by peacetime standards. But peacetime standards assumed you weren't building a bridge into hostile territory while a dimension-eating entity constructed its victory in the space you were trying to reach.
Yara watched him work with the particular attention of a colleague who learned through observation even when she'd never admit it.
"Your code is boring," she said.
"My code is reliable."
"Those aren't mutually exclusive. They just happen to coincide in your case."
He ignored her. Needling was how Yara processed stress.
The base connection compiled. Tested. Held. The pathway extended from the bridge into the staging area and terminated at the boundary where Spirit Plane architecture met dimensional void. A dead end. Waiting for Yara's code to punch through the wall.
---
Yara's code was nothing like Nox's.
He watched her build the void-facing interface and felt the specific discomfort of a systematic thinker observing an intuitive one. She didn't plan. She didn't diagram. She wrote code the way a jazz musician played -- riff, test, adjust, riff again. Her Compiler moved through the void's non-architecture with a fluidity that bordered on recklessness.
She wrote a pathway segment. Extended it into the void. It destabilized within three seconds.
"Expected," she said. Deleted the code. Wrote it differently. Extended. Destabilized in five seconds.
"Better." Deleted. Rewrote. Extended. Seven seconds before destabilization.
"The void is rejecting fixed structures," she muttered. "It doesn't want permanent code. It wants..." She trailed off. Her hands moved on the console. The shaking one was steady for the moment, held in place by focus. "It wants code that moves."
"Code that moves."
"Dynamic. Self-modifying. Code that changes its own structure in response to the void's fluctuations. Not a bridge. A river. Something that flows instead of stands."
She built a pathway segment that rewrote itself every 200 milliseconds. The code was alive in a way that the Spirit Plane's architecture wasn't. Not stable. Not fixed. In constant flux, adapting to the void's shifting conditions the way a boat adapted to waves -- not by being rigid but by being flexible enough to move with the water.
The segment held. Five seconds. Ten. Twenty. A minute.
"It holds," she said. The ghost of triumph in her voice.
"It's changing fifty times a second. The computational overhead --"
"Is the Plane's problem. And the Plane is already compensating." She pointed at the energy flow data. The Spirit Plane's intelligence was feeding additional processing power to the self-modifying code, sustaining its constant rewrites the way a river sustained its own current. The Plane understood Yara's approach better than Nox did. A living dimension recognized living code.
Nox swallowed his objections. The systematic developer in him hated self-modifying code with the intensity of a man who'd spent a career debugging other people's clever solutions. Self-modifying code was fragile. Unpredictable. Impossible to test comprehensively because the code you tested wasn't the code that would run.
But it worked. In the void, where fixed structures crumbled, Yara's fluid architecture flowed.
"Build the adapter layer," she said. "Your stable code on the bridge side. My moving code on the void side. The adapter translates between them. You know you want to write a compatibility layer. I can see it in your face."
He did want to write a compatibility layer. It was the one part of this collaboration that fit his skill set perfectly. A translation module between two incompatible systems. He'd written hundreds of them in his old career. APIs that bridged legacy databases to modern frontends. Middleware that converted between protocols. The thankless, essential work of making things talk to each other.
He built the adapter in ninety minutes. Yara's self-modifying void code on one side. His stable bridge architecture on the other. The adapter sat between them and translated in both directions, converting the void's fluid instability into the bridge's rigid stability and back again. Every 200 milliseconds, it read the current state of Yara's code, mapped it to the bridge's fixed parameters, and confirmed the connection.
"Handshake confirmed," he reported. "Bridge to void adapter is functional. Data flows in both directions. Latency is... acceptable."
"Acceptable meaning bad but not fatal."
"Acceptable meaning I've seen worse in production and the system survived."
---
The extension reached into the void at hour nine.
Not far. Twenty meters of dimensional space, measured by the monitoring systems' best approximation of distance in a place where distance was more of a suggestion than a measurement. But twenty meters was enough to see.
Nox and Yara stood at the extension's terminus. Not physically -- their bodies were in the Institute's editing lab, plugged into the bounded protocol's communication interface. But their Compiler perceptions extended through the bridge, through the base connection, through the adapter layer, and into the void.
The void was not empty.
It was absent. The difference was important. Empty meant space with nothing in it. The void was space without the concept of in. No physics. No code substrate. No energy patterns. Just raw dimensional potential, waiting to be shaped by any architecture strong enough to impose itself.
And across that absence, visible through the Compiler's perception like structures seen through fog, were the Null's absorption nodes.
Dark geometries. Fixed installations anchored in the void through methods that Nox's Compiler couldn't fully parse. The nodes looked wrong -- not in the way that Null code always looked wrong, but in a deeper way. They were made from consumed dimensional matter. The architecture of the eighteen civilizations the Null had absorbed, broken down, reconstituted, repurposed. Building material harvested from dead dimensions.
Each node was a condensed processing unit. Roughly spherical, maybe fifteen meters across. Their surfaces were layered with geometric patterns that shifted and reformed in continuous motion. Energy flowed between the patterns -- the consumed spirit energy from the surface constructs, routed through the breaches, fed into the network.
The relays were thinner. Lines of compressed energy connecting node to node, carrying data and power across the void. The network topology was visible from here -- the grid that Yara had first detected, wrapping around the planet's dimensional footprint.
"I count eleven nodes in visual range," Nox said.
"Fourteen," Yara corrected. "Three more behind the primary cluster. Your Compiler is still degraded. I can see further."
"Fourteen nodes. At least thirty relay connections." He read the energy signatures. Each node pulsed with processing activity. Consumed energy being consolidated. Catalogued. Prepared for the final activation. "They're assembling the collection infrastructure. When the network completes, every one of those nodes becomes an intake point. Energy flows in from the Spirit Plane's connection layer, gets processed, and feeds the central accumulator."
"Where's the accumulator?"
"Deeper. I can't see it from here."
The team needed to reach those nodes. Destroy them. Dismantle the network before it completed. And they needed to do it through twenty meters of void that they could barely code a pathway through, against construction-grade infrastructure built from the matter of consumed dimensions.
Yara's self-modifying code rippled around them. The extension held, swaying like a rope bridge in wind that didn't exist, sustained by the Spirit Plane's constant energy feed and the adapter layer's 200-millisecond translation cycle.
"The pathway is stable enough for personnel," Nox said. He ran the structural calculations. Load-bearing capacity. Energy throughput. The extension could sustain human bodies and active Spirit Cores. Not comfortably. Not safely. But functionally.
"Define stable enough," Yara said.
"It won't collapse while people are on it. Probably."
"Inspiring."
---
Sera was waiting when they disengaged from the Root Directory.
She had a topographic display running. The void's non-architecture, rendered in the best approximation the monitoring systems could produce. The absorption nodes glowed red. The relays glowed amber. The extension showed as a thin blue line reaching from the bridge into the void like a finger pointing at the enemy's infrastructure.
"I've been monitoring the node construction in real time," Sera said. "Two new nodes completed while you were building. Thirty-nine total now. The construction rate is accelerating."
"How long?"
"Sixteen days. The estimate keeps shrinking."
Sixteen days. They'd lost two days since the last estimate. The Null was building faster because it had more surface constructs feeding energy, and the dead-code weapons, while effective at killing constructs, hadn't reduced the overall construct population. The breaches were producing new units faster than the Weavers were destroying them.
"The extension is operational," Nox said. "We have access to the void. We can reach the network."
Sera's pen moved. Notes. Calculations. The constant recording that she'd maintained since the day Nox met her. Every data point captured. Every observation logged.
"Then we send a team," she said.
Pang Wei appeared in the doorway. He'd been listening. Of course he'd been listening. Pang Wei's approach to briefings was to arrive before they started and leave after they ended, absorbing information from every angle.
"I have a roster," he said.
He'd been planning the mission before the extension was confirmed. Before the pathway was built. Before the Spirit Plane had agreed. Because Pang Wei planned for capabilities he didn't have yet, so that when the capability arrived, the plan was already there.
Nox looked at the topographic display. The red nodes. The amber relays. The thin blue line of the bridge extension, reaching into the void like a single thread thrown across an abyss.
Inside those nodes, the consumed energy of the Spirit Plane's harvested connections pulsed with stolen life. The network was building. The clock was running. And the pathway was open.
"Brief the team," Nox said. "We go in twelve hours."
