"Basically a for-loop with bad variable naming."
The room went quiet. Twelve researchers, ranging in age from mid-twenties to late sixties, stared at Nox from behind a conference table littered with papers and recording crystals. The presenter, a man named Dr. Huang who had spent the last twenty minutes explaining his theory of "resonant frequency harmonics in fire-affinity skill activation," stood at the chalkboard with a piece of chalk frozen mid-diagram.
Sera, sitting in the back row, closed her eyes.
"Excuse me?" Dr. Huang said.
Nox hadn't planned to speak. Tong had brought him to the weekly research seminar as an introduction. "Observe," Tong had said. "Listen. Take notes." Nox had listened. He'd taken notes. And then Dr. Huang had described his theory of why fire skills activate at different speeds depending on the caster's "resonant frequency," and Nox had seen the code underneath the theory and the code was simple. Stupid simple. The activation speed was a parameter. The parameter was set at skill acquisition. There was no resonant frequency. There was a value in a field.
And he'd said this out loud because twelve years of code reviews had trained him to flag incorrect assumptions immediately, and his social calibration still defaulted to "meeting room full of engineers" instead of "meeting room full of academics who've spent years on this research."
"The activation speed variation you're describing," Nox said, because stopping now would be worse than continuing, "isn't caused by a resonance effect. It's a parameter. Each skill has an activation_speed field set during the download from the altar. Different altars set different values. The variation between casters is because they acquired the skill from different altars at different times, not because their personal frequency modulates the skill's behavior."
Twelve faces. Twelve different expressions. Some confused. Some offended. One amused, which was Sera, who had opened her eyes and was watching the disaster with the specific focus of someone who'd predicted exactly this and was documenting it for her personal records.
Dr. Huang set down the chalk. "And you know this how, exactly?"
"I've read the code."
"You've read the code."
"The source code. Of fire-affinity skills. The activation_speed parameter is explicitly defined. It's not calculated at runtime."
"Source code." Dr. Huang turned to Tong, who was sitting in the front row with his hands folded and his expression carefully neutral. "Dean Tong. This is the student you recruited? The one who reads 'source code'?"
"This is Nox Renn," Tong said. "He will be working with us. His methods are unconventional."
"His methods are fiction. Spirit skills don't have 'source code.' They're channeled through resonant frequencies that, which is, as I've been explaining for twenty minutes—"
"I think," Sera said from the back row, "that we should move on to the next presentation."
The seminar moved on. Nox sat through two more presentations and said nothing. His notebook filled with observations about the researchers' work: which ones were close to the truth, which ones were operating on flawed models, which ones were asking the right questions with the wrong tools. He kept his mouth shut because Sera had kicked his ankle under the table after the for-loop comment and the bruise was a sufficient reminder.
After the seminar, in the corridor, Sera walked beside him and didn't speak for thirty seconds. This was long for her.
"For-loop with bad variable naming," she said finally.
"It was accurate."
"It was accurate. It was also the worst possible way to introduce yourself to a room full of people you're going to work with for the next year. Dr. Huang has been publishing on resonant frequency theory for a decade. You just told him his life's work is a for-loop."
"It is a for-loop."
"Nox."
"What?"
"People are not compilers. They don't respond well to error messages. You can't just flag someone's code as wrong and expect them to refactor. They have to want to see the bug."
She was right. And she was right in a way that the truth of the for-loop comment didn't address. The researchers in that room didn't know what Nox could see. They couldn't verify his claims. All they knew was that a D-rank former academy student had walked into their seminar and told a senior researcher that his work was wrong, with no evidence they could examine.
"I'll be more careful," Nox said.
"You'll try to be more careful. There's a difference." Sera's pen appeared in her hand. The automatic draw. "Come on. The mapping lab is this way."
---
The Institute's mapping lab was a chamber built around a portal. Not the full-size portal in the main facility. A smaller one. Research-grade. Heavily instrumented, ringed by monitoring crystals and recording equipment that captured every fluctuation of spirit energy within a fifty-meter radius.
The portal opened into a restricted Spirit Plane zone. Not wild territory. A controlled environment, maintained by the Institute for research purposes. The monsters were culled regularly. The architecture was stable. The zone was essentially a terrarium: a slice of the Spirit Plane kept in laboratory conditions.
Tong had left twelve spirit skills in the lab. Crystals containing skill imprints, arranged on a shelf like library books. Fire skills, water skills, earth skills, wind skills. C-rank through B-rank. A representative sample of the most common combat skill types.
"Map them," Tong had said. "Document every parameter, every function call, every line of code you can read. Sera will record. You will describe. We will build the first complete architectural documentation of spirit skill source code."
Nox started with a fire skill he hadn't seen before. Flame Lance. C-rank. Basic. He held the crystal, activated his Compiler perception, and read.
The code was familiar in structure. Parameters: damage, range, cost, cooldown, effects. The same framework as Sea of Fire. The same syntax. The same organizational logic.
But the function calls were different. Flame Lance called a function named `elemental_damage(type: fire, base: 45)`. Sea of Fire called the same function: `elemental_damage(type: fire, base: 12)`. Different parameters. Same function.
He picked up a water skill. Tidal Surge. C-rank. Read the code. The damage function was `elemental_damage(type: water, base: 38)`. Same function. Different type parameter.
Earth Wall. Defensive skill. Its damage function was `elemental_damage(type: earth, base: 0)` with a secondary function `barrier_generate(type: earth, strength: 200)`.
"Sera," Nox said. "They all use the same functions."
She was sitting at a monitoring station with three recording crystals active and her notebook open. "Same functions?"
"The damage calculation. Every skill I've looked at calls the same function for damage. `elemental_damage`. Different parameters for type and base value, but the function itself is identical. It's a shared library call."
"Like a common API."
"Exactly like a common API. The skills aren't independent programs. They're applications built on shared libraries. Standard functions that handle damage, range calculation, cost management, effect application. The individual skill is just a configuration file that calls the right functions with the right parameters."
Sera's pen stopped. Started again. Faster. "That's what Grandfather theorized. He called it 'the universal framework.' A common architecture underlying all spirit skills. He couldn't prove it because he couldn't see the individual function calls. He inferred it from statistical patterns in skill behavior."
"He was right. Mostly. The framework is there. It's real. It's standardized." Nox set down the water skill and picked up a wind skill. Read the code. Same shared functions. Same API calls. "The Spirit Plane is running on a single codebase. Every skill, every process, every system component, all built on the same framework. It's like a massive application suite running on a single operating system."
He said this with the certainty of a developer who'd spent his career working with exactly these patterns. Shared libraries. Standard APIs. Common frameworks. The Spirit Plane's architecture was, to his eyes, the work of an operating system designed to be maintainable and scalable. A machine built by something that understood software engineering.
That was the conclusion. The Spirit Plane was a machine. An enormously complex machine, yes. A machine with features he didn't understand yet, absolutely. But a machine. A system. Built. Designed. Running on code that followed rules he could read and edit.
He was wrong about this. He wouldn't know he was wrong for a long time.
---
The discovery happened on the seventh skill.
Nox had worked through the shelf methodically. Fire. Water. Earth. Wind. Ice. Lightning. Each one documented. Each one's shared function calls mapped. Sera had filled twenty pages of notes. The recording crystals were full and she'd swapped in fresh ones twice.
The seventh skill was a healing technique. Spirit Mend. C-rank. Basic. The kind of skill that every support-type Weaver learned in their first year.
He opened the code. The structure was the same. Parameters. Function calls. Standard library references. But the healing skill had different shared functions than the combat skills. Instead of `elemental_damage`, it called `biological_repair(type: tissue, rate: 15/sec)`. Different API. Same framework.
Nox mapped the healing functions. Documented them. Started to close the code.
Then he saw it.
Buried deep. Below the function calls. Below the shared library references. Below even the standard framework layer. A line of code that didn't belong to any visible parameter or function. It was small. A single call to a process that had no name in the skill's documentation.
```
BACKGROUND_PROCESS: monitor_call(entity_signature, edit_history, location)
```
He stared at it. Moved to the fire skill. Opened the code again. Looked deep.
Same line. Same background process. Same call.
Water skill. Same.
Earth. Wind. Ice. Lightning.
Every single skill in the collection had the same hidden background process running. A monitor call that reported three things: the entity using the skill, their edit history, and their location. Every time any Weaver anywhere activated any spirit skill, this function executed. Silently. In the background. Invisible to anyone who couldn't read the code.
The Spirit Plane was tracking every skill activation. Not through external monitoring. Through the skills themselves. The tracking was built into the code at a level so deep that no normal Weaver would ever know it was there.
"Nox?" Sera looked up from her notebook. He'd been silent for too long. "What is it?"
He read the line to her. Slowly. She wrote it down. Read it back.
"A monitoring function embedded in every skill," she said. Her voice had gone flat. The analytical register she used when the data was ahead of the theory.
"Every skill. Every activation. It phones home. Entity, edit history, location. The Spirit Plane knows who is using what skill, where, and whether they've been modified."
"That's how the defense system finds you."
"That's how it finds everyone. It's not looking for me specifically. It's logging everything. Every skill activation from every Weaver in the world feeds data back to the Spirit Plane's framework. The defense system just runs queries against the database."
Sera's pen was still. She was staring at the monitoring crystal, where the code was still displayed, the hidden function call visible in Nox's hand-drawn documentation.
"How long has this been running?" she asked.
"As long as the skills have existed. It's part of the base framework. Not added later. Built in."
"The Spirit Plane has been monitoring every Weaver on the planet. Since the beginning. Since the Fracture."
"Since before that, probably. The framework is older than the skills built on it. The monitoring was built first. The skills came after."
Sera closed her notebook. Not because she was done recording. Because her hand was shaking too badly to write.
"We need to tell Grandfather," she said.
"Not yet." Nox set down the healing crystal. Picked up his notebook. Drew a diagram: the shared function layer, the framework beneath it, and below that, the hidden monitoring layer. Three strata. Applications. Framework. Surveillance.
"First I need to know how deep it goes," he said. "And what it's doing with the data."
The monitoring crystal in the lab pulsed softly, recording their conversation with the same quiet efficiency as the background process that Nox had just discovered was running inside every spirit skill on the planet.
Somewhere in the Spirit Plane's architecture, a database was growing.
