Chapter 15

# Chapter 15

Ghost brought back four people and a thermos of something that had once been coffee in the same way that a corpse had once been alive.

Ren arrived first, because Ren was always first when computation was involved. She was seventeen, had the social skills of a feral cat, and could parse System notation faster than anyone I'd met—including me, and I was the one with the modified perception skill. She took one look at the whiteboard, said "interesting," and sat cross-legged on the floor with her own tablet like she was settling in for a meditation retreat.

Dex came second. Big guy. Used to be campus security before the Event. Now he was our barrier specialist—class: Fortifier, subclass: something he refused to tell anyone. He looked at the whiteboard like it owed him money.

"It's four in the morning," he said.

"Four-twelve," Ghost corrected.

"That's worse."

Lin was third, half-asleep and dragging her hand along the wall like she needed it for navigation. Sensor class. She could feel System infrastructure the way some people felt weather pressure—a dull ache in her bones when enforcement proximity passed certain thresholds. Right now she was rubbing her left wrist the way you'd rub a bruise.

"They moved closer," she said instead of hello. "While you were napping. Two of the fourteen. Inner ring position."

"How close?"

"Forty-minute walk. Maybe less if they're not maintaining formation." She found a chair that wasn't covered in maps and collapsed into it. "The whole net contracted about three percent since midnight. I can feel it pulling."

Three percent. That ate into our twenty-two hours. I did the math—if the contraction rate was accelerating, we might be looking at eighteen. Maybe sixteen.

"Cool," I said. "Great news to pair with terrible coffee."

The fourth person wasn't a person. Compass—the camp's only AI-class entity, or what the System had categorized as one. It manifested as a shifting geometric shape about the size of a basketball, hovering at eye level and emitting a soft amber glow. Nobody understood what Compass was before the Event. Nobody understood what it was after, either. But it could interface with System architecture in ways that organic minds couldn't, and right now I needed every translator I could get.

"I have reviewed the entropy signature you flagged," Compass said. Its voice was like someone had fed a wind chime through a vocoder. "Your reading is correct. The conditional structure is embedded in enforcement build layer seven. It is not a glitch."

"So the System put it there on purpose."

"On purpose implies intent. I would say it was *placed* there by the same process that built the enforcement net. Whether that constitutes purpose depends on your philosophy of distributed systems."

"My philosophy of distributed systems is that they're annoying," I said. "Can you read the condition?"

Compass pulsed—amber to gold and back. Its version of a frown.

"Partially. The notation uses a recursive self-reference structure I have not previously encountered. The condition references itself. It is, in a literal sense, a riddle that asks you to understand the riddle in order to understand the riddle."

Ren looked up from her tablet. "Bootstrapping problem."

"Exactly," Compass confirmed. "But not unsolvable. The self-reference has an anchor point—a concrete value buried in the recursion. If we can isolate that anchor, the rest of the conditional should unfold."

I turned to the second whiteboard—the one where I'd written my three questions in black marker at four AM. Added a fourth line beneath them:

*Find the anchor.*

"Okay." I set down the terrible coffee and picked up the tablet. The cracked screen painted my hands in red overlay light. "Here's what we know. The System is building a siege—fourteen enforcement modules, closing net, twenty-two hours until impact. Standard suppression protocol for a community-class barrier. But inside the siege architecture, buried in build layer seven, there's a conditional exception. An if-then. If the condition is met, the enforcement net opens. Not breaks—*opens*. Like a door."

"That's insane," Dex said. "Why would the System build an exit into its own siege?"

"Because the System isn't monolithic." This was Ren, not looking up from her tablet, fingers moving across cracked glass. "It's layered. Modular. The enforcement subsystem builds sieges. But the enforcement subsystem isn't the whole System—it's a component. And other components can inject conditions into its build process. Like API hooks."

"Someone hooked into the enforcement build?" Dex looked like he wanted to hit something, which was his default state but more so.

"Something," I corrected. "Not someone. The notation is pure System-native. No human wrote this. But it wasn't the enforcement module either—the signature is different. This came from a higher-level process."

"Or a parallel one," Compass added. "The System's architecture permits lateral injection between modules of equivalent authority. The condition may have been placed by a subsystem that operates at the same level as enforcement but with different objectives."

I let that sink in. The System wasn't a single thing with a single goal. It was a bureaucracy—a massive, distributed, multi-objective bureaucracy that happened to rewrite the laws of physics as a side effect. And bureaucracies, by their nature, had conflicting priorities. One department builds a cage. Another department installs a door. Not because they're enemies—because they're solving different problems with overlapping jurisdiction.

"Ren. The anchor point. How do we find it?"

She held up her tablet. On it was a visualization I didn't recognize—her own skill at work, some kind of notation parser that turned System-native code into something vaguely resembling a dependency graph. The graph was a mess. Branches went everywhere, folded back on themselves, formed loops that should have been impossible in any sane programming paradigm.

"The recursion has seven layers," she said. "Each layer references the one above it and the one below. But layer four—" She tapped a node in the center of the graph. It pulsed green. "Layer four references something external. Something outside the conditional entirely. A value it's importing from elsewhere in the System."

"What value?"

"That's the problem. The reference is obfuscated. Not encrypted—obfuscated. Like someone wrote it in shorthand that only makes sense if you already know what it points to."

I leaned over her shoulder. The overlay painted the graph in red entropy lines—designed structure, deliberate complexity. Not random. Not chaotic. This was someone—some*thing*—being clever on purpose.

"Show me the obfuscated reference."

She zoomed in. The notation was dense, alien—System-native at its most impenetrable. But Entropy mode did what Entropy mode always did: it found the fingerprint. The deviation. The one piece that didn't match the pattern around it.

There. Buried in the obfuscation. A structure I recognized.

"That's a player reference," I said.

Silence.

"A what?" Dex.

"A player reference. The System's internal notation for identifying an Awakened individual. I've seen it before—in my own skill tree, in the architecture of my own class. That—" I pointed at the tiny cluster of symbols "—is how the System writes *person*."

Ren's fingers stopped moving. "The condition requires a specific player?"

"Or a specific player *type*. I can't read enough to tell." I straightened up. My brain was doing the thing again—compiling too fast, connections forming before I could verify them, pattern-matching without peer review. "Compass. Can you resolve a player reference? Match it to something concrete?"

"If I could access the enforcement module's registry, possibly. But the registry is inside the enforcement architecture. Behind the net."

"So we need to get outside the barrier to read the thing that tells us how to get outside the barrier."

"Essentially, yes."

"Fantastic. Another bootstrapping problem."

"Not necessarily." Lin had her eyes closed, but she was speaking clearly—sensing something. "The enforcement modules broadcast. You know that. The ones in the inner ring are close enough that I can feel individual data streams. If the player reference is in their active registry, I might be able to isolate it from the broadcast noise."

I looked at her. She was still rubbing her wrist—the one that ached when enforcement proximity spiked. Using her skill at this range, with the net contracting, would be like sticking your hand into static and trying to grab a specific frequency.

"That would hurt," I said.

"Most useful things do." She opened one eye. "But I'd need to be closer. The broadcast signal degrades over distance. From here, all I get is pressure and direction. To read specific data streams, I'd need to be within—" She calculated. "Three hundred meters of the barrier edge. Inside the dead zone."

The dead zone. The space between our camp's inner perimeter and the barrier itself. We'd cleared it deliberately—no structures, no cover, nothing between us and the walls. If the barrier failed, we wanted to see it coming. But that also meant anyone in the dead zone was exposed. Visible. And close enough to the enforcement net to trigger proximity responses.

"I'll go with her," Ghost said. Not a question. Not an offer. Statement of fact.

"You'll need someone to compile the data in real-time," Ren said. "I can build a capture filter, but it needs to run on Kai's overlay. His Entropy mode is the only thing calibrated for this kind of noise isolation."

So that was three of us in the dead zone. Me, Lin, and Ghost. Close to the barrier. Close to the net. Close to fourteen enforcement modules that had been designed to suppress exactly the kind of skill usage we'd be attempting.

"When?" I asked.

"Dawn," Lin said. "The enforcement broadcast cycles have a low-amplitude window about twenty minutes after local sunrise. Less noise. Cleaner signal. And the net contraction pauses during cycle resets—it'll be the safest window we get."

I checked the overlay clock. Two hours until dawn. Twenty hours and seven minutes until the net closed completely.

"Okay." I turned to the whiteboards. Picked up the marker. On the third board—the one that had been blank all night—I started writing. "Here's the plan. Ghost, Lin, and I go to the dead zone at dawn. Lin reads the enforcement broadcast. I run Entropy mode to isolate the player reference from the noise. Ghost keeps us alive if something notices."

"Something will notice," Ghost said.

"Yeah. Probably." I kept writing. "Ren stays here with Compass. Once we pull the reference data, we transmit it back. Ren parses it against the conditional structure. Compass resolves the self-reference recursion with the concrete anchor."

"And Dex?" Dex asked.

"You keep two hundred people calm while three idiots walk into the dead zone at sunrise."

He grunted. "I hate my job."

"Everyone hates their job. That's how you know it's important." I finished writing and stepped back. The third whiteboard now had a timeline, assignments, and a big circle labeled UNKNOWN RISK at the bottom, because I believed in honest project management.

Ren was already building her capture filter—fingers dancing across her tablet, writing something in a hybrid notation I couldn't follow. Compass hovered beside her, pulsing in rhythmic gold as they collaborated in whatever language an AI-class entity and a teenage prodigy shared.

Ghost checked his weapons. Two knives—one System-enhanced, one mundane steel. He never explained why he carried both. I'd stopped asking.

Lin sat with her eyes closed, doing whatever Sensors did to prepare. Calibrating. Tuning. Turning her pain threshold into a dial she could crank up when the time came.

I stood in front of three whiteboards and let Entropy mode paint the room. Red lines everywhere—probability vectors, outcome branches, risk assessments. The overlay was calculating success rates and I didn't look at the numbers because sometimes ignorance was the only thing that kept you moving forward.

The camp was waking up. I could hear it through the walls—sounds of morning routine asserting itself against existential dread. Somebody was cooking. The smell of rice porridge drifted through the hallway like a ghost of normalcy. Kids were arguing about something. An old man was doing tai chi in the corridor, his movements painting smooth blue lines in my overlay—zero entropy, zero deviation, perfect practiced harmony. The System had given him a skill for it. He'd been doing it for forty years before that.

Maya appeared in the doorway. Her staff glowed faintly—the healing aura she maintained over the camp, a constant low-level drain on her own resources that she never complained about and we all pretended not to notice.

"You're going to do something stupid at dawn," she said. Not a question.

"Moderately stupid. Calculated stupid."

"There's no such thing as calculated stupid, Kai. There's just stupid you've rationalized."

"Okay, but this time the rationalization is really good."

She didn't smile. She studied me the way she studied patients—looking for fractures beneath the surface, the breaks that didn't show on the overlay.

"Your HP is at seventy-eight. Stamina forty-four. If you push Entropy mode at full resolution for more than eighteen minutes, you'll hit cognitive bleed. Twenty-two minutes and you start losing coherence. Twenty-five and I'm carrying you back."

"Noted. Eighteen-minute window."

"Fifteen," she corrected. "You always lose track of time when you're compiling. I'm building in a margin."

"That's—" I wanted to argue. Didn't. She was right. She was always right about the margins. "Fine. Fifteen."

She reached into her pocket and pulled out three small paper talismans—folded, inscribed with her own skill notation in tiny precise characters. Emergency stabilizers. She'd been making them all night instead of sleeping.

"One for each of you. If coherence drops or pain spikes beyond functional, crush it. It'll buy you ninety seconds of clarity." She held them out. "Don't waste them."

I took the talismans. Warm paper, faintly luminous. Maya's work was always warm.

"Thank you."

"Don't thank me. Come back functional." She turned and left. The glow of her staff lingered in the doorway for a moment after she was gone, like an afterimage. Like a promise.

I distributed the talismans. Ghost tucked his inside his jacket without looking at it—he'd used Maya's work before, trusted it implicitly. Lin held hers up to the light, studying the notation with professional interest before sliding it into her sleeve.

Dawn was an hour and forty-three minutes away. The enforcement net was nineteen hours and fifty-one minutes from closure. Somewhere in the System's architecture, a conditional exception waited with a player reference I couldn't yet read, buried in seven layers of recursive self-reference, obfuscated in shorthand that only made sense if you already knew the answer.

Standard Tuesday, honestly.

I sat down with my tablet, opened Entropy mode to passive monitoring, and started running pre-compilation on the capture filter Ren was building. The cracked screen split her code into fragments, but I could read it—clever work, elegant work, the kind of clean logic that made me remember she was seventeen and already better than me at half of this.

Ghost settled into his corner. Lin breathed slowly, rhythmically, building her pain tolerance like a muscle. Compass pulsed and processed. Ren coded. Dex drank terrible coffee and looked at the UNKNOWN RISK circle on the whiteboard with the expression of a man who had seen too many unknown risks resolve into known catastrophes.

Outside, the sky was still dark. But the entropy signatures at the edge of my overlay were shifting—the enforcement modules adjusting their positions for the dawn cycle, the net's topology flickering through reconfiguration states like a screensaver between modes. In nineteen hours, that net would reach critical density and the barrier would fail. Two hundred people would be exposed. Unprotected. Subject to whatever the enforcement modules did to communities that exceeded the System's tolerance thresholds.

I didn't know what that looked like. Nobody did. No community had survived a full enforcement closure to report back.

We weren't going to be the first to find out.

One hour and forty-one minutes to dawn. I compiled faster. The code shaped itself behind my eyes—Entropy mode's dark-red architecture merging with Ren's capture filter, creating something new. Something that could reach through the enforcement broadcast and pull a single reference from the noise.

A name. A type. A key.

Somewhere in the System, a door was waiting. And in ninety-seven minutes, we were going to walk close enough to read what was written on the lock.

The coffee was terrible. The plan was worse. The odds were unkind.

But the marker on the whiteboard was right. Three questions and one instruction:

*What is the condition?*

*Who left the door?*

*What happens when we open it?*

*Find the anchor.*

Dawn was coming. And we'd be ready.

Or we wouldn't, and twenty-two hours from now, none of it would matter anyway.

I've always found deadlines motivating.