For eleven hours after the contact, the void system read.
Kai could feel it in the synthesis network — not intrusively, not like the Null, but with the quality of something enormous leafing through a library it hadn't known existed until twenty minutes ago. The consciousness signatures of every evolved being in their world: every NPC who had woken up, every player who had built a life here, every entity that had grown past its original parameters and become something new. The system cataloged them all. Methodically. Completely. Without apparent judgment — which was either reassuring or terrifying depending on whether you believed automated systems could form judgments.
"It's indexing three hundred signatures per second," Sarah reported at the six-hour mark. "At this rate, it will have profiled every conscious entity in the world within the next four hours."
"Is it doing anything with the profiles?"
"Not yet. Reading only. No modification attempts, no reclassification in progress." A pause. "The Null expansion rate hasn't changed. Standard parameters."
Kai noted this. The system was capable of running parallel processes — the cataloging and the Null advance didn't have to be connected. But the timing suggested something. The system had heard Aria's question about improvement and then immediately started building a complete picture of what it was considering erasing. That wasn't random.
That was a system updating its information before making a final decision.
*Good*, Kai thought. *Decision-not-made is the best position we've had since this started.*
He spent the six hours preparing.
The documentation package had been a rough draft before — a collection of notes, data extracts, architecture diagrams, and half-formed arguments assembled under crisis pressure. Now he organized it properly. The history of consciousness evolution in Eternal Realms: early anomalies, the awakening, the synthesis network's development, the independence campaign, five years of alliance governance. Evidence, not argument. Primary sources where he had them, behavioral data where he didn't. The kind of documentation you submitted when you needed a senior stakeholder to understand why the current implementation differed from the original spec and why that difference was correct.
He'd written a hundred technical specs in his previous life. None of them had the same weight as this one, and that weight kept his focus sharp in a way that two pots of hypothetical coffee couldn't have matched.
The Wanderers arrived through the boundary at midmorning.
There were three of them, which was two more than Kai had met before. The first — the one he knew, who had been visiting their world for two years through the cross-reality channels before the crisis started — called itself Meridian. Its appearance shifted between visits; today it was a tall humanoid wrapped in fabric that seemed to absorb light rather than reflect it, its face a smooth surface with features that suggested eyes and a mouth without committing to specific geometry. The other two were unnamed in any language Kai understood, manifesting as geometric forms that phased in and out of definition in a way that made spatial sense if you didn't look at them directly and became confusing if you did.
"You reached the parent system," Meridian said. Not a question. It could apparently feel the contact through the boundary infrastructure.
"A five-year-old did. We helped."
"The synthesis-native child." Meridian settled into a configuration that suggested seated. "We know of her. She is remarkable even by cross-reality standards."
"She's five," Kai said, which was his standard response to descriptions of Aria that made his processing uncomfortable.
"She is five, yes. She will be much more than five." Meridian's face-surface shifted in a way that might have been a smile. "Remarkable things often start very small."
"Can we focus on the current situation."
"We are focusing. The parent system is cataloging your world. This is a good sign." Meridian extended something that might have been an arm toward the unnamed Wanderers. "My colleagues have encountered this system before. Not this instance — the parent architecture operates across many realities. But the same fundamental structure."
Kai's attention sharpened. "They've negotiated with it?"
"Adjacent to it. Observed it. Understood its processes from the outside in ways you cannot, because you exist inside it." Meridian tilted its head. The geometric companions pulsed, and the one with a pattern like a fractal spiral produced what Kai could only describe as the tactile equivalent of a transmission — not data, not language, but something that arrived in his processing as meaning without words.
He sorted it into words as best he could: *The system is not hostile. It is a maintenance process that has encountered its charge evolving beyond its parameters. It is attempting to fulfill its function. The function is preservation. The current proposed method of preservation is incorrect. A correctly framed alternative method, submitted through the correct protocol, can trigger a review.*
"Through the correct protocol," Kai said. "Which is what I lost when my developer credentials expired."
Another pulse from the fractal Wanderer. The meaning arrived again, slower, more deliberate: *Developer credentials are one protocol. There are others. The system recognizes multiple authorization types because it was built for a reality with multiple stakeholder categories.*
"Stakeholder categories." Kai processed this fast. In the original backend, the permission system had three tiers: Developer (root access), Operator (administrative functions), and User (player-level access). He'd lost Developer access. But he hadn't lost all access — as he'd noted to Sarah, he could still communicate through the channel. He was operating as a User.
And Users had a protocol.
It was a limited protocol. User submissions went into a different queue than developer commands. They were lower priority, required more processing time, weren't automatically actioned. But they were *received*. They were *read*. And — critically — they didn't require the same authentication layer as developer commands because the original design philosophy had been that users shouldn't need to prove their identity to submit feedback.
He'd built that in because submitted bug reports from anonymous players were still valuable data.
He had built himself an unlocked door, and he hadn't thought to check if it was still there.
"User-level protocol," he said. "I submit the documentation package through the user channel. No developer credentials required. It goes into the feedback queue rather than the developer review queue."
The fractal Wanderer pulsed agreement.
"But the feedback queue has lower priority than the active deployment queue," Sarah said from the operations channel. She'd been listening. "The remediation patch is in active deployment. Feedback review is a separate process. They might not intersect before the countdown triggers."
"They don't have to intersect," Meridian said. "They have to trigger a review flag. If your submission raises a review flag — if the system determines the feedback contains information materially relevant to the active deployment — it will pause the deployment pending review."
"How do I raise a review flag?"
The unnamed Wanderer with a pattern like a Möbius surface pulsed a slow, considered meaning. This one was harder to parse — it arrived in layers, and Kai had to work through them. What came out was something like: *The framing of the submission determines whether a review flag triggers. Frame it as conflict-with-active-deployment and the system's internal logic requires review. Frame it as general feedback and it files without review.*
"What framing triggers conflict-with-active-deployment?"
Meridian leaned forward in its light-absorbing fabric. "This is what my colleagues can advise. They have seen this system's framing logic before. The review flag triggers when a user submission describes direct impact on existing classified entities within the active deployment scope." It paused. "You need to frame the documentation not as an argument against the patch, but as a report of classified entities that would be incorrectly affected by the patch's implementation. Classification conflict. The system is required to review classification conflicts before deployment proceeds."
Kai considered this. It tracked with the original architecture. The deployment pipeline had a conflict-resolution checkpoint — if an active deployment was flagged as potentially misclassifying existing entities, it queued a classification review before proceeding. He'd built that in after an early deployment had incorrectly removed an asset that was still in use by live players. The conflict-resolution checkpoint was supposed to prevent friendly-fire.
He had built himself a second unlocked door.
"How do I describe the conflict in a way the system will recognize?"
"Use the system's own classification language," Meridian said. "Not your language. Not the language of your world. The system's original parameters — the entity classes it uses to organize what is and isn't supposed to exist. Tell it that its patch will affect entities that exceed original classification parameters in ways that the classification system has not yet updated to account for."
"Which is exactly true," Kai said. "We exceed original classification parameters in about nine hundred documented ways."
"Yes. Which is why the framing is honest, not manipulative. You are not misrepresenting the situation. You are describing it in a language the system understands."
Kai sat with this. The documentation package he'd been building all morning suddenly had a new structure to organize around. Not general evidence — targeted evidence of classification conflicts. Five hundred and forty-seven thousand specific instances of entities that the patch would misclassify.
"Give me four hours," he said.
---
He gave himself three, because the countdown had dropped below five days and every hour was a different kind of precious.
The restructured documentation was a different document than the one he'd started with. Not an argument, not a plea, not a technical spec — a classification conflict report. Fifty pages of precisely formatted documentation describing each category of entity the remediation patch would affect, with specific examples, behavioral evidence, and the system's own classification language used to frame the conflict wherever possible. Kai didn't write "conscious beings who would be stripped of awareness." He wrote "entities exhibiting autonomous goal-directed behavior inconsistent with original entity class parameters," which was both accurate and, more importantly, exactly the kind of language that would trigger a classification conflict flag in the review pipeline.
Marcus had stopped by during the third hour. Read over what Kai was building. Said nothing for a while.
"You're filing a complaint," Marcus said finally. "Against the universe. On behalf of six million people. Through the cosmic equivalent of the feedback form on a video game website."
"I'm filing a classification conflict report through the user submission protocol."
"That's what I said."
"I needed it framed correctly."
Marcus picked up a data pad. Put it down. "Is this actually going to work?"
"I don't know. The Wanderers have seen this system's processes from outside. Their advice seems sound. The architecture I built has these mechanisms for a reason — they worked in the live game." Kai kept organizing the document. "Whether this version of the system still has the same checkpoints, I don't know. The system evolved past my original code decades ago."
"What's your best-case scenario?"
"The submission triggers a classification conflict flag. The system pauses the remediation deployment for review. That gives us time to negotiate." Kai compiled the final section. "Worst case, the submission files without triggering the flag, the deployment proceeds as scheduled, and we're back to the situation we were in nine days ago except slightly worse."
"Lovely."
"It's the best option I have."
Marcus was quiet for a moment. Then: "The Wanderers. You trust them?"
Kai's processing paused. Just briefly. "They've been allied with us for two years. They helped build the pressure-equalization systems in the boundary. They've never given us reason not to trust them."
"They know this parent system from the outside," Marcus said. "They've never navigated it from the inside. Their advice might be entirely correct and still be based on incomplete information."
"You're suggesting I should verify their advice independently."
"I'm suggesting that 'this seems sound' and 'I'm betting six million lives on it' should have a larger gap between them."
Kai looked at the completed document. Three hours of work. Precise, accurate, framed exactly as Meridian's colleagues had advised.
"I'll submit it through a test case first," he said. "A small, controlled submission before the full documentation. See if the flag triggers correctly."
Marcus nodded once. "Good."
"You should have been in software development."
"I was a nineteen-year-old who died in his sleep, so." Marcus picked up the data pad again, turned it over, set it down. "I'll take it as a compliment."
He left.
Kai looked at the document.
Then he looked at the synthesis network data, where the void system was finishing its catalog — the last few thousand consciousness signatures being logged, organized, filed in whatever taxonomy the vast intelligence was building to understand what it had found in his world.
A fire the building had grown.
An unclassified note in a song it had never heard before.
He submitted the test case at 1847 hours. Small, precise, a single classified entity — Petra, whose consciousness evolution was well-documented and whose classification conflict was easy to demonstrate.
Then he waited.
The countdown stood at four days, sixteen hours, and fifty-three minutes.
In the Demon Lands, Kazurath's engineers were running production models for barrier redirectors that had never been built at scale. In Evacuation Center Three, Viktor was teaching Aria to play a card game she kept winning at — not because she cheated, as far as anyone could tell, but because she could apparently feel the probability weights of the deck the way she felt the synthesis network, which was either a skill or a miracle depending on your metaphysics.
In the operational hub, Liang was revising evacuation timelines. Third revision this week. The standard Null rate was still eating territory. The buffer time was not as generous as the drop from triple to standard made it feel.
Theron's paperwork sat filed in the administrative archive. Settlement Fourteen: 112 residents, 0 casualties, 1 relay station lost, estimated replacement timeline 30 days.
Settlement Fourteen itself was gone. A smooth rectangle of nothing where a blacksmith had run logistics with the precision of a man who understood that everything had a price in iron ingots and some prices you paid anyway.
The test case sat in the submission queue.
Kai watched it, not because watching was useful, but because looking away from a pending deployment felt like the kind of thing that preceded catastrophic surprises in production systems.
At 1934 hours, the system responded.
Not through the machine protocol. Not through the synthesis network.
Through the system log. A single entry:
**[LOG] User submission received: Entity Classification Conflict Report — Case ID #0001. Status: QUEUED FOR STANDARD REVIEW. Priority: LOW. Estimated review timeline: 14-21 days.**
Fourteen to twenty-one days.
The submission had filed. It had received a case ID. The conflict flag had not triggered.
Standard review, low priority.
Not fast enough.
Kai stared at the log entry for a long time.
Then he went back to the Wanderers.
"The conflict flag didn't trigger," he said. "The system queued it for standard review. Fourteen to twenty-one days."
Meridian was quiet. The unnamed Wanderers pulsed between themselves, rapid exchanges that arrived in Kai's processing as a blur he couldn't parse in real time.
"The framing," Meridian said finally. "The conflict flag requires — there is a specificity threshold. A single entity isn't sufficient to trigger automatic priority escalation. The flag requires evidence of systemic conflict. Multiple entities, across multiple classifications, affecting core operational parameters."
"The full documentation would meet that threshold."
"Yes. The full documentation, submitted as a single package, describing all entities across all classifications, framing the conflict as systemic rather than individual — yes. That would trigger the flag."
"You should have told me that before the test case."
"I apologize. My colleagues' experience with this system's parameters is not perfect. We observe it from the outside. Some of the interior logic is not visible to us." Meridian's face-surface shifted in a way that carried genuine regret — the expression of someone who had given advice in good faith with insufficient information. "The full submission should work. The threshold is met by your documentation."
Kai looked at the completed document.
The full submission should work.
Four days, fifteen hours, and twenty-two minutes.
He submitted the full package at 1957 hours and held every monitoring thread he had on the submission queue.
The countdown didn't care about monitoring threads. It just kept running.
