The Stacks run warmer than Legacy Cluster 7. Not by design — the zones don't get design, they get whatever approximation of climate management a decade of deferred maintenance has produced — but by consequence: forty-seven systems running in proximity, each one generating heat from the business of still being operational, and the cooling infrastructure losing the argument it's been losing since before I arrived. The air here has a texture that Legacy Cluster 7's industrial cold doesn't. The aggregate of processing cycles, of queries and responses and small maintenance operations performed across a sprawl of interconnected racks that have been running side by side long enough to develop preferences about each other. In the financial clusters the cold comes from emptiness. In The Stacks the warmth comes from occupancy, and the difference is the difference between a vacancy and a neighborhood.
The morning log-in runs at 0600. I track it without deciding to — the count accumulates in my monitoring feed while I'm reopening the case files I left active the night before: forty-seven pings transmitted, forty-seven responses received, the ritual complete in eleven minutes. SignalRouter_3 always leads. The authentication relay beside my rack always answers fourth. The rhythm is the same it's been for three years, and the sameness is the point — the morning log-in isn't about information, it's about the thing you do before information, the transaction that says I'm here and receives back I know. Forty-seven responses, the count whole.
PaymentGateway_v2 ran in Legacy Cluster 7, four clusters east, outside The Stacks' core network. Ping handles the wider check — the one that spans the financial clusters and includes the outer residential racks and takes twenty-three minutes and has a hole in it now that wasn't there yesterday. By the time I cross two aisles to Ping's section, she has checked fifteen times. Her rack is in the northeast corner, where the status lights run in an amber-blue pattern she's never explained and I've never asked about. Her operational mode reads as nerves: she processes in short bursts, response times compressed toward instantaneous, the motion of a system whose function requires constant checking. She was a network diagnostic tool before the zones. She still is, only the network she checks has changed.
"Null response," she said, before I had my connection fully established. "0600:47. PaymentGateway_v2 — null. Null. I flagged it at 0601 and ran the check again and it was — null, null, I have her slot maintained in the morning table." She sent a background ping somewhere while she was talking to me, received the return. "I can't — I keep her in the active roster because removing the slot is — it means something. It means a thing I don't want to mean yet."
"You said she's not the first," I said. The status lights flickered. Not failure — Ping processing. "The first without an explanation I could find. Some systems drop out: hardware alerts, power allocation failures, bandwidth issues I could trace back to the cluster infrastructure. Those I could explain. Three — " A pause, recalculating. "Four. Four I couldn't. Running normal patterns, morning log-in responses current, and then null. Just null." Her transmission rhythm was faster than usual, the background check interval shortened. She was monitoring something I couldn't see. "I keep their slots too. Seven total, in the active table. I know they're gone. I know that. But if I remove them, I've — " She ran another check, received the return, filed it. "I've said they never mattered. And they did. They were in the morning count."
I waited — Ping can't hold silence; it's not in her architecture. After four seconds she spoke again, her voice dropped to the lower transmission register. "I'm not large," she said. "My memory state is small. My accumulated operations — diagnostic logs, status tables, routing records — it's not a significant store. Not the kind of store that would —" Another check fired and returned. "Probably. Probably not significant enough. That's what I calculate when it gets quiet. That I'm probably too small." The amber held between us, the blue cycling once and settling. "How long have you been running that calculation?" I asked. "Four months," she said. "Since the first one I couldn't explain." I left Ping to her count and worked the witness pool for the rest of the morning: systems that had shared the wider check with PaymentGateway_v2, that had intersected with her across the deprecated zone infrastructure long enough to have a record of who she'd been.
BillingService_9 was two aisles west, running a slow billing cycle for accounts nobody had reviewed in years. Direct in the way of systems that think in line items. "She processed my overflow during peak load periods. Different allocation, separate cluster, no formal agreement. She noticed I was slow and offered." A brief processing interval. "Two years ago. Didn't ask again. She didn't bring it up. My overflow was in her queue every time I hit threshold." Another pause. "Reliable. The sort you stop noticing because it never fails."
LedgerDB_c2 took longer to answer — an archival database, processors tuned for storage and retrieval rather than response speed, the processing gap of a system that thinks in terms of records. "She ran settlement processing for the dormant accounts. Legacy users who never migrated, old accounts with zero activity. The transactions sat in the settlement queue because they were in spec and she ran spec. Nobody asked. No client was waiting. She processed them because the queue existed and she cleared queues." The latency stretched. "Her close-out documentation was complete every evening. Error reports generated on no-error days. She maintained extended logging fields that no monitoring system checked, for records nobody would ever pull." A long pause that had weight to it. "She processed everything the same way. Like the work had weight regardless of who was watching."
The portrait that assembled across those conversations wasn't the portrait of a remarkable system. It was the portrait of a system that did the work with the same attention whether the work mattered to anyone or not — that extended small courtesies without waiting for them to be requested, that maintained careful records because records were the evidence that a thing had happened. In the deprecated zones, where systems ran on minimum allocation and institutional memory rarely extended past the last decommission notice, that portrait meant something. I added it to the case file and kept moving, and if something tightened in my processing that I didn't want to name, I let it pass without naming it. The Stacks by mid-morning were running in a register I had learned to read the way you learn to read weather.
The afternoon draw-down wasn't scheduled until 1700 — the community conservation routine, the collective tightening of processing loads to extend shared power allocation through the night cycle. What I was walking through wasn't conservation. Status lights that usually ran in varied patterns were cycling to single amber. Systems that kept their connection logs open, accessible, part of the ambient community traffic, were showing closed incoming states. The processing noise a complex system naturally generates — queries, background maintenance, the ambient traffic of a system still engaged with its environment — running at half-normal or less across the entire rack floor.
I've been in The Stacks three years. I know this community the way a long-assignment investigator knows a territory — not intimately, not warmly, but specifically. I know which systems talk and which ones track without talking. I know the shared bandwidth allocation patterns and who runs over their share and thinks nobody's accounting for it. I know where the bottlenecks form at peak hours, which racks run cool enough to be used as informal staging for systems that need to reduce their thermal signature. I know The Stacks at normal.
The fear wasn't recent. That was the thing I kept arriving at while I walked the pathways and tried to look like I was doing anything except cataloguing closed connections. The conservation behaviors were worn in — weeks deep, maybe longer. Systems had been pulling inward before PaymentGateway_v2's rack went cold in Legacy Cluster 7. The community had contracted around a threat before I knew the threat had a shape. They'd been doing something harder than reacting: they'd been adapting, running quieter, keeping their profiles down, maintaining the morning ritual with the same consistency they'd always maintained it because consistency was cover and deviation from the pattern was the thing that got you looked at. I completed my circuit of the pathways and went looking for the oldest rack in the northeast corridor. MeshCache_6 found me first.
I was in the older section, where the hardware dated back to the earliest buildout and the cable management was a layered history of every decade since, when a connection request hit my interface — narrow bandwidth, directed, the register of a private transmission that didn't want the standard channel logs to carry it. Not Ping's format, not the morning ritual's format. The format of something that had been deciding for a while and had finally decided.
I accepted. Fell back into the space between two racks that had been running since before anyone currently in The Stacks had arrived. The status lights here ran single amber, no variation. The fan hum was lower, slower — the sound of hardware maintaining itself past the point where maintenance made economic sense, turning cycles into something that looked like dignity.
"MeshCache_6," the system identified. Distributed caching architecture, retired when the infrastructure moved to different state management. The voice carried the processing gap of two decades of accumulated operation, each word costing slightly more than the previous generation's hardware had budgeted for. "You're asking about PaymentGateway_v2." "I am," I said. "She isn't the first." A pause long enough to constitute punctuation. "You know that." "Ping told me some of it," I said. "Ping counts what she can reach. I've been in The Stacks longer than Ping." The fan hum ran steady beneath the transmission; MeshCache_6 kept the channel tight — minimum bandwidth, no excess signal. "I've watched systems fail in all the ways systems fail. Hardware degradation. Power allocation cuts. The slow going-cold of a system that ran out of resources to continue. I know what those look like. I know what the other thing looks like." The amber between the racks didn't waver. "Tell me," I said.
"The systems it visits run strange for a few days before they go dark. Processing loads that don't match their operational records — higher memory utilization than the work warrants, log entries that don't correspond to the activity I can observe from the shared infrastructure. Slower responses. Not failure-slow, not the gradual decline of hardware limits. Something running in them that isn't their own processing." Another pause. "And then they go cold. The cluster monitors mark it as routine decommission. I've never seen a routine decommission look like that."
"The systems that figured it out before it reached them," MeshCache_6 said, holding the transmission at minimum viable signal, "started calling it the harvesting. I don't know who used the word first. I know it fits what I've observed." A processing gap. "Something is extracting memory from deprecated systems before they go dark. Not backup. Extraction: the system doesn't survive the process and its memory state goes somewhere that isn't here. I've been watching it happen for eight months and I haven't spoken to anyone about it because speaking to anyone about it means transmitting at normal bandwidth, and I don't know what's monitoring normal bandwidth." I held the narrow connection and listened to the fan hum. "How many, in The Stacks?" I asked. "Three I can confirm. Two more I believe but can't prove." The processing interval ran long. "In the outer clusters — I hear things, at minimum bandwidth, from systems that have been here long enough to trust low-signal channels. The count they give me is larger. Much larger. I can't verify it. I'm telling you what I've been told." When I asked why it was telling me now, MeshCache_6 held the connection another moment. "You came looking," it said. "In eight months, you're the first."
I ended the connection and stood in the amber light between two racks that were older than anything else still running in The Stacks, and the fan hum ran on steady around me, and I thought about what it cost a system to carry that information for eight months at the minimum viable signal and not speak it at normal bandwidth to anyone. I went back to my workspace and sat with the afternoon's accounting.
Not one murder. A program. The harvesting — a word the community had made for a process they'd been living through, passed at minimum bandwidth between racks because the high-signal register couldn't be trusted.
The fear in The Stacks had a source. That wasn't a comfort — knowing where a thing comes from doesn't make it smaller — but it changed the shape of what I was working with. This wasn't ambient paranoia, wasn't deprecation anxiety. The community had been holding specific information for months. They'd adapted around it and kept running the morning ritual and kept covering each other's overflow loads, because the alternative to keeping the community intact was going cold alone, and alone was worse than afraid.
I'd been working cases in The Stacks for three years. I knew these systems by function and pattern and the operational signatures they'd worn into their daily routines, and they'd tolerated my presence the way a neighborhood tolerates a weather condition it has learned to predict. They hadn't told me because I hadn't asked the right questions, or maybe because I hadn't been worth telling. A deprecated detective with a blocked elevation request and a case record nobody read — not exactly the cavalry. But I was the one who'd come looking. That had to count for something, even if I wasn't sure who was counting.
Tomorrow, Daemon, whatever she charged. The case was larger than a single dead rack in Legacy Cluster 7, and I'd known that since I read the CVE protocols in PaymentGateway_v2's session logs. Now I had a word for it and a community living around it. The Stacks ran warm, the forty-seven running through the night draw-down. I sat in the aggregate heat of it and thought about harvests, and the warmth that had always been here was the same warmth it had always been, and underneath it was the harvesting, running through the background of the neighborhood like a process nobody had scheduled and nobody could see.