Ghost's three freelancers entered the Bukhansan B-rank gate at 4:22 AM.
Taeyang watched from seven hundred meters upslope, sitting against a pine tree in the dark with the resonance mapping protocol running at surface level. The baseline ache. The constant. His ribs had graduated from sharp pain to deep soreness, the kind that reminded him they were broken every time he breathed wrong, which was most of the time.
The freelancers were professionals. Two melee-class hunters and a support, all B-rank, all experienced enough to clear a frost-variant dungeon without dying and cheap enough to take a job from an information broker who paid in cash and asked nothing. Ghost had found them through a contact who ran freelance hunter jobs out of a pojangmacha near Hongdae. The contact asked what the job was. Ghost said "dungeon clearance, Bukhansan B-rank, before six AM." The contact asked why. Ghost laughed and didn't answer, and the contact charged a fifteen percent finder's fee and didn't ask again.
The gate pulsed as they entered. Three mana signatures, each one depositing its frequency stamp on the gate boundary layer as they passed through. The stamps would overlay Taeyang's existing signature at the gate, layering fresh mana-spectrum data on top of his three-day-old residue. The more signatures, the more noise. The harder it would be for Song Eunji to isolate a single hunter's profile from the contaminated data.
For the primary mana signature, it would work. Three fresh overlays on a three-day-old residue would degrade Taeyang's primary frequency below the threshold for reliable tracking. Mina had run the calculations. The signal-to-noise ratio would drop to approximately 0.3, well below the 0.7 minimum that standard mana-signature analysis required for positive identification.
For the secondary infrastructure frequency, it wouldn't work at all.
Taeyang opened the resonance mapping protocol wider. Surface level. The infrastructure beneath the Bukhansan gate, the code-layer architecture that the System had built on, the pre-System foundation where his Origin Scan interaction had left traces that existed in a completely separate spectrum from mana signatures. The freelancers' mana output would wash over the infrastructure layer like rain washing over a submarine. Different medium. Different depth. The infrastructure frequency would sit undisturbed beneath the mana-layer noise.
He watched the readings for twelve minutes. The freelancers were inside. Song Eunji was scheduled for six AM. Ninety minutes away.
The infrastructure frequency from his Bukhansan run was still there. Clear. Distinct. The strongest secondary signature he'd produced anywhere, because the Origin Scan depth interaction in the boss chamber had been the deepest infrastructure contact he'd ever made inside a dungeon. If Eunji's ability was sensitive enough to read the code layer beneath the mana spectrum — and Ghost's intelligence suggested it might be, given her four years of Bureau-trained analysis work — she'd find it. She'd compare it to the Gwanak secondary. She'd know.
He called Jiyeon through Suhyeon's relay.
"The contamination plan covers the mana layer. It does not cover the infrastructure frequency."
A pause. The relay's encryption adding latency. "I am aware. I told you the rule-modification mask would partially obscure but not eliminate the code-layer signature."
"Can you mask the code layer at the gate boundary remotely? From your current position?"
"No. My rule modification requires proximity to the architectural element I am modifying. The gate boundary is at the Bukhansan location. I am at the Buramsan monitoring position. The distance exceeds my operational range."
"What's your operational range for code-layer modification?"
"Approximately one hundred meters for precise work. Two hundred for coarse adjustment."
The gate was seven hundred meters downslope. Jiyeon was on the opposite side of Bukhansan. Neither of them was close enough.
Taeyang looked at the gate. The blue-white pulse, steady, the freelancers somewhere inside running the frost dungeon. Song Eunji ninety minutes away. The infrastructure frequency sitting in the gate boundary's code layer like a name carved in stone that no amount of rain would wash away.
"I'm going in," he said.
"Your ribs are cracked. The mana mask I prepared requires calibration time that—"
"How long to calibrate the mask?"
"Four minutes at the gate boundary. I can transmit the calibration sequence through the relay. You would apply it to your own mana output using your hacking interface."
"Send it."
He moved downslope. The ribs objected. Moving through mountain terrain in the dark with broken ribs was the kind of experience that made you very aware of how many muscles connected to the rib cage, which was all of them. He reached the gate perimeter in nine minutes. Checked the area — no Association presence, no patrol routes within four hundred meters. Dojin had confirmed the patrol schedule.
The calibration sequence arrived through the earpiece in a format that Jiyeon's rule modification translated into hacking interface parameters. He applied it at the gate boundary. The mask settled over his mana output like a skin, converting his dungeon-modification signature into a generic fire-class energy pattern. If Eunji read his mana output now, she'd see a fire-type hunter. Wrong class, wrong signature, wrong person.
He entered the gate.
The transition dropped him into the frost environment. Same ice cavern network from five days ago, same blue-white walls, same frozen floor. The dungeon had regenerated since the freelancers entered — the System's standard regeneration protocol restoring cleared sections behind the active party. He was entering a fresh instance that shared the same gate boundary but generated independent interior space.
He moved to the gate boundary's interior surface. The section of architectural code where the System's transport protocol interfaced with the dungeon's generated space. This was where his mana signature — and his infrastructure interaction signature — was stamped. The gate boundary was the doorway, and everything that passed through it left traces on both sides.
The infrastructure interaction residue was embedded in the code layer beneath the gate boundary's System architecture. He could see it with the resonance mapping protocol at surface level: the secondary frequency from his Origin Scan interaction, dense, clear, unmistakable. A frequency that told anyone who could read it that this hunter had interfaced with pre-System infrastructure at a depth that no standard dungeon ability should reach.
He needed to scramble it. Not delete — he couldn't delete data from the infrastructure's code layer without hub-depth access, which would cost pain he couldn't afford with broken ribs. But he could overwrite the frequency with noise. Randomized code-layer data, generated by his hacking interface and pushed into the infrastructure layer at the gate boundary, covering the existing frequency with garbage data that would make it unreadable.
Degaussing. The developer's term for scrambling a storage medium's data by flooding it with random magnetic noise. He'd done it to hard drives during his game dev days when builds needed to be securely deleted. Same principle. Different medium.
He opened the hacking interface. Reached past the System's gate boundary code into the infrastructure layer beneath it. The pain arrived. Not the scanning pain — the hacking pain. The modified operator protocols converting the code-layer interaction into a signal that his body processed as a spike through the skull. Sharp. Focused. The blade behind his eyes driven in with a hammer.
He held the connection. Generated randomized code-layer noise through the hacking interface, feeding garbage data into the infrastructure frequency at the gate boundary. The noise overwriting the infrastructure interaction residue the way static overwrites a radio signal. Each second of sustained hacking produced another wave of pain. His jaw locked. His vision compressed.
Four seconds. The infrastructure frequency was half-obscured. The garbage data covering the original signal in patches, breaking up the clean profile that Eunji's analysis would need.
Seven seconds. The frequency was mostly scrambled. Fragments of the original signal visible through gaps in the noise, but the overall pattern disrupted beyond reconstruction. A mana-signature analyst reading the code layer now would see fragments. Anomalous, yes. Incomplete, yes. But not enough to build a comparative profile against the Gwanak data.
Nine seconds. The frequency was buried. The garbage data covering the infrastructure layer at the gate boundary in a dense blanket of randomized code. He pulled back from the hacking interface. The pain receded in slow waves, each wave leaving behind the residual ache that would take hours to fully fade.
He stood in the frost dungeon's entry corridor, breathing through broken ribs and scrambled vision, and checked the gate boundary's code layer one more time through the resonance mapping protocol.
Clean. Or close enough. The infrastructure interaction frequency was noise now. Unreadable garbage.
He exited the gate before the freelancers completed their run. The mountain air hit his sweat-soaked jacket. 5:11 AM. Forty-nine minutes before Song Eunji's scheduled arrival.
He climbed back to the observation position. Seven hundred meters. Twelve minutes with cracked ribs. He sat against the pine tree and ran the resonance mapping protocol and watched the gate boundary's code layer from the safety of distance and passive scanning.
5:58 AM. A car on the access road below the gate. Rental sedan. Single occupant.
Song Eunji stepped out and walked to the gate with the economy of motion that comes from doing the same job hundreds of times. She stood at the gate boundary for six minutes. Reading. Her ability processing the contaminated signatures, the overlapping mana frequencies from three freelancers and a three-day-old masked residue, the scrambled code layer beneath the mana spectrum.
She left at 6:12 AM.
Through the resonance mapping protocol, Taeyang couldn't read her analysis. He couldn't see what her ability detected or how she categorized the data. He could only watch her leave and hope that the contamination and the scramble had been enough.
Ghost's contact in Iron Sword's admin pool confirmed two hours later: Eunji's preliminary report listed the Bukhansan gate data as "inconclusive — multiple overlapping signatures, degraded primary, secondary frequency artifacts present but non-reconstructible." She'd flagged it for re-examination if additional samples became available.
Inconclusive. Not clean. Not negative. Inconclusive.
She'd found fragments of the secondary frequency. She knew something was there. She just couldn't see enough of it to build a profile.
Taeyang closed the resonance mapping protocol and sat in the safe house and processed the partial victory. Then Jiyeon's monitoring report came through Suhyeon's relay.
"The Bukhansan peripheral junction." Her voice was flat. The engineer reporting a structural finding, not an emotional response. "Node seventeen on the network map. The unattended junction two point three kilometers southeast of the Bukhansan convergence site."
"What about it?"
"Its autonomous correction cycle recorded an anomalous load spike approximately forty minutes ago. The spike's frequency pattern matches code-layer noise. Randomized data. The type of noise that a hacking interface would produce when overwriting infrastructure-layer data at a connected gate boundary."
The garbage data. The randomized code-layer noise he'd pumped into the Bukhansan gate boundary to scramble his infrastructure interaction signature. The noise hadn't stayed at the gate boundary. It had propagated through the infrastructure's connection paths, traveling from the gate to the nearest junction the way static traveled through a wire.
Node seventeen. One of the nine unattended junctions. A junction with no embedded consciousness to absorb unexpected data loads.
"The node's autonomous correction process absorbed the noise spike," Jiyeon continued. "The absorption cost was a stress increase of approximately three percent. Node seventeen's cumulative stress level is now at fourteen point seven percent. Pre-spike baseline was eleven point eight percent."
Three percent. A single event. The stress projections Mina had calculated assumed a steady accumulation rate of 0.4% per day from the resonance growth. Node seventeen had just jumped forward a week's worth of stress in forty minutes because Taeyang had scrambled a gate boundary to hide his tracks from a mana-signature analyst.
"The noise propagated from the gate boundary through the infrastructure connection," he said.
"Correct. The gate boundary's code layer is connected to the infrastructure network through the same architectural pathways that carry the Deep's signal. Data introduced at the gate boundary travels the connection. Randomized noise travels the connection. The noise reaches the nearest junction and the junction's correction process must absorb it."
He'd fixed the tracker problem. And he'd pushed one of the nine unattended nodes closer to failure.
The game developer who knew about dependencies. About systems where fixing a bug in one module crashed another module downstream. About the impossibility of touching code in a complex architecture without triggering side effects in systems you didn't know were connected.
The infrastructure was a complex architecture. Everything was connected. Every interaction at the code layer propagated through the network. Every hack, every scan, every modification he made at any point in the system reached other points through pathways he was only beginning to map.
He couldn't interact with the infrastructure without consequences. Even when the interaction was damage control. Even when the purpose was to protect the network from discovery. The act of protection damaged the thing he was protecting.
"Can node seventeen absorb more spikes at this level?"
"The autonomous correction process can absorb additional loads until cumulative stress reaches approximately thirty percent. Above thirty percent, the correction process begins to fail. Correction failure at an unattended node would produce cascading effects through the connected infrastructure pathways." Jiyeon paused. "You are thinking about future gate boundary operations."
"I'm thinking about the fact that every time I touch the infrastructure, somewhere in the network, something breaks a little more."
Jiyeon didn't respond for several seconds. The relay's encryption filling the silence with the faint hiss of mana-layer static.
"Yes," she said. "That is an accurate assessment."
He put the earpiece down. Looked at Hyungsoo's documentation on the floor. Pages forty-seven through forty-nine. The resonance mapping protocol, which operated at surface level and left no trace because it didn't interact with the infrastructure. It only listened.
Listening was safe. Touching was not.
Every dungeon he entered left his signature. Every hack produced pain. Every infrastructure interaction propagated through the network to junctions that couldn't absorb the load. Every solution created a new problem. He was playing a game where every move cost health points and the health bar was shared between him and the infrastructure he was trying to save.
The nine unattended nodes. The tracker calibrating her ability against his breadcrumbs. The Association investigating anomalies they couldn't explain. The resonance growing. The presences waking. And now, because he'd tried to cover his tracks, one of the nine weak points was weaker than it should have been, and the others were one gate-boundary hack away from the same fate.
Mina arrived at noon with updated stress projections.
She looked at him. At the residual pain in his face. At the documentation on the floor and the earpiece on the table and the posture of a man who had solved a problem and discovered that the solution was itself a problem.
"Node seventeen," she said.
"Three percent spike. My scramble at the Bukhansan gate boundary propagated through the connection."
She sat down and opened her laptop and recalculated the stress timelines without asking him how he felt about it. The analyst who dealt in data because data didn't require emotional processing to be useful. She ran the numbers for four minutes.
"At the revised stress level, node seventeen's failure timeline has shortened from twenty-six days to nineteen." She typed. Saved. Closed the laptop. "What did we gain?"
"Eunji's Bukhansan data is inconclusive. She has fragments of the secondary frequency but cannot reconstruct a profile. We bought time against the tracker."
"Seven days of node seventeen's structural timeline, traded for an inconclusive report from a tracker who will continue searching." She looked at him. "Was it worth the trade?"
He didn't answer. Mina didn't push. She opened the laptop again and started working on something else, and the question sat between them the way the chain of causation sat between them, unanswered because the answer depended on which problem killed them first.
