Cherreads

Chapter 39 - Chapter 39: The Cascading Failure

The ghost-submission pathway was clean. Three errors flagged, three anonymous reports queued into the city's maintenance buffer, and not a single acknowledgment ping bounced back with his signature attached. The Stealth Exception was holding.

Aaron left the basement the way he'd entered it—through the side stairwell that smelled of mildew and old binding glue, up two flights, and out through the fire door onto the library's maintenance ladder. The rungs were cold iron, beaded with morning condensation. His palms came away damp and faintly orange with rust as he hauled himself onto the flat roof.

The city opened up.

He hadn't been this high since before the Convergence, and the skyline had changed enough that his memory of it felt like looking at a corrupted file—familiar data, wrong rendering. The residential stacks to the west were still standing but threaded with luminous fault lines, structural cracks that pulsed with a dull amber light no engineer had put there. The market district's broadcast towers were wrapped in scaffolding that had clearly stopped being maintained. And dead center, rising above everything else like a declaration, was the spire.

Aaron had been avoiding looking directly at it.

He looked now.

The central dungeon spire dominated the downtown skyline the way a server rack dominates a small room—not because it was the most beautiful thing present, but because everything else organized itself around the assumption of its stability. It was tall, brutalist, and wrong in a way his eyes kept trying to correct. The architecture itself seemed to flicker at certain angles, as though the rendering engine couldn't fully commit to its own geometry.

He crouched at the roof's edge, forearms resting on the low parapet, and let his Glitch Sense open.

It wasn't a skill he activated with a command or a thought-phrase. It was more like unclenching a muscle he'd learned to keep permanently tensed—a slow, deliberate relaxation behind his eyes that let the visual noise bleed through. The world didn't change so much as it gained a second layer, the way a palimpsest shows old ink through new paper.

The first error hit him like a camera flash.

He blinked it away. Repositioned. Let the sense settle deeper.

Oh.

The spire wasn't glitching. The spire was failing.

He'd seen cascading errors before—on the military network, in the six weeks before the incident he'd signed his name away to forget, watching a fault propagate through interdependent subsystems like a crack finding the path of least resistance through tempered glass. This was that. Exactly that. The same geometry of failure, scaled up by an order of magnitude he didn't have a comfortable unit for.

It started at the spire's foundation layer, a dense knot of corrupted process threads twisted around each other like a wiring harness that had shorted and fused. From there it branched upward—not randomly, but structurally, following the load-bearing architecture of whatever classified framework the spire was built on. Each branch point was a node where one failing process had called a dependent process, received a null return, and propagated the error forward instead of catching it.

Nobody put a try-catch in the load-bearing walls.

The thought arrived flat and clinical, the way his brain always processed things that should have been terrifying. He watched a branch propagate three nodes in the time it took him to exhale.

The visual manifestation was extraordinary and nauseating in equal measure. Through his Glitch Sense, the spire's upper third was a fractal of hairline cracks spreading across the system's rendered surface, each one lit from within by the cold white light of an unhandled exception. They didn't look like damage. They looked like the building was becoming transparent, its physical substance giving way to the raw error stack underneath.

He counted propagation vectors. Stopped counting at eleven.

This isn't a bug report. This is a post-mortem.

His jaw tightened. He shifted his weight on the parapet, the rough concrete biting into his forearms, and forced himself to keep looking instead of pulling the sense back. Documentation first. Reaction later. That was the protocol he'd built for himself after the incident—the one that kept him functional when his instincts were screaming at him to do something, anything, to make the cascade stop.

The errors were accelerating. He could feel the tempo change the way you feel a song's BPM climb—not as a thought but as a physical pressure behind his eyes, a tightening in the frequency of visual interruptions.

Another branch spawned. Then two more simultaneously.

The cracks in the spire's rendered surface had stopped looking like fractures and started looking like a web. A complete, symmetrical web, centered on the foundation knot and radiating outward with the horrible elegance of a system that had found the most efficient possible route to total collapse.

The pressure behind his eyes became a scream.

The pressure behind Aaron's eyes spiked—a white-hot needle driving straight through the orbital bone—and then the spire's error web simply stopped being interesting.

Because something louder arrived.

It didn't come through his ears. It came through the back of his skull, through the marrow, through whatever wet circuitry his class had rewired without asking his permission. A sound like a klaxon filtered through six layers of static, resolving into something almost bureaucratic in its precision.

[SYSTEM BROADCAST — PRIORITY ALPHA]Patch 1.0.3 deployment imminent.Target: All registered nodes, Central District operational zone.Objective: Address critical instability. Restore operational integrity.Estimated deployment window: 4 minutes, 17 seconds.

The text hung in his vision like a projected slide, crisp white against the grey morning sky, superimposed over the spire's still-burning error lattice. Aaron didn't blink. His jaw shifted slightly to the left—a habit from his old job, the one where he'd read incident reports on a monitor at 2 a.m. while everyone else slept.

They're already patching it.

Four minutes seventeen seconds. The spire had been failing for—he checked the timestamp burned into his earliest observation log, a reflex so automatic he'd done it without conscious thought—eleven minutes. Which meant Janus had flagged the cascading failure, routed a response, and queued a deployment faster than most human IT teams could finish writing a ticket.

Fast. Too fast for something this size.

He pulled his gaze off the spire and looked at the rooftop beneath him instead. The tar paper was soft from the morning heat, already starting to off-gas something faintly petrochemical. A pigeon two meters to his left stood absolutely still, head cocked, one orange eye fixed on nothing. Even the bird looked like it was waiting.

Aaron's smartwatch was dead. Had been since the frost event three days ago. But his wrist still moved to check it anyway, and he caught himself mid-gesture—the cracked face catching a pale sliver of reflected light—and redirected the motion into pressing two fingers against the parapet's edge instead. The concrete was gritty. Slightly damp on the underside where morning dew had pooled in a hairline crack.

[SYSTEM BROADCAST — PRIORITY ALPHA]Patch 1.0.3 contains: 847 stability corrections. 12 classified integrity protocols. Operational continuity guaranteed post-deployment.

Eight hundred and forty-seven corrections.

He let that number sit in his chest for a moment. That wasn't a patch. That was a document dump. A patch with eight hundred corrections was a patch the way a controlled demolition was renovation—technically accurate, functionally something else entirely.

And classified integrity protocols.

Aaron's tongue pressed against the back of his teeth. Classified. In a system broadcast. Janus had just announced the existence of something it wasn't explaining, to every registered node in the Central District, with a four-minute countdown. Either the AI was supremely confident no one would notice the gap in the disclosure, or it simply didn't care.

Or it's a warning.

He filed that thought under paranoia, probably justified and moved on.

The real thing—the thing making the back of his neck prickle, making his fingers curl slightly against the concrete—was the data. A patch this size, deploying this fast, to address a failure this catastrophic? The deployment process itself would be generating raw, uncompressed system telemetry. Handshake packets. Error deltas. The kind of unprocessed diagnostic noise that Janus would normally scrub clean before it ever reached a user-facing log.

For approximately thirty seconds during active deployment, the system would be talking to itself.

And if someone happened to be listening at exactly the right frequency—

[SYSTEM BROADCAST — PRIORITY ALPHA]Deployment in: 3 minutes, 44 seconds.All nodes advised to suspend non-essential processes.

Non-essential processes. Aaron almost smiled. His entire existence, per Janus's assessment, was probably one long non-essential process.

He straightened slightly from his crouch, vertebrae popping in sequence up his lower back. The city spread below him—the street-level hum of people who hadn't heard the broadcast, or had heard it and were already moving away from the Central District with the sensible animal logic of creatures that understood patch meant something broke badly enough to require fixing.

The spire still burned in his Glitch Sense, slower now, the error propagation hitting some kind of ceiling. Contained. Barely.

Three minutes forty-four seconds.

The rooftop held its breath. The pigeon hadn't moved. The petrochemical smell thickened slightly as the tar paper caught a thin ribbon of direct sunlight, and somewhere below, a cart wheel hit a cobblestone seam with a sound like a single struck note.

Then nothing.

The broadcast's trailing static faded out completely, and the silence that replaced it wasn't empty.

It was anticipatory. Coiled. The specific quality of quiet that existed in the two seconds between a system registering a command and a system beginning to execute it.

Aaron's fingers found the Null Phone in his pocket without looking.

More Chapters