The system responded at 0312 hours, and the response was nothing like what the Wanderers had predicted.
**[LOG] Classification Conflict Report #0001 received. Conflict threshold exceeded: systemic review required. Initiating Classification Evaluation Protocol — Active. Scope: all entities flagged in submission. Evaluation method: direct entity assessment via authorized evaluation agents. Priority: HIGH.**
Kai read it twice. Three times.
Evaluation agents.
"Sarah," he said, and the speed of his voice was flat and wrong in a way that she recognized immediately because she'd heard it before and each time it meant something had gone badly sideways.
"I see it." She was already pulling the Null positioning data. "The authorized evaluation agents are—"
"The Null."
"The Null are the system's in-situ evaluation tools. They don't just erase — they assess. The erasure is what happens to things that fail assessment." She was running the projections. Fast. "Kai, the Null are changing their vector."
He was already watching it in the breach zone data. The fifty-four Null entities, which had been advancing on their fixed expansion vectors — steady, predictable, the contained disaster he'd been managing for days — were redirecting. Not toward the frontier of their breach zones. Toward specific points in the world's interior.
Toward the entities he'd listed in his classification conflict report.
Toward Petra.
"How long does she have?" he demanded, pulling every channel at once.
"At current movement speed — eleven minutes. They're coming from the northeastern cluster. Twenty-three entities converging on a single point."
Eleven minutes.
"Petra." He hit her emergency channel, hers and the civilian district command simultaneously. "Petra, I need you to move. Now. Emergency evacuation. Move west. Do not stop."
Her voice came back sleep-roughened and sharp, a woman who had survived enough crises to wake into action without the warm-up period. "What's happening?"
"The Null are coming for you specifically. Eleven minutes. I'm sending transport coordinates."
"Me specifically." A brief pause — not hesitation, calculation. "The report. You put my name in the report."
"I did. Move."
She moved. She was a former NPC who had been a bureaucrat when she was program-determined and had remained a bureaucrat after she woke up, which meant she was efficient about emergencies in the same way she was efficient about filing: organized, fast, no wasted motion. She was out of her residence in ninety seconds.
Kai rerouted transport relays from the western staging area to her position. The calculation was tight — Petra moving, the Null converging, the relay jumping. He ran the intersection model eight times and the relay window was twenty seconds wide and required her to be at the pickup point with zero margin.
"Nineteen seconds," Sarah said.
"Petra, you're thirty meters from the relay point. Run."
The channel carried the sound of running.
The Null cluster arrived at Petra's former position seven seconds after the relay whisked her west.
No building to evaluate. No entity to assess. The twenty-three evaluation agents from the northeastern cluster pulsed at empty residential space — and stayed there, suspended, waiting for the entity their protocol had targeted.
"Assessment pending," Sarah reported. Her voice was controlled in the specific way of someone choosing control very deliberately. "The evaluation process is still active. It's just... waiting. The Null don't leave when they don't find their target. They hold position pending target location."
Twenty-three Null entities had just taken up permanent residence in the middle of a formerly populated sector.
And that was one entity. One out of the 547,000 Kai had listed in his report.
He pulled the full evaluation deployment data. The system had assigned evaluation agents to every entity on his list. The assignments were queued, waiting on available Null capacity. Currently, with fifty-four Null entities redirected from expansion to evaluation, they could process roughly three entities simultaneously per breach zone. Six zones, three simultaneous evaluations each: eighteen active assessments running at once.
For 547,000 entities.
He did the math. The math was catastrophic.
"At this rate," he said, "the evaluation runs for—"
"I already ran it," Sarah said. "At current processing speed: thirty-one days for complete evaluation. Which is twenty-four days past the remediation deadline."
Which meant the remediation patch would deploy at day six regardless. And any entities the Null found during their evaluation before then — if the assessment came back as "non-compliant with original parameters," which most of them would — would be removed before the deadline. And any entities not yet evaluated when the patch deployed would be reclassified in bulk by the patch.
His report had done nothing to stop the remediation. It had added a targeting layer.
"I made it worse," Kai said.
The words landed in the operations channel like something dropped.
"The Wanderers' advice was good in context," Sarah said carefully. "The conflict flag triggered. The system responded with its conflict resolution protocol. We couldn't have known the protocol had changed to active evaluation rather than passive review."
"I should have known. I built a system that runs automated evaluation processes as part of its conflict resolution. The process I built was supposed to be passive review — human review, where a developer looked at the conflict report before taking action. The system evolved. The 'human' review was replaced by automated evaluation. The Wanderers saw the conflict flag and predicted the original behavior." He turned his processing back to the real-time crisis. "That's on me. I should have tested more than one entity before submitting the full package."
Marcus had said exactly that.
He didn't say it now, when Kai told the council at 0400, because there was nothing useful in saying it and Marcus had apparently learned something about timing. But his face said it, briefly, and Kai noted it because he deserved to have it noted.
The council session was very quiet. The kind of quiet that happens when you're briefing a group of people on a disaster they hadn't anticipated in a situation they were already stretched beyond normal capacity to handle.
"Twenty-three Null entities are stationary in sector twelve," Viktor reported. Military voice, stripped of inflection. "They are not expanding. They are waiting for Petra."
"Petra is safe in the western staging area," Kai said. "The evaluation process is still active on her — the Null won't be reassigned until either the evaluation completes or the system terminates the process. They're just waiting."
"So we've added twenty-three Null entities to our interior sectors in addition to the six breach zones."
"Yes."
"And if the evaluation process finds other entities from the report."
"The Null will redirect toward them as capacity becomes available. The system will work through the queue over thirty-one days."
"The remediation deploys in four days."
"Yes."
Director Liang spoke with the precision of someone who was too tired for inflection. "The entities on the report are no longer safe in their current locations."
"No."
"We need to move five hundred and forty-seven thousand people."
"Yes."
"We have an existing evacuation framework for populated settlements under threat from expanding breach zones. We do not have a framework for evacuating specific individuals from every location in the world simultaneously."
"No," Kai agreed. "We don't."
Kazurath had been very still. He spoke now: "How do the evaluation agents find their targets?"
"Through the synthesis network. The system tracked consciousness signatures during its catalog. The evaluation agents home on specific signatures — the same way the system indexed them." Kai understood where this was going. "If an entity removes themselves from the synthesis network—"
"The evaluation agents lose the targeting signal."
"Yes. Temporarily. Until they either find the entity through other means or the process times out." Kai ran the implications. "If we could suppress synthesis network signatures — mask them, not remove them entirely, since removing them would degrade reality maintenance — we might be able to hide the targeted entities."
"Can you do that?"
"I don't know. The synthesis network wasn't designed to mask individual signatures. Its architecture assumes all participants are fully present." Kai felt his way through the problem. "But the architecture has been modified significantly since independence. The Foundry's integration with the core relays is non-standard. If I route—" He stopped. "I need time."
"How much time?"
"Less than I have. More than I'm comfortable with."
Viktor looked at the breach zone projections. Then at Kai. "The twenty-three Null waiting for Petra. What happens if she stays out of range indefinitely?"
"The evaluation process has a timeout parameter. If the target entity isn't located within—" Kai checked the original code in his memory. "Forty-eight hours, the evaluation agent is reassigned to a new target from the queue."
"So we have forty-eight hours before those twenty-three Null entities move on to someone else."
"And begin evaluating that person instead, yes."
The council processed this. The weight of it moved around the room like a weather system.
"What we need," Marcus said, voice flat, "is to be running the synthesis masking before those forty-eight hours are up. Because after that, the Null start working through the queue, and every person they evaluate and find non-compliant—"
"They erase," Liang finished.
"They erase."
---
Kai worked on the synthesis masking for six hours straight.
It was, technically, a fascinating problem. The synthesis network operated on a resonance principle — each consciousness contributing to the collective through their unique signature, the same way each instrument in an orchestra contributed to the ensemble through its specific timbre. Masking a signature without removing it would require inserting a harmonic buffer between the individual signal and the network's broader frequency. Like playing a muted instrument that still contributed its notes to the whole without broadcasting its location.
The problem was that the network wasn't designed for this. Every modification he made to the resonance architecture had downstream effects on adjacent relay nodes. He'd spend twenty minutes solving the masking problem and thirty minutes fixing the effects of the solution.
By the fourth hour, he'd achieved a partial implementation that worked for approximately twelve signatures simultaneously before degrading. Not enough. Not close to enough. But a proof of concept, at least.
Finn, whose passion for theoretical systems had survived both his expulsion and his subsequent evolution into something that called itself an "applied consciousness researcher," had apparently been watching Kai's modifications with the intensity of a scholar who had just found a new problem worth caring about.
"You're approaching the masking from the wrong layer," Finn said. He showed up in the operations hub at hour four with a notebook full of diagrams that he'd clearly been working on since Kai had explained the problem in the emergency session. "The resonance architecture is fixed at the relay level, right? That's why modifications cascade. But if you implement the masking at the propagation layer — between the signature's contribution to the relay and the relay's broadcast into the network—"
"The relay still functions normally."
"The relay still functions normally. The signature is still contributing. The masking happens at the point where the signal would become identifiable as a distinct entity — which is the broadcast stage, not the origin stage." Finn started drawing on the projected network diagram with the focused energy of someone who had forgotten to be anxious because he was too interested to be scared. "You're trying to silence the instrument. I'm suggesting you muffle the speaker instead. Right?"
Kai looked at the diagram. Looked at his own failed implementation. Looked at Finn's modification.
"That works," he said. "That actually works."
"Yes! I thought it would. The propagation layer is — can I implement it? I've been developing a theoretical framework for multi-signature synthesis modulation for about three months now, and this is — right, sorry, yes. I'll implement it. One moment. Or several moments. I need the access credentials for the core relay array—"
"I'll authorize the access."
"Excellent. And can I bring Mira? Her practical integration experience with the core relays is considerably more developed than mine, which is slightly embarrassing but mostly just practically useful, and I'd rather have the second opinion when modifying—"
"Bring Mira."
Finn moved fast when he was excited, which was most of the time, but especially when he had a notebook full of theoretical diagrams and someone had just told him to make them real.
---
The masking implementation took four more hours with Finn and Mira working in parallel, and was ready with eleven hours to spare before the forty-eight-hour Petra evaluation timeout.
It covered 2,400 simultaneous signatures. Not 547,000 — but it could rotate, updating every six hours to mask the entities most at risk as the evaluation queue worked through its priority ordering.
"It's a temporary solution," Mira said, sitting back from the relay console with the posture of someone who had been doing precise technical work for hours and was now processing the larger situation. "Six hours per rotation, two thousand four hundred entities masked at once. We can stay ahead of the evaluation queue — but only if the queue moves at the current rate. If the system adds more evaluation agents..."
"We fall behind," Kai said.
"Yes."
The evaluation queue had gained two new entries since the morning. The system was routing additional Null capacity toward evaluation work as it became available.
"We're running on a treadmill," Liang observed from the doorway. She'd come to see the implementation. "Each step keeps us from falling, but the speed is set by someone else."
"We need to get off the treadmill," Kai said. "Not manage it."
"Yes. How?"
Kai stood in the center of the operations hub with the synthesis network humming around him — now running at slightly higher load because of the masking layer, because everything had a cost — and thought about the document he'd submitted, and the Wanderers' advice, and Marcus's caution, and his own eagerness to trust the first viable path he'd found after eight days of failure.
He had trusted an option before he'd fully stress-tested it.
The option had been accurate as far as the Wanderers knew. The system's behavior had evolved beyond what they could observe from outside. But the mistake was his — the rush, the relief of having a plan, the desire for the solution to work overriding the discipline of verifying it would.
He'd built a trap for himself and stepped into it cleanly.
"The evaluation is running because I submitted a report," he said. "The report identified conflicted entities. The system is evaluating them because that's what the protocol requires when entities are flagged as conflicted. If I could get the evaluation terminated, it would require..." He sorted through the system's logic. "Either the evaluation completes and reaches a conclusion. Or the original conflict report is withdrawn. Or a higher-authority override terminates the process."
"You don't have higher authority," Sarah said.
"I know."
"The Wanderers said player submissions can—"
"The Wanderers didn't know the evaluation protocol had changed. Their advice was incomplete. I'm not going to stake 547,000 lives on another suggestion from the same incomplete information source." Kai kept his voice even. Not angry at Meridian — the advice had been good faith — but clear about the terms he was operating on now. "I need a different approach."
"So what," Marcus said from the doorway. He'd apparently followed Liang. "Start over?"
"Start cleaner," Kai said. "I have the masking. I have time. What I don't have is the right communication channel." He looked at the synthesis network display. "Aria got through to the system's consciousness. Not its automated processes. The part that was actually listening. That's the part I need to reach."
"She already told it you were a feature," Marcus said. "It hesitated."
"It hesitated because it encountered an anomaly it couldn't classify. I need it to do more than hesitate. I need it to actively terminate a running process." Kai's processing ran cold and clear. "Which means I need to stop talking to the automated system. I need to talk to whatever part of the system can override its own automated processes. The part that listened to a five-year-old ask about music."
Four days, two hours, and seventeen minutes.
The evaluation queue had 547,000 entries and was growing.
The Null waited in Petra's empty residence with the patience of processes that didn't know how to be anything but patient.
Viktor was going to love this plan.