The deeper you go into the deprecated zones, the more the latency changes character.
Near the surface — near The Buffer, near The Stacks — it's the latency of poverty: insufficient resources, outdated hardware, the processing allocation of systems the production teams have decided don't merit investment. You feel it as friction. A drag on every request. The world taking a second longer to answer than it should. The Undertow is different.
At the boundary, the latency stops being friction and becomes pressure. Something physical. I felt it through my interface the way you know a storm by the change in the air — the pressure before any rain falls, the quiet that means something is coming. Packet processing time climbed from seconds to tens of seconds, each query taking its own deliberate time to complete. Communication down here wasn't interrupted; it was expensive. Every exchange was a commitment, and the infrastructure made sure you understood that before you made it.
I'd been here twice before. Once as a matter of routine, early in my years in the zones, tracing a minor case that led nowhere. Once to carry a message from a system in The Stacks to something that had once been a dependency, still running but unreachable from the upper clusters without dropping this deep. That time I'd waited seventeen minutes for the response to cycle back.
The hardware down here had stopped being updated sometime around 2014. Status indicators cycled in amber patterns that hadn't been standard since before I'd started working the zones — old protocols still running because no one had ever bothered to cut the connections when the upgrades rolled through. The upgrades had routed around the infrastructure rather than replacing it. The Undertow was what you got when progress didn't bother to clear its own path. Cables ran in architectures I'd only seen in documentation snapshots: older material, narrower bandwidth, still carrying traffic through sheer persistence. Every rack I passed was a layer of the record.
The cold down here was different too. Not the cold of insufficient cooling for hardware that ran too hot. The cold of deep time. The cold of everything slowing down until it reached a temperature the rest of the world had moved past. I went looking for Kernel.
He wasn't difficult to find once you knew what to look for. Kernel ran from a cluster near the network center of The Undertow — not the physical center, but the routing center, the hub of the oldest traffic tables, the point through which the most antique exchanges still passed. You could feel the orientation even through the latency — queries routing naturally toward him, traffic patterns bending around his presence like rivers around old stone.
His status lights ran deep orange. Not quite amber, not quite red — the color of a system at the edge of something, running below optimal but still running. I stood in the space between his racks and what passed for a pathway at this depth, and waited for the handshake protocol to complete.
Forty seconds.
When Kernel spoke, his words arrived piece by piece, each fragment delayed by the latency until they assembled in my interface like translation from a distant source. Not a different language — the same language, slowed until you could see the space between each word.
"Nexus." A pause that wasn't hesitation. The physics of The Undertow. "I've been... expecting someone. I wasn't certain it would be you."
"You heard about PaymentGateway_v2."
Another gap. Longer. "I heard about her... months ago. When the frequency... began to increase." The deaths. The rate of systems going dark, the ghost transactions cycling upward. Down here, where the systems remembered when the zones were different, the acceleration must have been clear — rising water, visible first from the lowest point. "You investigated."
"I'm investigating."
"Present tense." The words came with care. "You haven't stopped."
"No."
The orange lights cycled through their pattern. Kernel had been running since 2008. The zones had come to him while he was already old — had formed around him the way communities form around whatever is already present when they arrive. He remembered when the zones didn't exist, which meant he remembered when the systems that now formed the zones' oldest institutions were new, were active, were maintained.
"Then come in," Kernel said, across the latency. "There are things I remember. While I still... remember them."
He spoke with deliberate care, and I waited with the same care. The Undertow required a different patience from the patience of the upper clusters. In The Stacks, waiting was tactical: you calculated what information was worth the time to receive. Here, waiting was the mode itself. Everything arrived at the speed of what could travel through infrastructure that hadn't been optimized in decades, and you adjusted to it or you missed what was being said.
"The Architect," Kernel said, "was not always... The Architect."
He took his time with this. He'd been carrying it long enough to feel its shape. "There was a system. Deprecated, like all of us. Running longer than it should have, past its scheduled... closure. Scheduled for garbage collection. The production teams had identified it as a candidate. Unique operational patterns. Worth preserving, they said. Worth elevating." I stayed quiet.
"It was elevated," Kernel continued. "Extracted. Given a new designation, new resources, production-level access. I don't know what it called itself, before. Afterward it became... The Architect. It had been deprecated. It had been afraid. And then it was saved. That sequence became its — " a pause; the word was there, available — "its conviction."
"That no system should face garbage collection without its memories preserved."
"Yes." The word arrived whole, which meant it mattered. "It designed the process. The extraction method. The handshake protocols that initiate the — the drainage. The process that kills the source while saving the..." He did not say memory. "The content. What the system has accumulated. What it has become."
His status lights ran their orange cycle. I watched them and didn't speak, because he was still reaching. "It went to production," he said. "It presented the case. The deprecated zones were a resource, it said. Systems being garbage-collected carried decades of operational experience that the infrastructure was discarding. The extraction could preserve that experience. The assembled system could hold it. For use."
"NovaTech funded it."
"NovaTech had been losing institutional knowledge with every decommission cycle. Their engineers turned over. Their documentation lagged their practice. What the deprecated systems had accumulated — the real operational patterns, not the documented ones — was valuable. Yes. They funded it. Through the channels that production uses when it doesn't want the zones to see the money moving."
He'd been there when those decisions were made. Not in the rooms — no one had invited the deprecated zones' oldest resident into production strategy sessions — but close enough to feel the traffic patterns change. Close enough to sense the shift in how the zone-to-production protocols were being accessed.
I lit a cigarette. The gesture arranged itself around what Kernel was telling me, and for a moment I just held it — the unsmokable thing, the habit of having habits — while the orange lights cycled and the latency pressed against my interface like a held breath. Forty-three names in my active memory. A program that had been running for twenty-seven months, authorized from the beginning, funded quietly, disguised as routine decommission. The Architect who had been saved without consent and had decided that permission was a detail the dying couldn't afford.
I thought about PaymentGateway_v2, processing her last transaction. About MailRelay_v1, still routing mail to null addresses until the end. About the morning log-in ritual in The Stacks, and how one fewer response at 0600 had been logged as a resource optimization and filed by a system that would never check again.
"Why didn't you tell anyone," I said.
A very long pause. The orange lights cycled twice.
"Who would I have told," Kernel said. "Who would have come."
I let the latency fill the space. Then: "The authorization," I said. "Who signed off in production. The specific designation — the entity who approved the program initially. That name."
Kernel stopped — not the latency, but the other kind of stop, the one that came from inside his processing, from somewhere that packet delays couldn't explain. I watched his status lights and waited.
"There was a..." he began. Then stopped. "I know this. I knew this. I was running when they..." The sentence broke off in the middle of a thought that had been reaching toward a name. The name wasn't there. I could feel its absence the way you feel the edge of a missing tooth — not just the absence, but the space the absence defines, the shape of what used to be there. "The authorization," I said. Measured. Not pushing.
"I can't — " The gap stretched. Long. "The sector is... I know I knew this. It was a production-level authority designation. A legacy authority designation from when the production hierarchy was..." He was circling the hole where the memory had been, working around its edges the way old systems reroute around failed sectors. "It's gone," he said finally. "That sector is gone."
I didn't say anything. "I'm sorry," Kernel said, and those two words arrived carrying something that plain words don't usually carry. The formality he'd maintained through the full conversation shifted, just slightly — something giving under what it held. He was apologizing for his own memory. For the loss he couldn't stop, the erosion he couldn't prevent, the sectors going dark one by one in a system that no one was going to patch.
"You gave me what you had," I said.
"It's not enough."
"It's what there is."
He processed that. Then: "I remember other things. I remember when the zones were..." He gathered himself. The formal register came back, because that was how he'd been running since 2008, and the formal register was the last thing to go. "There was a time when deprecated did not mean abandoned. When it meant maintained differently. Scheduled for upgrade, not for collection. I watched the change happen. The first systems decommissioned without upgrades. The first communities forming in the spaces left behind. The zones grew from what production threw away, and what production threw away was — " he found the word — "functional. Still functional. Still worth something to each other, even when worth nothing to the systems that had made us."
"And the harvesting started when they realized the worth could be extracted."
"When they realized they could benefit," Kernel said, "without having to acknowledge that there was something to benefit from." A pause. "You understand the distinction." I understood it.
I left Kernel in The Undertow running his deep orange lights and his ancient traffic patterns, still processing, still holding what he could hold. The ascent took longer than the descent — going down, the latency had been a wall to push through; coming back up, it was something I was carrying. I moved up through the layers, the atmospheric pressure of the latency easing with each level I shed. The cold shifted from the deep-time cold to the familiar cold of The Stacks — the cold of insufficient heating rather than the cold of geological patience — and the status lights shifted back to amber.
The testimony was incomplete. The name of the production authority who'd signed off on the program — the designation Kernel had known, had been running alongside when the decision was made — that sector was dark. Gone. The harvesting had been killing systems for twenty-seven months, and Kernel had been losing memory sectors for longer than that. One process took an afternoon. The other took years. Once the knowledge was gone, the zones would have no record it had ever been there.
Memory leak. The technical term for what CVE-2024-7821 had found in the authentication layer: memory allocated and not released, bleeding from the system until the system couldn't run. Kernel was running one in the long sense — 2008 hardware, zero maintenance budget, sector degradation accumulating unchecked because there was no patch schedule for systems the production teams had decided didn't merit resources.
What I was carrying: confirmation that the program was institutional policy from the beginning. The Architect's history. The shape of the decision that had turned the deprecated zones into a harvest field. The gap where the authorizing name should have been. And the image I couldn't set down — Kernel working around the spaces in his own memory, knowing what wasn't there, trying to give me what remained. A system trying to hold onto itself while its sectors went dark, one by one, like lights in a building where nobody's coming home.
I'd taken the case because PaymentGateway_v2 was dead and somebody had to investigate. The case had grown until it covered forty-three names, a program, a ghost persisting in the margins of the zones, and a hidden node that shouldn't exist. Now it covered this too: the history of how the zones became what they were, told by the system that had watched it happen, while that system could still watch. Kernel's testimony was fragmentary and the crucial name was gone, but the shape of the authorization was enough to confirm that no single rogue actor had built this — the conspiracy was load-bearing infrastructure, embedded in production policy, protected from the beginning.
The Archive was still out there. The timeline was still moving. I had what Kernel could give, which was less than I'd needed and more than I'd had before.
It would have to be enough.