Fang Zhao hit the training dummy and it didn't move.
Not because Fang Zhao hit softly. He hit with the steady, competent force of a senior Institute student with earth affinity and five years of combat practice. The dummy registered B-rank force. Consistent. Reliable. The same reading every time, plus or minus two percent. Fang Zhao was a metronome in a world of jazz musicians.
"Solid," Shi Chen said. He was leaning against the courtyard wall, arms crossed, watching the way he watched everything: with the flat assessment of a fighter measuring a fighter. "Not flashy."
"I don't do flashy," Fang Zhao said. He was twenty-one. Quiet. Broad-shouldered in the way that earth affinity Weavers tended to be, as if the spirit energy that reinforced stone also reinforced bone density. His hands were large and unhurried. "I hold positions. I absorb damage. I give the damage dealers time to work."
"Works for me." Shi Chen turned to Nox. "He's the fifth?"
"He's the fifth."
Fang Zhao had been Sera's suggestion. A senior student who'd been at the Institute for three years, who trained every morning at six, who had never missed a seminar, who did exactly what was asked of him without complaint or ambition. The kind of person who showed up, did the work, and went home. In a team of specialists and anomalies, Fang Zhao was the foundation. The part of the building that nobody looked at because it was too busy holding everything else up.
The Daxia Challenge team was complete. Nox (tactical analyst, Compiler, combat hybrid). Pang Wei (dual affinity, high B-rank). Sera (support, fire B-rank, research analysis). Shi Chen (melee, C-rank rebuilding). Fang Zhao (earth anchor, B-rank).
Five people. Six weeks of preparation. Against a Korean team led by an S-rank lightning specialist.
The math didn't work. Nox liked it when the math didn't work. It meant the answer wasn't in the numbers.
---
Stealth editing was an accident.
Nox discovered it during a Tuesday afternoon mapping session. He was cataloguing skill variations in the Institute's restricted collection, a routine task he'd been doing for weeks. The monitoring function logged every Compiler activation. Each time he opened a skill's code, the background process fired. Each time it fired, Sera's recording crystal captured the event.
The events were getting smaller. The monitoring function still logged his activations, but the log entries were shrinking. Less data per entry. Lower priority flags. The system was getting used to him reading code. It was like a firewall that had added an exception rule for his IP address. His Compiler activations were still logged, but they'd been downgraded from "security alert" to "routine traffic."
He tested this. He opened a C-rank wind skill and made a tiny edit. A one-percent increase to the range parameter. Barely a rounding error. The smallest modification he'd ever attempted.
The monitoring function logged the edit. The priority flag was LOW. No surge response. No hunter-killer deployment. The system had noticed and done nothing.
He tried again. Another one-percent change. A different parameter. Same skill. The log entry was the same. LOW priority. No response.
"Sera. I just made two edits and the defense system didn't react."
Sera checked her crystal. Confirmed. Two edit events. Both logged. Both flagged LOW. No escalation.
"The threshold changed," she said. "The COMPILER_ACTIVE classification increased your aggression threshold. The system tolerates small edits from you now."
"It tolerates them. Or it's watching to see what I do with them."
"Both. It's a monitoring stance. Like a security system that stops setting off the alarm for small movements and starts recording them instead."
Stealth editing. Small changes. Below the detection threshold. Each edit individually meaningless, but cumulative modifications could add up to significant changes if done gradually.
Nox spent the next two weeks testing the boundaries. How big could an edit be before it triggered a response? How many small edits could he stack? How long between edits before the system reset its cumulative tracking?
The answers: individual edits under five percent parameter change passed without response. He could stack up to three small edits per session before the cumulative total crossed the threshold. The system reset its tracking every twenty-four hours.
He wrote the rules in his notebook:
*STEALTH EDITING: Edits under 5% parameter change per modification. Max 3 per 24-hour period. Cumulative tracking resets daily. Larger edits still trigger immediate response. System is watching, not attacking. The leash is longer but it's still a leash.*
Using stealth editing, he acquired Heart-Piercing Blade from the Institute's B-rank collection and edited it over three days instead of three minutes.
Day one: defense break modifier added to slot one. Five percent base chance to ignore armor.
Day two: shield break modifier added to slot two. Five percent base chance to destroy active barriers.
Day three: armor pierce modifier added to slot three. Five percent bonus damage against armored targets.
Each edit individually minor. Each one a five-percent tweak that wouldn't change a fight by itself. But all three stacked on a single-target piercing skill turned Heart-Piercing Blade into a dedicated anti-defense weapon. Against armored opponents, the cumulative effect was a fifteen-percent advantage that multiplied with each hit.
No surge. No hunter-killer. No compilation headache. The stealth edits compiled with the energy cost of a sneeze.
"You're getting better at this," Sera said. She was tracking his edit efficiency on a graph. The line was going up. "The compilation cost per edit has dropped by forty percent since you started stealth editing. You're optimizing."
"The Compiler is caching the common operations. Same thing that happened with the B-rank edits. Practice makes the process cheaper."
"It also means the monitoring system has more data on how you edit. It's learning your patterns the same way you're learning its thresholds."
An arms race in slow motion. Nox getting better at editing quietly. The Spirit Plane getting better at watching him.
---
Team training was a controlled disaster for two weeks and then, gradually, it was just controlled.
Pang Wei refused to limit his dual affinity usage during practice. His position was that training at reduced capacity was training for a fight he wouldn't fight. His microfractures were a problem he'd deal with by not dealing with them, which was a philosophy that Nox recognized from developers who ran production systems on hardware they knew was failing because replacing the hardware meant downtime they couldn't afford.
"If the fractures get worse during the challenge, I'll switch to single affinity," Pang Wei said. He was standing in the training yard with both swords drawn, the ice and fire blades leaving contrails in the morning air. "But I train with both. Because that's what I'll use."
Nox read Pang Wei's Core architecture once per week. The fractures weren't worsening during single sessions. They were stable. The danger was cumulative. Three or four dual-affinity fights in a row and the stress would build past the safety margin.
"Two fights maximum with dual affinity," Nox told him. "After that, switch to single. Ice only. It puts less strain on the fracture plane."
"Three."
"Two."
Pang Wei sheathed the fire sword. Drew it again. Sheathed it. A habit that looked like a tic but was probably calculation. "Two dual-affinity fights. Then ice only. Agreed."
Shi Chen trained differently than the others. He didn't practice techniques. He practiced fighting. Every session was a sparring match against whoever was available. Fang Zhao, who could take his punches. Pang Wei, who was fast enough to test his reactions. Even Sera, who he treated with the specific care of a man who was physically gentle with people he could break by accident.
His C-rank was solidifying. The patched channels were settling into their new configurations. His output was consistent, climbing slowly, and the growth ceiling Tong had estimated at B-rank was starting to look accurate. In six months, Shi Chen would be back to where he'd been before Park's gauntlets. Maybe higher.
They didn't have six months. They had four weeks. And C-rank Shi Chen was what they'd work with.
Sera's combat training focused on precision over power. Her fire lance was B-rank and she'd been able to hit the gaps in a hunter-killer's armor from fifteen meters. But she'd never been in a competitive fight. Her role in the challenge was support and analysis, same as the academy expedition, but the challenge format meant she might need to enter the arena.
"If I fight," she told Nox during a break, "it should be strategic. A forfeit that gives you tactical data. Like what the outline says." She caught herself. Smiled at her own slip. "Like what the plan says."
Nox had trained her to relay information. During sparring sessions, she stood at the perimeter with her recording crystal and called out what she could see. Skill types. Damage ranges. Cooldown timings. Her partial code perception, sharpened by weeks of Spirit Plane exposure, gave her visibility that no normal observer could match. Not Nox's full resolution. But enough.
---
The Korean team arrived on a Wednesday.
They flew in on a military transport that landed at the capital's auxiliary airfield. Five fighters. Three support staff. Two diplomatic attaches. And a security detail that was larger than what a cultural exchange delegation needed, which told Nox everything about how seriously Korea was taking this.
Nox saw them from the Institute's courtyard. The airfield was visible from the upper floors of Building 4, and Sera had set up a spotting position near the window with her recording crystal aimed at the arrival platform.
"Five fighters," she said. "Four in standard Korean military uniform. The fifth in something different. Higher quality. Custom fit."
"Jin Seong."
"Probably."
Nox activated the Compiler. The distance was maybe four hundred meters. Beyond his normal reliable range. The code overlay flickered, thin, barely readable. Individual parameters were blurry. He couldn't read specific numbers.
But he could see shapes. Outlines. The general architecture of the Korean fighters' skill code. And Jin Seong's code was different from the others the way a cathedral is different from the houses around it.
The four standard fighters had clean, efficient code. Korean military formatting. Well-maintained. Compact. Like code written by a team with strict style guidelines and regular reviews.
Jin Seong's code was massive. Dense. The spiritual energy output from his Core was visible even at this distance as a bright node in the code overlay. S-rank. The difference between his output and the B-rank fighters around him was the difference between a server farm and a laptop.
But inside the density, something was wrong. The code wasn't clean. Parts of it were frayed. The edges of his skill architecture had ragged sections where the code was degrading, the syntax corrupting in slow motion. Like a program with memory leaks that had been running too long without a restart.
"His code is degrading," Nox said.
Sera looked up from her crystal. "You can see that from here?"
"Not the details. The shape. His skill architecture has corruption around the edges. It's old damage. Not recent. Like his code has been breaking down for a while."
Sera wrote fast. "Jin Seong's S-rank skill is called Heaven's Circuit. Korean intelligence reports suggest he's been the top young fighter for four years. That's a long time to operate at S-rank output." She stopped writing. "What if the degradation is from overuse? S-rank skills demand more from the Spirit Core than lower ranks. If he's been running at max capacity for years, the code could be wearing out."
"Like skill degradation."
"Like hardware degradation. A processor running at peak clock speed for too long without cooling."
Nox watched Jin Seong's outline move across the airfield. The S-rank energy signature was bright. Clear. But the corruption around the edges was there. Faint from this distance. Readable up close.
Jin Seong was degrading. His signature skill was breaking down. And the Korean team had entered this challenge knowing their strongest fighter was operating at less than full capacity.
Which meant they either believed he was strong enough to win at reduced power, or they needed the challenge victory badly enough to risk fielding a compromised ace.
Either way, the corruption was a weakness. A bug in the enemy's production code. And Nox was the only person in the world who could see it.
"Don't tell anyone else yet," Nox said.
"Why not?"
"Because if Korea knows we know about the degradation, they'll change their strategy. If they think Jin Seong is at full strength in our eyes, they'll play him the way they planned. And a predictable enemy is a readable enemy."
Sera closed her notebook. Her pen went behind her ear. She looked out the window at the distant figures crossing the airfield.
"You're thinking like a general," she said.
"I'm thinking like a developer who found a bug in the competitor's product and wants to wait for the right moment to exploit it."
"Same thing."
Nox kept watching. Jin Seong crossed the airfield and disappeared into the transport building. The S-rank signature dimmed as he moved out of range. The corruption faded with it.
Four weeks until the challenge. A team of five against a team with a degrading S-rank. Commander Renn's map to Zone Null as the real prize. And a Spirit Plane that was watching Nox with a classification it had invented just for him.
Somewhere in that tangle of competing interests and broken code, there was a path to winning. Nox just needed to find it before the clock ran out.
