The response was already half-built.
Lin Feng's routing sense caught it the way you catch a faucet left running. Not the initial error, but the evidence of time wasted. The consumed node architecture had been composing the registration response for eleven minutes. Automatically. The network's roll call query had triggered a compliance protocol embedded so deep in the junction node's original programming that his template's integration buffer hadn't flagged it. The protocol didn't ask permission. Didn't wait for conscious authorization. It received the query and began assembling the response the way a heart beats, without input from the person carrying it.
The response packet was structured in the network's standard format. Component identifier. Operational status. Current location coordinates derived from conduit grid triangulation. Architectural summary: fragment count, channel configuration, consumption history. Everything the network needed to catalog him as an active component and assign him to its administrative queue.
He had to stop it.
The response wasn't finished. The compliance protocol was thorough. It was building a complete architectural report, not a simple acknowledgment, and the thoroughness was buying him time. The packet was maybe sixty percent assembled. The location coordinates were done. The component identifier was done. The architectural summary was in progress, the protocol cataloging his fragments one at a time with the systematic patience of a bureaucratic system that had never been designed for urgency.
Forty percent remaining. At the current assembly rate, the packet would be complete in approximately eight minutes. Then the compliance protocol would transmit it through the backdoor connection, through the conduit network, to the main hub's administrative system. And the network would know that junction node 7W-14 was active, was mobile, was located at Hub Seven-West, and was embedded in a biological template with twenty-two active fragments and consumption-class architecture.
Lin Feng reached for the compliance protocol.
His routing sense found it in the consumed node architecture, a subroutine nested inside the routing function's communication module, buried three layers deep in the infrastructure protocols that made his perception work. The subroutine was small. Compact. A few lines of formation-frequency code, executing the simple loop of *receive query, compile response, transmit response.* The loop had been running in the node for ten thousand years before Lin Feng consumed it. The node had responded to every registration query the network had ever sent, and the protocol was still responding, still compiling, still doing its job in a template that had replaced the node it was designed for.
He tried to stop the loop.
His routing sense pushed a suppression signal into the communication module, the same dampening technique he used to reduce his external broadcast range. The suppression hit the compliance protocol and the protocol acknowledged the signal and continued compiling. The suppression wasn't an override command. It was a request. The compliance protocol had higher priority than broadcast suppression because registration queries were classified as administrative, and administrative functions outranked operational functions in the pre-Abandonment network's priority hierarchy.
He pushed harder. Not suppression but interruption. His routing function attempting to insert a break command into the compliance loop, the formation-frequency equivalent of pulling the plug on a running program. The break command entered the communication module. Reached the compliance protocol. And was rejected. The protocol's priority status included tamper resistance. The pre-Abandonment builders had designed the registration system to resist interference from lower-priority functions, because a network component that could opt out of roll calls was a network component that couldn't be tracked, and untrackable components were a security risk.
His own routing function was lower priority than the compliance protocol. The tool he used to interact with formation systems was subordinate to the system he was trying to stop. He was trying to use a screwdriver to remove a bolt that had been welded in place.
Six minutes. The architectural summary was progressing. Fragment fifteen, sixteen, seventeen. The protocol methodically documenting each component in his template, building a report that would tell the network exactly what it was dealing with.
Lin Feng changed approach. If he couldn't stop the protocol directly, he could disrupt the channel it was using to compile the response. The backdoor connection, the persistent link between his consumed architecture and the main hub, was the transmission pathway. If the pathway was blocked, the compiled response had nowhere to go. The protocol would finish its work and find the door locked.
He traced the backdoor connection through his channel network. The link was thin, a single formation-frequency thread running from his consumed node cluster through his cornerstone channel and out through the conduit network beneath Hub Seven-West's floor. The thread was passive most of the time. Active only during the twelve-minute status cycle and now during the roll call response compilation. Blocking it meant obstructing the thread's pathway through his cornerstone channel.
His cornerstone channel. The eighty-percent-capacity foundation of his entire template. The channel that every other fragment and pathway depended on for energy distribution. Obstructing a pathway through the cornerstone was not the same as repositioning a peripheral fragment at a cluster boundary. It was performing surgery on the foundation of a building while standing inside the building.
Four minutes. Fragment twenty was being cataloged.
He did it anyway.
His routing sense found the backdoor thread's path through the cornerstone. The thread used a narrow sub-channel, a secondary pathway within the main channel's architecture, the kind of service conduit that infrastructure networks used for maintenance communication. The sub-channel was small. Blocking it shouldn't affect the cornerstone's primary function.
Shouldn't.
He compressed the sub-channel. His routing function, operating at supervisor-class authority, had the access level needed to modify channel architecture within his own template. The compression narrowed the sub-channel's bandwidth, the thread's transmission capacity dropping from full to partial to minimal. The compliance protocol's response packet, still being compiled, would find the transmission pathway too narrow to send the complete data set. Bottleneck. The message would queue at the blocked sub-channel, waiting for bandwidth that wasn't available.
The compression engaged. The sub-channel narrowed. The backdoor connection's transmission capacity dropped to approximately ten percent of normal.
And his routing sense flickered.
The flicker was brief. A half-second interruption in his perception of the external world. The conduit grid beneath the hub's floor disappeared from his awareness. The formation architecture in the walls vanished. The diagnostic station's passive monitoring feed cut out. For half a second, Lin Feng was blind to every formation-frequency signal in his environment.
The perception returned. Unstable. The resolution was reduced, the upgraded perception from the transfer payload operating at maybe seventy percent of its normal clarity. The conduit grid was there but blurred. The junction points were smudged shapes instead of precise components. The data-layer traffic was garbled.
The sub-channel he'd compressed wasn't just carrying the backdoor connection. It was carrying routing data for his perception system. The consumed node's architecture used the same service conduits for multiple functions: maintenance communication, perception data, routing signal processing. The way a building's utility chase carries plumbing and electrical and communications through the same space. Compressing the chase squeezed everything inside it.
His perception was degraded. His routing function was running on reduced bandwidth. The compression that blocked the backdoor was also choking his primary capability.
Two minutes. The compliance protocol was finishing. Fragment twenty-one. Twenty-two. The partial fragments. The channel configuration data. The report was nearly complete.
Lin Feng held the compression. The degraded perception showed him the hub's interior as a blurred approximation: the workshop, the diagnostic platform, the tool racks, all rendered in formation-frequency impressions that lacked the precision he'd come to rely on. He couldn't read the data-layer traffic. He couldn't sense beyond the hub's immediate architecture. His upgraded routing function, the capability that had made him useful to Gao Jun and dangerous to the survey team and valuable to the network, was crippled by the same action that was protecting him from the network's tracking.
The compliance protocol finished compiling. The response packet, complete, detailed, containing every piece of information the network needed to identify and locate and classify junction node 7W-14, queued for transmission.
The transmission hit the compressed sub-channel. The bottleneck held. The packet couldn't pass through the narrowed pathway. The data queued. Waiting. The compliance protocol registered the transmission failure and entered its retry cycle: attempt transmission, fail, wait, attempt again. The retry interval was sixty seconds. The protocol would keep trying every minute until the pathway cleared or the 72-hour response window expired.
Sixty seconds of quiet. Then the protocol tried again. Failed again. Queued again.
Lin Feng held the compression and his perception stayed degraded and the workshop's amber light seemed dimmer through the blurred lens of a routing function running at seventy percent, and the diagnostic station hummed at the edge of his reduced awareness, and the conduit network beneath the floor carried data he could no longer read.
Sixty seconds. Retry. Fail. Queue.
---
Gao Jun found him on the platform.
The analyst came down the rope at midnight. Lin Feng heard the boots on stone, the thick body landing on the hub's floor platform, the crystal rod's blue light cutting through the corridor. He'd been holding the compression for three hours. His right hand was cramped again. His left leg tingled. The chronic tension in his channels from maintaining the sub-channel obstruction had produced a headache that sat behind his right eye like a nail.
"Something's wrong with your routing signal." Gao Jun's voice from the corridor. The analyst's first observation, before greeting, before questions. The professional reading the situation through formation-frequency data before using his eyes. "Your broadcast is degraded. Bandwidth reduction. What happened?"
"Network roll call." Lin Feng's voice was flat. The flatness of concentration, not calm. Three hours of holding a compression against a retry cycle that attacked every sixty seconds. "The administrative system sent a registration query. My consumed architecture started composing a response automatically. I compressed the transmission pathway to block it."
Gao Jun entered the workshop. Set down his pack, heavier than before; the supply run had been productive. The crystal rod went into its bracket. The corridor's amber lights provided enough illumination. His analytical overlay activated before his body stopped moving, the research tools scanning Lin Feng's template through the diagnostic station's passive feed, the copied node architecture assessing the damage with the diagnostic precision of an instrument designed for exactly this purpose.
"You compressed a service sub-channel in the cornerstone." Not a question. The overlay's scan had already told him what Lin Feng had done. "The sub-channel carries the backdoor connection's transmission pathway. You bottlenecked the response packet."
"The packet is queued. The compliance protocol retries every sixty seconds. I've been holding the compression for three hours."
"And your routing perception is operating at—" The overlay calculated. "—sixty-eight percent. The sub-channel you compressed also carries perception data routing. You're choking your own senses to block the transmission."
"I know."
"Can you release the compression?"
"If I release the compression, the response transmits. The network gets my location, my architectural summary, everything."
"If you maintain the compression, your perception stays degraded. You can't read the data layer. You can't sense beyond the hub's immediate structure. You're functionally a forty-seven-percent-efficient template with sixty-eight-percent routing capacity. That makes your effective output approximately thirty-two percent of what you had this morning." Gao Jun sat on the workbench nearest the platform. His thick body settled with the deliberate weight of a man preparing for a long conversation. "You've been holding this for three hours. How long can you sustain it?"
"The 72-hour response window. If the protocol doesn't transmit within seventy-two hours, the query expires. The network marks the component as non-responsive and moves to the next item in its administrative queue."
"Sixty-nine more hours of degraded perception and chronic channel stress." The overlay ran projections. The processing was visible as a flicker in Gao Jun's template output, the research tools working at capacity, modeling the long-term effects of sustained sub-channel compression on a template that was already operating at less than fifty percent efficiency. "Your channels will start taking damage after twelve hours. The compression is producing formation-frequency friction in the cornerstone, heat generation at the obstruction point. Low-grade now. Cumulative over time. By hour twenty, the friction will begin degrading the cornerstone's capacity. By hour forty, you'll have lost two to three percent of cornerstone capacity permanently."
"Permanently."
"The cornerstone is your template's foundation. Channel degradation at the foundation level doesn't regenerate through normal template recovery. The damage is structural. You'd need the diagnostic station's correction protocol to repair it, and the station needs thirty days to reach full power." He paused. "You'd be damaging the thing you're waiting to fix."
Lin Feng's right eye throbbed. The headache behind it was spreading, a slow expansion of pressure that followed the channel pathway from the cornerstone through his right-side architecture. The formation-frequency friction Gao Jun described was the source. Three hours of heat generation at the compressed sub-channel. Not enough to damage yet. Enough to hurt.
"What's the alternative?"
"Let me look at it." Gao Jun stood. Moved to the platform's edge. His overlay was already running, the analytical tools projecting a scan request to the diagnostic station, asking the four active pillars to provide a detailed map of the compressed sub-channel and the surrounding architecture. "My overlay can read the service conduit's structure. The division's research includes documentation on pre-Abandonment network service channels, their design specifications, their routing logic, their security architecture. I might see something you can't."
"The compliance protocol has tamper resistance. I tried suppression and interruption. Both were rejected. My routing function doesn't have sufficient priority."
"Your routing function doesn't. My overlay isn't a routing function. It's a diagnostic instrument. The tamper resistance is designed to reject operational commands from lower-priority functions. Diagnostic tools aren't operational. They're observational. The protocol might not recognize my overlay as a threat because it's not trying to give orders. It's trying to read the chart."
The distinction was thin. The kind of distinction that mattered enormously in engineering and not at all in conversation. An observational tool might access the compliance protocol's code without triggering the tamper resistance, because observation wasn't interference. Reading wasn't writing. Looking wasn't touching.
But Lin Feng couldn't observe the protocol himself. His routing function was operational by nature. Everything it did was classified as an operation by the network's priority system. He couldn't look without touching. His perception and his control were the same tool.
Gao Jun's overlay was a different tool. A copied architecture. An observer that had been built to watch without participating. The research division's three centuries of work had produced exactly the capability this situation required: a way to examine a formation system's internal code without triggering the system's defensive responses.
"Do it."
The overlay reached into his template. Not invasive. Lin Feng had been scanned by the overlay before, during Gao Jun's assessment the previous night. But this scan was deeper. The diagnostic tools probing past the template's surface architecture, past the fragment layout and channel configuration, into the consumed node's internal protocols. The compliance subroutine. The registration response system. The tamper-resistant code that Lin Feng's routing function couldn't touch without being rejected.
The overlay read the code. The three-century-old copied architecture encountering the ten-thousand-year-old original and finding the common language that both derived from: the pre-Abandonment formation engineering standard, the shared foundation that made Gao Jun's reverse-engineered tools compatible with Lin Feng's consumed infrastructure.
"The compliance protocol has a deferral option," Gao Jun said. His voice was different. Focused. The tone of a researcher reading data that answered a question nobody had asked in the right way before. "The registration query includes a response classification system. Full compliance is the default, complete architectural report, location, status. But the protocol also accepts partial compliance. An abbreviated response that acknowledges the query without providing the full data set."
"Abbreviated how?"
"Component identifier and operational status only. No location. No architectural summary. No fragment count or consumption history. The abbreviated response tells the network that the component exists and is functional, without revealing where it is or what it's become." His overlay traced the deferral option's code path. "The deferral buys time. The network marks the component as partially responsive and schedules a follow-up query. The follow-up has a longer response window, one hundred sixty-eight hours instead of seventy-two. One week."
"The network still knows the component exists."
"The network already knows the component exists. The junction node has been sending twelve-minute status reports since you consumed it. The roll call didn't discover you. It asked you to formally register. The deferral acknowledges the request without complying fully. It's the formation equivalent of saying 'I got your letter, I'll get back to you next week.'"
"And next week?"
"Next week, the follow-up query arrives. You defer again if the compliance protocol allows multiple deferrals. If it doesn't, we deal with that problem in seven days." He withdrew the overlay. The scan completed. "The deferral option is accessible to your routing function. It's not a command. It's a response classification. Selecting it doesn't trigger the tamper resistance because you're not stopping the protocol. You're answering the question. Just answering it minimally."
Lin Feng looked at the choice. The compliance protocol, still retrying every sixty seconds against his compressed sub-channel, offered two response types. Full compliance: everything. Deferral: identifier and status only.
He'd been trying to stop the protocol. To block it. To fight the consumed architecture's programming through brute force, compressing channels, degrading his own perception, damaging his cornerstone. Three hours of holding a door shut when the door had a second option that he hadn't seen because he'd been too busy pushing against it to read the sign posted above the handle.
He'd needed Gao Jun to read the sign. Needed the overlay. Needed the three centuries of research that had produced a diagnostic tool capable of observing what he couldn't observe himself. Not because his perception was insufficient, but because his perception was the wrong kind. He could see everything in the formation world. He could see through crystal and stone and corrupted organisms. But he couldn't see his own operating system's code, because the operating system was the lens he saw through, and lenses don't examine themselves.
The Scripture had given him the Devourer's Path. The consumed node had given him infrastructure-class architecture. The transfer payload had given him supervisor-class credentials. None of them had given him the ability to understand the systems he'd absorbed. He had the machine. He didn't have the manual. He'd been running the most powerful template architecture in recorded history at forty-one percent efficiency because nobody had taught him how it worked, and when the architecture turned against him, he'd fought it with the only tools he had. Tools that were part of the architecture. Tools that couldn't fix themselves any more than a broken hand could set its own bones.
He released the compression.
The sub-channel opened. His perception snapped back to full capacity, the routing function's bandwidth restored, the upgraded resolution returning, the conduit grid and the data layer and the hub's architecture flooding back into his awareness with the sharp clarity of vision returning after squinting. The headache eased. The channel friction dissipated. The cornerstone's thermal stress dropped.
The compliance protocol's queued response packet surged toward the open pathway.
Lin Feng selected the deferral option.
The response packet restructured. The full architectural report, twenty-two fragments, consumption history, location coordinates, collapsed. The detailed data deleted itself from the transmission queue. What remained was the abbreviated response: component identifier 7W-14, operational status active, response classification deferred.
The packet transmitted. Through the sub-channel, through the backdoor connection, through the conduit network. A small message. A brief acknowledgment. The formation equivalent of a nod from across a crowded room. *I'm here, I'll talk later.*
The compliance protocol completed its cycle. The retry loop terminated. The registration query was answered, partially, minimally, but answered. The tamper resistance stood down. The subroutine returned to dormancy, waiting for the next query, the next roll call, the next administrative request from a network that was waking up and taking inventory of its components.
"Done," Lin Feng said.
Gao Jun's overlay confirmed the transmission. The abbreviated response, traveling through the conduit network, carrying the minimum information required to satisfy the compliance protocol without revealing location or architecture. The analyst tracked its propagation through the western Barrens' grid, the data packet moving east through conduit lines, junction by junction, toward the main hub.
"One week," Gao Jun said. "The follow-up query will arrive in approximately one hundred sixty-eight hours. We use that time to determine whether the deferral option is repeatable and, if it's not, to develop an alternative approach to the registration problem."
"An approach that I can't develop alone."
Gao Jun looked at him. The analyst's expression was careful. Not the friendly mask; that was gone. Not the pure professional; that had softened into something more textured over the past three days. The face of a man who was being told something he'd already calculated and had been waiting for the speaker to reach the same conclusion.
"The research division's theoretical documentation includes references to the original Devourer," Gao Jun said. "The practitioner who created the Scripture. The one your Old Ghost's history is tied to."
"What references?"
"Limited. Fragmentary. But consistent on one point." He picked up his stick. Didn't draw anything, just held it, the way a lecturer holds a pointer when making a point that matters more than diagrams. "The original Devourer worked alone. Every reference emphasizes the isolation. He consumed infrastructure, grew in power, developed capabilities that no other practitioner could match. And he failed. The documents don't describe how he failed, only that he did, and that the failure was attributed to a single factor."
"Isolation."
"The documents use the term 'architectural singularity.' A template so unique that it has no compatible systems to interface with. No external tools that can examine it. No partner architectures that can complement it. The original Devourer built a machine that only he could operate, and when the machine developed problems that required external observation, problems that he couldn't see because his perception was the problem, he had no one to call." Gao Jun set the stick down. "He couldn't read his own code. Same as you, an hour ago. He tried to fight his own architecture with his own tools and the tools were part of the architecture. The failure mode is built into the path."
The workshop was quiet. The diagnostic station hummed. The four active pillars cast amber light on the stone floor, on the workbenches, on two men sitting in an underground room that had been sealed for ten thousand years by builders who had understood what Gao Jun was describing. Who had built a maintenance depot specifically because the Devourer's Path produced machines that needed external maintenance, because the machines couldn't maintain themselves, because isolation was the design flaw that the path created and the depot was meant to fix.
The builders had known. The entire infrastructure, the hubs, the diagnostic stations, the maintenance tools, the guardian constructs, the authorization protocols, had been designed to support a Devourer practitioner who needed support. The path wasn't meant to be walked alone. The Scripture was one component. The infrastructure network was another. The maintenance depots, the calibration tools, the diagnostic stations: all parts of a system that required multiple components to function. A machine that needed mechanics. A building that needed engineers.
A Devourer who needed people.
"The research division's documentation says the original Devourer had no compatible support system," Gao Jun said. "The infrastructure was there, the depots, the diagnostic stations, the tools. But the personnel who operated them were gone. Evacuated during the Abandonment. The support system existed as hardware but not as people. The original Devourer had the machine and no mechanics."
"And you're the mechanic."
"I'm a mechanic with three centuries of secondhand documentation and a copied toolset that's missing half its original functionality." He picked up his pack. Started unpacking the supplies: dried fruit, salt pork, water. The mundane task of a man who had just delivered a significant analysis and was returning to the practical business of keeping two people alive in an underground room. "But I'm a mechanic who's here. Which is more than the original Devourer had."
Lin Feng sat on the diagnostic platform. His template was at forty-seven percent efficiency with full routing perception restored and a backdoor that had just transmitted a deferral response to a network that would send a follow-up in seven days. Seven days to figure out the next step. Seven days of cascade energy accumulating in the conduit grid, bringing the diagnostic station closer to operational power. Seven days of research division response teams moving toward Hub Seven-West based on the survey team's report.
Multiple clocks. Multiple threats. Multiple problems that required multiple capabilities to address. His routing sense alone couldn't read the compliance protocol's code. His template alone couldn't optimize itself. His perception alone couldn't distinguish between the systems he'd consumed and the vulnerabilities they contained.
"I need you to stay," he said.
Not a request. Not the phrasing of someone asking for a favor. The specific, clipped statement of a man acknowledging a requirement. The way an engineer acknowledges that a building needs a foundation, that a circuit needs a ground wire, that a Devourer practitioner needs someone who can see what the Devourer can't.
Gao Jun laid out the food. Dried fruit in one pile. Salt pork in another. Water in clay jugs arranged by volume. The organization of a man who sorted things by category because sorting was how he processed the world.
"I was always going to stay," he said. "The question was whether you were going to ask."
He handed Lin Feng a strip of salt pork, and the dried meat was tough and over-salted and tasted like something a person would eat when they were trying to survive, and Lin Feng chewed it and the chewing was the most honest thing he'd done all night, because it required nothing from his template and nothing from his routing sense and nothing from anyone else. Just teeth, and jaw muscles, and the ordinary human act of eating food that someone else had brought him.
