The world dissolved.
Not metaphorically, not dramatically — dissolved, like salt in warm water. Webb's apartment, the smell of old paper and burnt coffee, the hum of computers and the warmth of Riven's perpetual flame aura — all of it melted away and was replaced by something Kael's brain struggled to process.
He was standing in a void. But not the empty void of death that he remembered from the end of his first life. This void was full.
Data. Rivers of it. Columns and cascades and oceans of luminous information streaming in every direction, branching and merging and splitting like the circulatory system of something incomprehensibly vast. Each stream was a different color — blue for Rift coordinates, gold for hunter stat calculations, red for threat assessments, green for environmental parameters.
The System's core processing. He was inside the machine.
[PARADOX MARK — INVERSION IN PROGRESS]
[Connection Status: Active — Unstable]
[Compass Stabilization: 73%]
[Time Remaining Before Forced Disconnection: 11 minutes 42 seconds]
Eleven minutes. The Compass was buying him time, but not much. Every second inside the System was a second the Architect could track him, counter him, kill him.
Kael moved — or rather, his consciousness moved. There was no body here, no physical form. He was a point of awareness drifting through an architecture of pure information. And the architecture was familiar.
Not because he'd seen it before. Because it followed patterns he recognized from his decade of studying the System's behavior. The Rift generation algorithms. The stat allocation formulas. The difficulty scaling mechanics. He'd spent years reverse-engineering these systems through observation. Now he was seeing the source code.
And it was beautiful. In a terrifying, alien way, it was the most elegant thing he'd ever seen. Every variable linked to every other variable in a web of dependencies so complex that no human mind should have been able to comprehend it.
But Kael wasn't just any human. He was SSS-Rank — or had been. His INT stat, even at Level 31, was 56. And inside the System, INT didn't just affect mana. It affected comprehension.
He could read it. Not all of it. Not even a fraction. But enough.
Enough to see the flaw.
The flaw was in the Paradox Protocol.
Elena Vasquez had theorized it. Webb had described it mathematically. Now Kael could see it with his own eyes — or whatever passed for eyes in this datastream existence.
The Paradox Mark was a two-way connection. The System used it to monitor Kael, to adjust difficulty, to send threats. But the connection was symmetric. For every byte of data the System sent to Kael, a byte of data flowed the other direction — from Kael to the System's core.
That return channel was supposed to carry monitoring data: Kael's position, his stats, his emotional state. Telemetry. Passive information that the System consumed and discarded.
But the return channel had no filter.
No firewall. No validation. No security. The System had designed the Paradox Mark to be one of a kind — it had never expected the need to protect against a Regressor who could invert the connection. Previous Regressors had tried and died. The System had never patched the vulnerability because it had never been successfully exploited.
Until now.
Kael reached into the data stream and did something no Regressor had ever done.
He wrote.
Not code — the System's architecture was beyond human programming. But data. Raw, unformatted data, pushed through the return channel into the System's processing core with the force of his entire INT stat behind it.
He didn't try to rewrite the System. He didn't try to destroy it. He did something far more subtle and far more dangerous.
He asked it a question.
[INCOMING DATA — PARADOX CHANNEL]
[Source: KA-001]
[Content: Query — 'What happens when the Architect completes the harvest?']
The System processed the query. It couldn't not process it — the return channel fed directly into core processing, and core processing handled every query it received. That was its function. That was its design.
The answer came not as text or sound, but as a flood of interconnected data that Kael's INT-enhanced mind translated into understanding:
When the harvest was complete — when the System had gathered sufficient human potential energy — the Architect would collapse the dimensional barrier between Earth and the Abyss. Not to release monsters. To absorb Earth's dimension entirely, converting all matter, all energy, all consciousness into fuel for the Architect's dying home dimension.
Not just humanity. The planet. The solar system. Everything within Earth's dimensional radius would cease to exist.
The System wasn't farming humans. It was farming reality.
Kael felt sick in a way that transcended physical sensation. The scope of what he'd learned was staggering. The Architect wasn't just a threat to humanity — it was a threat to existence itself.
But the data dump came with a bonus — unintended, accidental, the consequence of asking the System a question it was compelled to answer honestly.
He saw the harvest's progress bar.
[HARVEST STATUS: 67.3% COMPLETE]
[Estimated Completion: 8 years, 4 months, 12 days]
[Accelerated Estimate (with Paradox interference): 6 years, 7 months]
Eight years. In his first timeline, humanity had been destroyed at the ten-year mark. The harvest had been at approximately 95% when reality collapsed. Now, with the timeline accelerated by Kael's interference, the window was shorter.
Six and a half years to save everything.
And one more piece of data, buried in the harvest calculations like a footnote that the System hadn't meant to reveal:
[CRITICAL VULNERABILITY: Harvest cannot proceed if three Anchor Points are destroyed]
[Anchor Point 1: The Spire (Pacific) — Active]
[Anchor Point 2: The Vault (Vienna) — Dormant]
[Anchor Point 3: The Root (Coordinates Unknown — Deep Abyss)]
Three Anchor Points. Destroy all three, and the harvest stopped. The Architect's plan collapsed.
The Spire. The Vault. The Root.
The first two matched Elena Vasquez's coordinates exactly.
Kael felt a surge of something that was equal parts triumph and terror. He had it — the roadmap to victory. The actual, concrete path to stopping the Architect permanently.
He also had approximately four minutes before the System kicked him out and forty-three minutes before the Anomaly Hunter arrived.
He had one more question.
[Query — KA-001: 'Show me the Anomaly Hunter.']
The System hesitated. For the first time, Kael felt resistance — not from the architecture, but from something behind it. A presence. Vast, cold, and suddenly very aware of the intruder in its veins.
The Architect.
"You should not be here." A voice — not spoken, not heard, but imprinted directly into his consciousness. Ancient. Alien. Furious:
"And yet." Kael's response was instantaneous:
The Architect struck.
Not with a weapon or a monster or a System command. With pure processing power — a tidal wave of data designed to overload Kael's mind, burn out his neural pathways, and reduce his consciousness to static.
The Compass blazed. Its stabilization field absorbed the first wave, deflecting enough of the attack to keep Kael alive. But the Compass was cracking — 73% stability dropping to 60%, 50%, 40% —
In the real world, Kael was dimly aware of Sera screaming, of Riven's fire blazing, of Webb pulling at the Compass. His body was convulsing, blood running from his nose and ears.
He had seconds.
He grabbed one last piece of data — a snapshot of the Anomaly Hunter's specifications, ripped from the System's deployment queue before the Architect could redact it — and severed the connection.
[PARADOX MARK — INVERSION TERMINATED]
[Connection Status: Severed]
[Compass Stability: 12% — Critically Damaged]
[Data Retrieved: Harvest status, Anchor Point locations, Anomaly Hunter specifications]
[The Architect sees you now. It will not forget.]
Kael woke up on Webb's floor with the taste of copper in his mouth and a headache that transcended the concept of pain.
"He's back. He's back! Kael — say something. Say anything." Riven's face hovered above him, golden eyes wide.
"Three... Anchor Points. Spire. Vault. Root. Destroy all three... harvest stops." Kael's voice was a rasp.
"Got it. What else?" Sera was recording. Of course she was recording.
"Anomaly Hunter. Class 2. I have its specs."
He closed his eyes and let the stolen data organize itself in his mind. The Anomaly Hunter — the thing that was now thirty-seven minutes from arriving — had a name.
[Anomaly Hunter — Class 2]
[Designation: Erasure]
[Rank: S]
[HP: 120,000 | ATK: 2,400 | DEF: 1,800]
[Special: Temporal Lock — Prevents regression within 100m radius]
[Special: Paradox Consumption — Absorbs Paradox Mark energy to grow stronger]
[Special: Memory Blade — Attacks using target's own memories as weapons]
[Weakness: ??????]
S-Rank. One hundred twenty thousand HP. Specifically designed to counter Regressors — it could lock temporal mechanics and consume Paradox energy.
And its weakness was redacted. The Architect had caught the data theft in time to scrub that one critical piece of information.
"That thing has more HP than the last three dungeon bosses combined. And it eats Paradox energy? Kael, being near you makes it stronger?" Riven read the stats over Sera's shoulder.
"Yes."
"So the logical thing to do is run. Get as far away as possible and let it chase empty air."
"The Temporal Lock has a 100-meter radius. Once it's deployed, I can't escape. And it'll track the Paradox Mark across any distance. Running just delays the fight — it doesn't prevent it."
"The Compass is at 12% stability. One more heavy use and it shatters. We can't re-enter the System." Webb, who was examining the Compass with trembling hands:
"Then we fight with what we have. Thirty-four minutes. Kael — you said you got the specs. Is there anything in the data that suggests a weakness, even if the file was redacted?" Sera finished typing and looked up.
Kael closed his eyes and replayed the stolen data. The Anomaly Hunter's design was elegant in its cruelty — every ability was tailored to counter a Regressor. Temporal Lock prevented escape. Paradox Consumption turned the Mark into a liability. Memory Blade used trauma as a weapon.
But there was something odd in the design architecture. A gap. Not a weakness — more like an assumption.
"It's designed to fight one person. A lone Regressor. Every ability targets a single entity — the Paradox Mark holder. There's no area-of-effect capability, no multi-target processing, no team combat protocols."
"Because every previous Regressor fought alone." Sera's eyes lit up.
"Exactly. The System designed its Hunter based on historical data — and historically, Regressors didn't have allies. They were solo operators. Paranoid, isolated, fighting the System alone."
"And you're not alone." Riven cracked his knuckles. Flames danced.
"No. I'm not."
Thirty-one minutes.
"Here's what we're going to do." Kael stood up. His legs were shaking. Blood was still drying on his face. The headache was a living thing trying to eat his brain from the inside.
[End of Chapter 16]
Next Chapter: Thirty-one minutes to prepare for an S-Rank Anomaly Hunter. Kael's plan is insane. It might just work.