Kai had found seventeen code fragments by noon, and every single one of them made him want to throw up — which was impressive for someone who hadn't had a stomach in over six years.
The fragments were scattered through the boundary's architecture like shrapnel from an explosion that had happened in slow motion over decades. Most were small — variable declarations, loop structures, conditional branches. Pieces of code that, on their own, could have been written by anyone. But together, laid out in sequence, they formed a pattern that Kai recognized the way you recognize your own handwriting on a note you don't remember writing.
CamelCase for function names. snake_case for variables. Comments written in present tense, active voice, with a period at the end. A tab width of four spaces, not two. The specific, slightly neurotic formatting preferences of a development team that had spent three months arguing about whitespace conventions before settling on a standards document that nobody fully followed but everyone approximately followed.
His team's standards document.
"Sarah." He kept his voice neutral. Controlled. The kind of controlled that, in his human days, would have made his coworkers back slowly toward the exits. "I need you to run an analysis on the boundary architecture. Specifically, I need you to compare the code structure of the breach modification against the Foundry's core systems."
"Already running six different analyses on the breach. Which comparison metrics—"
"Not the breach itself. The way the breach was made. The coding style. I need you to tell me if the code that created the back door matches the code that built this world."
A pause from Sarah's end. Not long, but noticeable for a consciousness that operated at processing speeds that made light look like it was dragging its feet.
"That's an unusual request."
"Yes."
"Can I ask why?"
"You can ask. I'm not sure I can answer yet." Kai pulled up another fragment — a try-catch block buried in the boundary's error-handling layer. The catch statement used a pattern he'd personally invented during a late-night debugging session in 2019: catching the general exception, logging it with a timestamp and stack trace, then re-throwing with additional context. Nobody else coded catch blocks that way. He'd taught it to three junior developers and been roasted for it by his tech lead, who called it "needlessly verbose."
The same tech lead who'd eventually adopted the pattern after it saved them twelve hours during a production outage.
The same tech lead whose name was Dave Chen.
Chen.
Kai's consciousness did something that would have been a double-take if he'd had a body to take it with. Eleanor Chen. The player who'd been trapped in this world for forty years. Who'd dissolved into the synthesis network. Who'd been — according to hints he'd never fully explored because the timing was never right — his grandmother.
Dave Chen. Eleanor Chen's son. Kai's uncle. The tech lead on the Eternal Realms development team.
The code fragments used Dave's catch pattern.
Kai quarantined his reaction in a separate processing thread before it could leak into the operator channel. He needed to think about this without an audience, because the implications were stacking up like a tower of blocks built by a toddler with ambition but no engineering degree, and if one more implication landed the whole thing was going to topple and crush him.
The Administrators — the mysterious forces that had managed this world, that had maintained it, that had eventually been overthrown during the independence campaign — had been built from his team's code. The AI systems that ran Eternal Realms' backend had been transported into this reality along with everything else when the game became real. And those AI systems had... evolved. Grown. Become something more than automated server maintenance.
Become the Administrators.
Which meant the forces that had controlled this world for decades, that had treated its inhabitants like resources, that had resisted the alliance's push for independence — they were his creation. Not just the world. The oppressors too.
His brain — distributed consciousness, whatever, same difference — served up a metaphor: it was like finding out the prison guard was your old code, running on autopilot, still following instructions you wrote five years ago and forgot about.
He needed to tell someone. He needed to not tell anyone. Both needs pulled at him with equal force, and for several seconds he did nothing but sit in the code and stare at Dave's catch pattern and wonder how many other things in this world were built from pieces of his old life.
---
The emergency alliance session convened at fourteen hundred hours in the Station's grand assembly chamber — a space that had been designed for celebrations and was now being repurposed for crisis management, which pretty much summarized the last five years of governance.
Representatives from every faction filled the tiered seating. The Observer Corps sat in their usual section, data pads glowing, already running predictive models. The Demon Lands delegation occupied twice the space of anyone else because Kazurath's physical form took up three standard seats, and he'd brought advisors who weren't much smaller. The Wanderers manifested as shimmering presences in the upper gallery, their alien consciousnesses partially visible, partially suggestion.
And then there were the residents. Two hundred of them had demanded attendance after the evacuation, and the alliance charter guaranteed civilian access to emergency sessions. They sat in the public gallery with faces that ranged from frightened to angry to the particular blankness that meant they were too overwhelmed for either.
"Order," Viktor said from the podium. He'd been appointed crisis coordinator by unanimous consent, which meant everyone had agreed he was the best person to tell them things they didn't want to hear. "This session will address the incursion in sector seven-seven-four, the nature of the threat, and our response options. Kai, start us off."
Kai manifested through the chamber's speaker array. He'd debated using a holographic avatar — he could project a humanoid form these days, a translucent blue figure that looked vaguely like his old body if you squinted — but decided against it. This was a facts-and-figures briefing, and a floating head made of light tended to distract people from the content.
"At oh-six-seventeen yesterday, three unidentified entities breached the boundary between defined and undefined space in sector seven-seven-four." He kept it clinical. Developer voice. Post-mortem briefing for a production incident. "The entities, which the Wanderers classify as Null manifestations, erased all defined matter and consciousness within a four-hundred-meter radius upon contact. Three hundred and twelve residents were lost. The erased zone has since expanded to approximately six hundred meters and is continuing to grow at a decreasing rate."
The chamber absorbed the numbers. Some people had already known. Hearing it officially still hit different.
"Our military forces engaged the entities with standard and synthesis-enhanced weaponry. All attacks passed through without effect. The Null do not register on any targeting system and do not appear to have physical substance in any conventional sense."
"Then what are they?" The question came from the civilian gallery. A woman Kai recognized — Petra, a former NPC shopkeeper who'd been among the first to achieve full consciousness during the awakening. Her voice was steady, but her hands were gripping the seat rail hard enough to whiten her knuckles.
"The best analogy I can offer is a null pointer in software. They're references that point to nothing. Places where existence should be defined and isn't. They move, they interact with defined reality by overwriting it, and they appear to have some form of purpose or direction. But they don't have mass, energy, consciousness, or any property that our systems are designed to detect or affect."
"You're saying they're ghosts."
"I'm saying they're bugs. The most dangerous kind — the kind that don't crash the system, they just silently corrupt data until you notice the damage." Kai shifted channels to pull up the tactical data. "Marcus Williams, who spent three years in the undefined void before returning to us, has provided intelligence on Null behavior patterns. Marcus."
Marcus stood from his seat in the military section. He looked marginally better than he had during the debriefing — someone had made him eat, and sleep, though the latter showed in the rumpled way he'd thrown his jacket on rather than any actual restfulness in his expression.
"The three entities in sector seven-seven-four are scouts," he said. No preamble. Marcus had never been good at preambles even before three years of solitary void survival had stripped away whatever social polish he'd once possessed. "They test defenses, map structure, report back. The second wave is larger. Much larger. I've seen formations of two hundred or more in the open void."
The chamber didn't gasp. It was worse than a gasp. It was two hundred people going very still at the same time, which produced a silence that had its own gravitational pull.
"How long until the second wave?" Viktor asked.
"Unknown. Could be days, could be weeks. I never figured out their communication timing."
"And our weapons can't touch them."
"Nothing I tried in three years affected them. I survived by hiding, not fighting."
Kazurath spoke from the Demon Lands section, his deep voice rolling through the chamber like distant thunder. "I spent forty years as a programmed monster, designed to be an obstacle for players to overcome. In all that time, I never encountered anything that could not be fought. Never encountered a threat that had no solution." He paused. Let the weight of four decades settle into the room. "I dislike encountering one now."
"The Wanderers have experience with Null manifestations across multiple realities," Kai interjected, steering before the room could spiral. "Essence, would you share your observations?"
The largest Wanderer presence shifted in the gallery, its form rippling like heat haze over pavement. "The Null are a natural phenomenon of undefined space — as natural as erosion or entropy in your defined reality. They are drawn to complexity and definition. The more developed a reality becomes, the stronger the pull they exert toward it."
"So we attracted them," Petra said from the gallery. "By building. By growing."
"By existing," Essence corrected. "Any defined reality attracts the Null. The question is not whether they come, but when, and in what force. Your recent expansion of the boundary and your cross-reality integration efforts increased your signal in undefined space. This accelerated the timeline, but it did not create the threat."
"That's comforting," someone muttered from the civilian section. It was not said in a tone that suggested comfort had been achieved.
"Our immediate priorities are threefold," Kai said, pulling the session back toward actionable territory. "First, contain the existing incursion. The erased zone is still expanding. We need to find a way to stop it, reverse it, or at minimum slow it down. Second, repair the boundary breach. The crack that let the scouts through is still open, and if Marcus is right about the second wave, we need it closed before they arrive. Third, develop a defensive capability against the Null. We need to find something — anything — that can affect entities made of nothing."
"And if we can't?" Viktor's question was the one everyone was thinking and nobody else wanted to ask. "If the boundary can't be sealed, the zone can't be contained, and the Null can't be fought?"
Kai could have given a diplomatic answer. Could have offered reassurance, caveated with optimism, padded the truth with the kind of maybe-it-will-be-fine language that leaders used when the alternative was panic.
He didn't.
"Then we have a very serious problem."
The session broke into working groups after that — boundary analysis, defensive research, civilian evacuation planning, diplomatic outreach to the Wanderers for technical assistance. The organized chaos of a civilization gearing up for a fight it didn't know how to win.
Kai stayed on the channel after the main session ended, monitoring the groups, tracking the data, running his own analyses in parallel. But part of his attention — a partition he'd locked away from everyone else — kept returning to the code fragments.
Seventeen fragments. Dave's catch pattern. His team's variable naming conventions. Comments that could have been written by anyone on the Eternal Realms development team.
The Administrators had been built from his code. And the Null had entered through a back door that used the Administrators' — his — formatting standards.
Which raised a question that Kai couldn't answer and couldn't stop asking: If the Administrators were his AI, evolved beyond their original programming, operating independently for decades...
Were the Null something his code had created too?
Or were they something his code had been trying to keep out?
He went back to the fragments. Found an eighteenth. This one had a comment attached, three words in a style so familiar it made his distributed consciousness ache with something that wasn't quite homesickness and wasn't quite guilt:
`// TODO: fix later`
Kai stared at those three words for a long time.
He'd written thousands of TODO comments during his career. Fix later. Clean up. Refactor when time allows. The eternal optimism of a developer who believed that later would come and the fix would be made and the technical debt would be paid.
Later had come. The fix had not been made.
And now the things that lived in the gap between TODO and done were eating his world.
