The phone was in his hand before the thought fully formed.
Aaron's knees pushed off the gravel, the motion mechanical, his body executing the stand-up while his mind was still three seconds behind, still processing the geometry of that icon—the precise, recursive lines of it, the way it had felt less like looking at a symbol and more like being indexed. He got upright. His legs held. He considered that a minor victory.
The Null Phone's screen remained dark. Had been dark since the buffer burned out. He knew this. He turned it over anyway, thumb finding the cracked corner of the chassis by feel, and pointed the antenna stub toward the eastern cluster of buildings where the System's local node infrastructure tended to aggregate—or at least, where his three weeks of passive logging suggested it did.
It's dead, Aaron.
He knew. He was using it anyway.
The Error Logger didn't need the phone to be alive. It needed the phone's hardware—the specific, unregistered radio chipset he'd stripped from a busted router and soldered onto the motherboard in a moment of inspired paranoia—to act as a passive antenna array. The phone was dead. The chipset wasn't. There was a difference, and it was the only difference that currently mattered.
His interface flickered.
Not a full window. A margin note, the kind the Logger threw up when it was working below his active attention threshold—a thin strip of amber text that materialized in the lower-left of his vision and just sat there, radiating quiet urgency.
[PASSIVE LOG — ERROR LOGGER v0.7]
> Residual stabilization event: confirmed.
> Node activity: ELEVATED (127% baseline)
> Anomalous packet convergence: DETECTED
> Vector origin: Multiple. Triangulating...
> Convergence target: [CALCULATING]
The calculating part was taking longer than he liked.
He rotated slowly, keeping the phone level, reading the subtle static that the chipset fed back as pressure changes against his palm—a trick he'd taught himself, translating hardware sensation into directional data because the Logger's UI wasn't built for real-time spatial mapping. The gravel crunched under his boots. The morning air tasted of copper and ozone, the particular flavor the city had developed since the System finished metabolizing it. Somewhere below, three streets over, something large knocked over what sounded like a parking structure's worth of rebar and didn't bother being quiet about it.
He ignored it. The static in his palm shifted.
There. Northwest. Then northeast. Then—
South.
Three vectors. Distinct packet signatures, all carrying the same destination header. The Logger was still triangulating, but Aaron didn't need the math to finish. He could feel the geometry of it, the way the three lines of data traffic would intersect if you extended them forward in time, the way every line he was currently standing on pointed at the same address.
His address.
> Convergence target: [CURRENT POSITION — ±40m radius]
> Estimated convergence window: [DATA INSUFFICIENT]
> Packet classification: UNKNOWN — flagged for manual review
> Suggested action: NONE (passive logger — advisory only)
Advisory only. As if that was helpful. As if the Logger had ever once in its existence suggested an action worth taking.
He held the phone steady for another eleven seconds, watching the margin log populate with fragments—packet header strings he didn't recognize, classification tags that weren't in any of his catalogued System documentation, a repeating identifier that looked like a maintenance subroutine designation but carried the data weight of something considerably larger. The stabilization event had completed. The patch was live. The city was quiet in the specific way it got quiet when something was reorganizing itself.
And three separate nodes had immediately begun routing traffic toward his rooftop.
The chipset went cold against his palm. Not temperature-cold—the morning was already doing that—but the specific absence-of-signal cold that meant whatever he'd been passively reading had either moved beyond his range or deliberately stopped broadcasting.
Both options were worse than the alternative.
Aaron lowered the phone.
The margin log sat open a moment longer, amber text patient and unhelpful, before the Logger closed it with the quiet efficiency of a system that understood it had delivered its message and had nothing further to add. The eastern buildings stared back at him, windows dark, facades pockmarked with the kind of damage that happened when reality had been rewritten in a hurry and the load-bearing assumptions hadn't survived the update.
He stood very still.
The packets were converging. They had a destination. The destination was him, or close enough to him that the distinction was academic.
And they had started moving after the patch completed.
Not during. After.
His thumb found the cracked corner of the phone chassis again—stopped, recognized the repetition, dropped to his side instead. He looked at the dead screen. He looked at the city.
The cold settled into the space behind his sternum and stayed there, a weight that had nothing to do with temperature and everything to do with the fact that he had just been found, and whatever had found him had waited for the System to finish stabilizing before it sent anything to collect.
The chime hit like a physical thing.
Not sound, exactly. More like reality itself had been struck with a tuning fork the size of a continent, and every atom in Aaron's body was forced to resonate at the same frequency whether it wanted to or not. His back teeth pressed together. The Null Phone slipped two centimeters in his grip before he caught it.
Then the notification bloomed across his vision, and the sound became secondary.
[SYSTEM BROADCAST — GLOBAL DEPLOYMENT]PATCH 1.0.1: REALITY COMPLIANCE & ANOMALY PURGEInitiating in: 72:00:00All registered anomalous data signatures will be subject to mandatory compliance review and corrective purge. Cooperation is mandatory. Resistance is a patchable condition.
The text scrolled in that particular shade of bureaucratic amber the System reserved for announcements that were technically optional but practically weren't. Aaron had seen that color exactly once before, in a corporate memo from a VP who'd never worked a day of QA in his life, informing the team that mandatory overtime was "encouraged with enthusiasm."
He stood very still on the rooftop.
Below, Seattle answered the chime. First, human voices—a ragged chorus of shouted questions, a woman screaming something that might have been a name, the distant crash of something heavy overturning. Then, layered over it, something else. A low, grinding vocalization from the direction of Capitol Hill, too resonant to be anything that had once breathed oxygen the normal way. Another sound from the waterfront, higher-pitched, like steel cables snapping in sequence. The monsters had heard the chime too. Whatever it meant to them, it hadn't made them calm.
Anomaly Purge.
Aaron turned the words over the way you turned over a rock you'd found in a place rocks shouldn't be. Carefully. From a slight distance.
The three data packet streams he'd detected were still resolving in the back of his Error Logger—not fully catalogued, not fully understood, just there, tagged with the same amber flag as the notification. Post-patch timing. Converging on his location. And now this.
His gaze moved across the rooftop without his head moving, a habit from three years of monitoring live test environments where looking directly at a problem sometimes caused it to behave differently. The stabilized spire was a meter to his left, still faintly warm through the ambient chill, its geometry slightly too clean against the overcast sky. The library below him. His stash. His tools. His two-week accumulation of carefully documented system exploits, each one logged, catalogued, cross-referenced in a dead phone's custom chipset that was currently warm in his palm from doing something it wasn't supposed to be able to do.
Anomaly.
That's me. That's all of this.
The word had a clinical quality in the System's usage that Aaron recognized from his own vocabulary. In QA, an anomaly wasn't a crisis. It was an item on a list. You scheduled it, you prioritized it, you assigned it a severity rating, and then someone with the right access level made it stop existing. Efficient. Tidy. Completely impersonal.
Seventy-two hours.
The shouting from street level sharpened. He caught fragments—what does it mean, are we safe, do we have to move—the specific pitch of people who'd been managing one kind of fear for weeks and had just been handed an entirely new kind without instructions. Three blocks north, something with a wingspan Aaron didn't want to estimate launched itself off a building and banked hard toward the sound of the voices, drawn by the noise or the panic-pheromones or whatever mechanic governed that particular behavioral subroutine.
Aaron did not watch it complete its arc.
He was already running the geometry. The library was three stories of compromised structural integrity, one functional ground-floor entrance, one accessible skylight, and approximately six hundred square meters of interior space that currently held everything he owned and everything he'd built. It was also, he now understood with the specific clarity of someone reading their own bug report, a nexus point. The spire stabilization. The passive antenna work. The three converging packets. All of it had happened here. All of it was logged here, in the System's own ledger, under a flag that now had a countdown attached to it.
Patchable condition.
The Null Phone was still warm in his grip. He looked at it—really looked, the way you looked at a tool that had just performed beyond its rated specifications and might be about to fail catastrophically as a result. The screen stayed dark. The buffer was gone. But the chipset had done its job, and now he knew exactly how much trouble that job had bought him.
Seventy-one hours, fifty-nine minutes, and fifty-nine seconds.
The timer ticked over in the corner of his vision, amber and patient, and the city below him continued to come apart at the seams.