Chapter 13

# Chapter 13

I spent the first four hours of my thirty-six doing the one thing nobody expected from the guy who talked like he mainlined caffeine and sarcasm in equal measure.

I sat still.

Cross-legged on the floor of the rec center's storage room—a concrete box that smelled like chlorine and forgotten dodgeballs—with my cracked tablet propped against a stack of emergency blankets, I let Pattern Recognition run at passive. Not looking for anything specific. Just... listening. The way you listen to a codebase you don't understand yet. You don't start by reading functions. You start by watching the logs. You let the system talk, and you pay attention to what it says when it doesn't think anyone's listening.

The System was talking. Quietly, in the background radiation of its own architecture, it was running processes I'd never seen before. My overlay—glitching through the crack in my screen, half the data rendered in fractal artifacts—showed me fragments. Not patterns, exactly. More like the absence of patterns. Negative space where logic should have been, blank spots in the enforcement grid's metadata that hadn't existed six hours ago.

The System was cleaning house. Redacting its own code before I could read it.

Smart. Terrifyingly smart.

Tom knocked at thirty-two hours remaining. I knew it was Tom because he knocked three times, evenly spaced, like he was testing whether the door met building code.

"Come in."

He entered with a clipboard—an actual physical clipboard, because Tom believed digital tools were one EMP away from being expensive coasters. "Status report on the camp. Water's holding for about five days. Food for three if we ration aggressively. Maya's triaged everyone. Seven people need ongoing care. One kid broke his ankle during the evacuation, and an older woman is having chest pains that Maya says are probably stress-related but she's monitoring."

"And morale?"

"People are scared, Kai. They heard the enforcers. Some of them saw them through the barrier before it sealed. There are rumors circulating that we're trapped."

"We're not trapped. We're in a different zone partition."

"That distinction matters to us. To a sixty-year-old woman who watched a seven-foot robot try to disintegrate her neighbor's house, it's academic."

Fair point. I rubbed my eyes. They burned—Pattern Recognition's passive mode was still Pattern Recognition, and even at minimum power, it was like staring at one of those magic-eye posters for four straight hours. Except instead of a hidden sailboat, I was trying to see the architecture of a god-level operating system that was actively obfuscating itself from me.

"I'll talk to people," I said.

"When?"

"After I figure out whether we're going to survive past Thursday."

Tom adjusted his glasses. "It *is* Thursday."

"Then I should probably hurry."

He didn't laugh. Tom rarely laughed at my jokes, which I respected because it meant he was actually listening to the content instead of the delivery. Most people got distracted by the delivery. Tom heard the panic underneath.

"What are you looking for?" he asked, nodding at the tablet.

"Patterns in the System's restructuring process. If I can understand how it redesigns its enforcement architecture, I can predict what the new version will look like before it goes live. Pre-patch analysis. Find the bugs before they ship."

"Can you do that?"

"I don't know. Nobody's ever tried. Nobody's ever had to, because nobody's ever pissed off the System enough to trigger a full architectural review." I paused. "Until me."

"You sound almost proud."

"I'm terrified. But yeah, a little bit proud. It's a character flaw."

Tom made a note on his clipboard. Probably something like *Kai: still insufferable under pressure*. He left, closing the door with the same measured precision he'd used to open it.

I went back to staring at the void.

---

At twenty-nine hours, Ghost found me.

He didn't knock. He was just suddenly in the room, sitting against the opposite wall with his arms crossed, watching me with that particular brand of patient stillness that made you realize he'd probably been there for several minutes before you noticed. His arm was in a makeshift sling—Maya's orders, no doubt enforced with threats of creative medical malpractice.

"You haven't slept," he said.

"Sleep is a waste of clock cycles."

"Sleep is how your brain consolidates information. You're trying to learn a new system. Your brain needs downtime to process."

"Since when are you a neuroscience expert?"

"Since before the Fracture, I read." He said it the way he said everything—flat, factual, as if the concept of a combat-class reading neuroscience papers was the most normal thing in the world. Maybe it was. I didn't actually know anything about Ghost's life before all this. None of us did. He'd arrived fully formed, like a patch note with no changelog.

"I found something," I said. "Maybe."

He waited. Ghost was the best waiter I'd ever met. He could out-wait a screensaver.

"The System's restructuring process isn't monolithic. It's modular." I pulled up the overlay, angling the tablet so he could see the fractured display. "Look—these blank spots in the metadata. I thought it was redacting its code, hiding patterns from me. But it's not hiding. It's *decoupling*. Breaking its enforcement architecture into independent modules that don't share coordination logic."

"So you can't cascade-exploit them."

"Exactly. What I did at the park—breaking junction boxes to desynchronize the grid—that worked because the grid was a single coordinated system. Break one node, the whole thing stutters. The System figured that out. So now it's building enforcement modules that don't talk to each other. Independent units with independent protocols. No shared grid to exploit."

"That sounds worse."

"It is worse. It's catastrophically worse." I stood up because sitting still while describing catastrophes felt wrong. "A coordinated grid has patterns. Rhythms. Gaps. An uncoordinated swarm doesn't have gaps—it has *chaos*. And chaos is a lot harder to read than order."

Ghost considered this. "Can you read chaos?"

"Pattern Recognition literally requires patterns. It's in the name. It's the only thing in the name."

"Then adapt the skill."

I stared at him. "You can't just *adapt* a System-granted skill. That's like telling your operating system to rewrite its own kernel."

"You've been treating the System like a codebase since day one. Rewriting kernels is what you do."

"I rewrite *other people's* kernels. I've never tried to—" I stopped. The thought was there, fully formed, terrifying in its simplicity. "You're suggesting I debug my own skill."

Ghost said nothing. Which was his way of saying *yes, obviously, I've been waiting for you to catch up*.

"That's insane."

"You've done insane things before. You did four of them in four minutes."

I sat back down. Stood up again. Sat down. My legs couldn't decide what posture was appropriate for contemplating something this stupid.

Debug Pattern Recognition. Not exploit the System's patterns—rewrite my own ability to *perceive* them. If the System was designing enforcement without patterns, then I needed a skill that could read patternlessness. That could find signal in noise. That could look at chaos and see the structure underneath, the way a cryptographer looks at random data and sees the algorithm that generated it.

"That's not how skills work," I said, but I was already pulling up my skill tree on the tablet, already looking at Pattern Recognition's parameters with fresh eyes. "Skills are defined by the System. Granted by the System. Modified by the System through level-ups and class advancement. You don't just—"

"You found bugs in the enforcement grid," Ghost said. "In the System's own infrastructure. If its infrastructure has bugs, why wouldn't its skill architecture?"

I opened my mouth. Closed it. Opened it again.

"I hate that you're right," I said.

"I know."

---

At twenty-six hours, I told Maya what I was planning. This was a tactical error.

"Absolutely not."

"Maya—"

"You want to use Pattern Recognition on *itself*? To find bugs in your own skill? Do you understand what happens when a recursive function doesn't have a base case?"

"Stack overflow."

"In your *brain*, Kai. A stack overflow in your brain. That's not a metaphor. That's not a cute coding analogy. That is your neural pathways overloading because you're trying to run an introspective loop on a system that interfaces directly with your cognitive architecture."

"You don't know that'll happen."

"You don't know it *won't*. And the difference between those two uncertainties is that one of them ends with you drooling on the floor while your prefrontal cortex reboots."

She was pacing. Maya paced when she was scared, which she expressed as anger, which she channeled into walking back and forth so fast she was practically vibrating. Her healing staff cast shifting green shadows on the storage room walls with every turn.

"I can monitor his vitals," Ghost said from his corner. He'd been so still I'd forgotten he was there, which was probably the point.

Maya rounded on him. "You—with your *sling* and your *nine percent HP stunt*—do not get a vote."

"I'm at sixty-one percent."

"That is not the flex you think it is."

I stepped between them, which was physically unwise but conversationally necessary. "Maya. I'm not asking permission. I'm telling you so that if something goes wrong, you're ready."

"If something goes wrong, I can heal physical damage. I can't heal a brain that's turned itself into a feedback loop." She stopped pacing. Looked at me. The anger drained away, leaving something rawer underneath. "Kai. I can't fix *you*. I can fix bones, and blood, and tissue. I can't fix whatever happens if you break the thing that makes you *you*."

The room got very quiet.

"I know," I said. "But in twenty-six hours, the System finishes its restructuring. And after that, the new enforcement architecture goes live, and it will be designed specifically to counter everything I can do. No patterns. No exploits. No gaps. Just chaos and brute force. And those two hundred people out there eating terrible soup? They're relying on me being able to read the System. That's my job. That's my *only* job."

"Your job is to stay alive."

"Those are the same thing."

"They really—"

"Aren't. Yeah. I know." I was getting tired of that particular truth.

Maya closed her eyes. When she opened them, the healer was back online—clinical, focused, professional. "Fine. But I'm in the room. And if I see your HP drop below fifty, or your neural indicators spike past safe thresholds, I'm pulling the plug."

"Deal."

"And afterward, you sleep. Four hours minimum."

"Two."

"Three. Non-negotiable."

"Three." I nodded. "Ghost, you in?"

"I was in before you asked."

"How reassuring."

---

I sat on the floor, legs crossed, tablet in my lap. Maya positioned herself to my left, staff ready, her overlay calibrated to monitor my vitals in real time. Ghost leaned against the wall by the door—not for comfort, but for a sight line. If something came through that door while I was busy rewiring my own brain, he'd deal with it. That was the division of labor: I broke things, Ghost fought things, Maya fixed things.

Simple. Clean. Completely inadequate for what I was about to attempt.

I pulled up Pattern Recognition in my skill interface. Level 4, passive and active modes, with a detection range of roughly two hundred meters and a resolution that degraded with distance and complexity. The skill description was standard System text—clinical, precise, utterly unhelpful.

**PATTERN RECOGNITION (LV. 4)** *Identifies recurring structures, behavioral sequences, and systematic regularities in environmental, mechanical, and digital systems. Accuracy scales with pattern complexity (inverse) and observation duration (proportional).*

I'd read that description a hundred times. But I'd never looked at it the way I looked at enemy code. I'd always treated it as documentation—a description of what the skill *did*. Not as code itself. Not as something with an underlying architecture that could be inspected, analyzed, and exploited.

"Okay," I said. "Here goes nothing."

I activated Pattern Recognition at full power and pointed it inward.

The effect was immediate and violent. My vision went white, then inverted—negative space becoming positive, light becoming dark, the storage room transforming into a wireframe sketch of itself rendered in lines of burning data. My overlay—already fractured—shattered completely, the crack in my screen propagating through the projected interface like ice breaking on a pond.

And underneath the shattered overlay, I saw it.

My own skill, laid bare. Not the description. Not the documentation. The *source*. Lines of logic that weren't code in any language I knew, but followed a structure I could recognize the way you recognize a melody even when it's played on an unfamiliar instrument. Conditional branches. Evaluation loops. Threshold parameters. The architecture of perception itself, reduced to something I could read.

My HP dropped to seventy-two. Maya's hand tightened on her staff.

"I'm fine," I said, though my voice sounded like it was coming from very far away.

"Your neural activity is spiking. Kai—"

"I see it." The words came out reverent. Almost a whisper. "Maya, I can see the skill's architecture. It's got—there are parameters. Tunable parameters. The inverse complexity scaling, the observation duration dependency—those aren't fixed. They're *configurable*. The System set default values, but the architecture supports modification."

"Modification how?"

I was reading as fast as I could, trying to memorize the structure before the recursive loop did what recursive loops do. The skill was scanning itself scanning itself, and each layer of recursion added latency and cognitive load, and I could feel the stack building, Maya's metaphorical stack overflow getting less metaphorical by the second.

But there. Right there. A parameter I'd never noticed because nobody had ever looked at it. Hidden not by obfuscation but by assumption—the assumption that skills were static, read-only, defined by the System and accepted by the user.

**DETECTION MODE: [REGULARITY]**

Regularity. The skill was hardcoded to look for *regularity*. Repeating structures, predictable sequences, consistent behaviors. That was its detection mode. Its default. Its only option.

Except it wasn't. Because right next to that parameter, grayed out, was another option. Not hidden, exactly. More like deprecated. Left in the codebase but never surfaced in the UI. A feature that had been designed, implemented, and then turned off—either because it was dangerous, or because the System didn't want users to find it.

**DETECTION MODE: [ENTROPY]**

I reached for it.

My HP dropped to fifty-one. Maya's staff flared green.

"Kai. That's the line."

"One more second."

"*Now.*"

I toggled the parameter.

The world reorganized itself.

It wasn't dramatic—no flash of light, no cinematic transformation. It was more like putting on glasses for the first time. Everything was the same, but *sharper*. Clearer. And fundamentally different, because I wasn't looking at the world through a filter that searched for order anymore. I was looking at it through a filter that searched for *disorder*. For randomness that wasn't random. For chaos that had fingerprints.

My overlay—the shattered, fractured, glitching mess on my cracked screen—rebuilt itself. Not the same as before. Darker. The lines were red instead of blue, and instead of highlighting patterns, they highlighted *anomalies*. Deviations. The places where the System's attempt at engineered chaos broke down, because true chaos was impossible for a deterministic system to produce.

The System could design enforcement without patterns. But it couldn't design enforcement without a *designer*. And designers leave traces. Choices. Preferences. The entropy of their own decision-making process, embedded in the architecture like fingerprints on glass.

I could see those fingerprints now.

"Oh," I said.

"Oh good or oh bad?" Maya asked.

"Oh *interesting*." I looked at my skill display.

**PATTERN RECOGNITION (LV. 4) — MODIFIED** *Detection Mode: ENTROPY* *Identifies systematic irregularities, engineered randomness, and deterministic chaos signatures in environmental, mechanical, and digital systems.*

"I can read the new architecture," I said. "Not the patterns—the *anti-patterns*. The places where designed chaos fails to be truly chaotic. The System's trying to build something without patterns, but it's using a patterned process to do it. That's a contradiction it can't resolve."

Ghost pushed off the wall. "How long until you can exploit it?"

I checked the countdown. Twenty-five hours and forty-one minutes.

"Ask me in twenty-five hours."

Maya hit me with her staff. Not with healing energy—physically. In the shoulder. It hurt.

"Sleep," she said. "Three hours. Then you can go back to being reckless with your brain."

I wanted to argue. I wanted to keep staring at the new overlay, the red lines and entropy signatures, the beautiful chaos-that-wasn't-chaos that the System was building. But my HP was at fifty-one, my stamina was cratered, and my eyes felt like someone had sandblasted them from the inside.

"Fine. Three hours."

"Ghost, make sure he actually sleeps."

"I'll watch."

"That's creepy."

"Would you prefer I not watch and you don't sleep?"

"...Watch away."

I set the tablet down. The modified overlay continued to run, painting the storage room in red wireframe, highlighting the entropy signatures of everything around me—the inconsistent spacing of blankets on the shelf, the micro-variations in the concrete floor's surface, the slightly irregular rhythm of Ghost's breathing that told me his ribs still hurt more than he'd admit.

The new mode was sensitive. Very sensitive. It was going to take time to calibrate, to learn to filter signal from noise in a detection framework optimized for finding signal *in* noise.

But it worked. It actually worked.

I lay down on a pile of emergency blankets, closed my eyes, and felt the countdown continue behind my eyelids—twenty-five hours, thirty-nine minutes—each second a heartbeat in a System that didn't know yet that I'd just taught myself a new language.

I fell asleep smiling. Which was, all things considered, a stupid thing to do during an apocalypse.

But some bugs are best found by the people crazy enough to look for them in their own source code.

Twenty-five hours, thirty-seven minutes.

The clock kept running. But for the first time since the notification dropped, I wasn't just counting down.

I was compiling.