The first code review took four hours and nearly ended in a fistfight.
Not a literal fistfight. Pang Wei had taught Yara that you could resolve technical disagreements with swords, and she'd taken the concept metaphorically. The disagreement was about function naming conventions.
"Your variable names are incomprehensible," Yara told Park Somi. They were in the mapping lab. Three Compiler variants plus Nox. The bounded protocol redesign was displayed on the main console -- a shared codebase visible to everyone with sufficient Compiler perception. "What does 'xfer_buf_v2_mod' mean?"
"Transfer buffer version two modification. It's descriptive."
"It's abbreviated gibberish. Nobody else can read it."
"I can read it."
"You can read it now. Can you read it in six months when you've forgotten what 'v2_mod' refers to?"
Park Somi's jaw set. The controlled frustration of someone who'd been writing code her own way for months and was being told to change by someone who'd been at the Institute for two weeks.
Nox let them argue. Not because the argument was productive -- it wasn't -- but because code review culture required friction. The alternative was silent acceptance, and silent acceptance produced bugs.
"Both of you stop," he said when the argument hit the five-minute mark. "Somi, expand your variable names. Full words. Readable. Yara, phrase your reviews as questions, not attacks. 'What does this variable represent?' works better than 'this is gibberish.'"
"But it is--"
"Questions. Not attacks."
Yara crossed her arms. Uncrossed them. Tapped her fingers on the desk -- the coding rhythm, faster now. Frustrated.
"Fine. Park Somi." She pointed at the variable. "What does this variable represent, and would a new developer understand it without context?"
Park Somi looked at the variable. Considered.
"No," she admitted. "I'll expand it."
Progress. Incremental. Painful. Like every code review Nox had ever been part of.
---
The bounded protocol redesign took three weeks.
The original version -- the one Nox had written in the Root Directory during the compatibility patch -- was a single-user system. One Compiler. One set of access controls. One monitoring function. It worked for Nox because Nox was the only user.
The new version needed to support hundreds of Compiler variants with different permission levels, different perception ranges, and different edit capabilities. It was the difference between a personal computer and a server farm.
Nox architected the framework. The high-level design. The permission hierarchy. The monitoring integration. The defense system interface.
Yara wrote the permission engine. The code that determined what each registered Compiler user could access, what they could edit, and what required escalated authorization. Her implementation was aggressive -- she built in safety margins that Nox hadn't considered, informed by her own experience with the buffer exploit.
"If someone finds a loophole, the permission engine should fail-safe to restricted access," she said. "Not fail-open. Fail-safe."
"That could lock out legitimate users during a system error."
"A locked-out legitimate user is annoyed. A malicious user with open access is a casualty report. I'll take annoyed."
Nox looked at her. The fifteen-year-old who'd exploited his code for three weeks was building the lock that would prevent others from doing the same thing.
"Approved," he said.
Park Somi wrote the monitoring module. The replacement for Nox's secret surveillance framework. Open. Transparent. Shared. Every registered Compiler user could see the global edit log, the cumulative threat assessment, and the defense system's current response level.
"The transparency creates accountability," Park Somi explained during a review session. "If everyone can see everyone's edits, social pressure supplements technical enforcement. Nobody wants their name next to a flagged modification."
"Social pressure doesn't work on everyone," Yara said.
"It works on most people. Technical enforcement handles the rest."
Two other variants -- a mathematician from Daxia named Chen Wei and a former musician from Korea named Han Jae -- contributed integration modules. Chen Wei's mathematical precision produced clean synchronization code. Han Jae's pattern-recognition talent found rhythm inconsistencies in the data flow that nobody else caught.
The team worked in the mapping lab from 7 AM to midnight, six days a week. Nox reviewed every commit. Yara reviewed Nox's commits. Park Somi reviewed Yara's. The review chain was circular -- everyone checked everyone, and nobody's code went into the shared codebase without at least two approvals.
Sera documented the process. Not the code -- she couldn't read it at the detail level. The methodology. The collaboration patterns. The friction points and resolutions. Her notes would become the foundation of the Institute's Compiler Training Manual, the first formal guide to teaching code perception and edit capability.
"You're writing a textbook," Nox told her.
"I'm writing a field guide. Textbooks are theoretical. This is practical." She held up her notebook. Filled pages. Diagrams. Decision trees. "Chapter one: 'You're Not Crazy, the Code Is Real.' Chapter two: 'Reading Before Editing, or How Not to Kill People.'"
"Chapter two's title needs work."
"Chapter two's title is exactly right. Yara approved it."
---
The bounded protocol v2 compiled on a Tuesday evening.
The deployment was different from the original. Instead of Nox writing and deploying alone, the entire team compiled their respective modules simultaneously. Five Compiler users, working in concert, pushing code to the Root Directory through synchronized bounded protocol sessions.
The Root Directory's central intelligence monitored the deployment with what Nox perceived as curiosity. This was the first collaborative human compilation. Five minds editing the Plane's architecture in coordination. The Plane's impression was: interest. The same kind of interest it had shown when Nox had coded the filter together with it. A living system watching a new behavior emerge from its symbiotic partners.
The deployment sequence:
1. Park Somi deployed the monitoring module. Clean compile.
2. Chen Wei deployed the synchronization updates. Clean compile.
3. Han Jae deployed the integration pathways. Clean compile.
4. Yara deployed the permission engine. Clean compile. She exhaled when the validation passed. The first breath she'd taken in forty seconds.
5. Nox deployed the framework core and connected the modules. Clean compile.
The bounded editing protocol v2 went live.
Sixty-three registered Compiler variants worldwide received access. Their permissions activated. Their monitoring feeds came online. The transparent edit log populated with sixty-three accounts, each one identified by name, location, and perception level.
On the shared monitoring display, the defense system's cumulative threat assessment updated. The number dropped. Significantly. Because sixty-three previously unauthorized users were now authorized, and their historical edit signatures reclassified from "threat" to "managed activity."
The defense system's response level, which had been climbing steadily as Coalition variants accumulated unauthorized edits, dropped from yellow to green. The Plane's immune system relaxed. The antibodies stood down.
"Green across the board," Sera said. She was watching the monitoring console with recording crystals active. "Defense response at baseline. No elevated threat assessment. The protocol is live."
Nox looked at the deployment result. Five modules. Five authors. Zero errors. Clean compile.
"First distributed deployment in human-Plane interaction history," he said.
"Noted for the record," Sera said.
"Also noted: this is the first time my code shipped without a critical vulnerability that someone had to find afterward."
"Because four other people reviewed it."
"Because four other people reviewed it. Yes."
Yara leaned back in her chair. Her fingers tapped the armrest. The coding rhythm, slower now. Satisfied.
"That's a clean deploy," she said.
"That's a clean deploy."
"I've never had a clean deploy before. All my previous work was solo commits with no review."
"Welcome to team development."
"It's slower."
"It's safer."
"Both things." She looked at Park Somi, who was running post-deployment diagnostics with the focused precision that characterized everything she did. "Your monitoring module is solid, by the way."
Park Somi looked up. Surprised. Yara didn't give compliments.
"Thank you."
"Your naming conventions still need work."
"Thank you."
---
The days after deployment were quiet. The kind of quiet that Nox had learned to distrust, because in his experience, quiet periods preceded the discovery of whatever he'd missed this time.
But the protocol held. The monitoring framework tracked edits worldwide. Sixty-three Compiler variants operating within defined parameters. No unauthorized activity. No defense system alerts. No stutters, blackouts, or timing mismatches.
The Spirit Plane's recovery continued. The lease protocol's energy distribution was stable. The seed filter managed the awakening rate. The new Weavers who'd completed activation were progressing through the emergency training program that Sera had designed and the response team was delivering.
Nox spent the quiet time doing something he'd never done before: maintenance.
Not crisis response. Not emergency patches. Not desperate deployments. Just... checking things. Running diagnostics. Reviewing the code he'd written over the past months. Looking for vulnerabilities he might have missed. Testing edge cases he hadn't considered.
It was the most boring and most important work he'd done since arriving in this world.
Sera found him at the console at 11 PM on a Thursday, running his forty-seventh diagnostic cycle.
"You're maintaining," she said.
"I'm maintaining."
"You look almost peaceful."
"The system is stable. No alerts. No crises. No fifteen-year-olds finding bugs in my code."
"Yara found a minor inconsistency in the synchronization module this afternoon."
"What?"
"She reported it through the review channel. Park Somi confirmed. Chen Wei fixed it. The patch deployed through standard review process. Two reviewers. Clean compile."
Nox stared at her. "They fixed a bug in my system without me."
"They fixed a bug in the team's system through the team's process. That was the point."
He leaned back. The chair creaked. The monitoring display showed the globe -- seven million active Weavers, five hundred and seventy seed awakenings at various completion stages, sixty-three registered Compiler variants, and the vast architecture of the Spirit Plane recovering slowly from two hundred years of damage.
"In my previous life," he said, "I was a backend developer. I worked alone. My code ran on servers that nobody else touched. When something broke, I fixed it. When something needed building, I built it. The codebase was mine."
"And here?"
"Here, the codebase is seven billion people and a living dimension. I can't maintain it alone. The architecture is too big. The user base is too diverse. The edge cases are literally killing people." He looked at the monitoring display. "Yara was right. This needs to be distributed. Not just the protocol. The entire approach to human-Plane interaction. Open source. Peer reviewed. Community maintained."
"You're describing an institution."
"I'm describing the future of Compiler science." He pulled up the team's shared codebase. Five authors. Dozens of modules. Reviewed, tested, deployed. "Tong built the Research Institute to study the Spirit Plane. We need something bigger. An international center for Compiler development. Where variants from every nation can train, develop, and contribute to the architecture that connects humans to the Plane."
"That's a significant proposal."
"It's a necessary proposal. The seed program is producing new variants every month. Without a central institution, they'll be absorbed into military programs like Yara was. Used as weapons instead of trained as engineers."
Sera wrote for thirty seconds. Closed her notebook. Opened it. Wrote more.
"I'll draft the charter," she said. "Dean Tong will co-sign. Chunwei can push it through Daxia's government channels. Jin Seong can bring Korea in."
"And the Coalition?"
"The Coalition just signed the Accord. They'll resist a new institution, but they'll participate if the alternative is being left out."
Nox nodded. The quiet evening continued. The monitoring display hummed. The Spirit Plane breathed its steady rhythm.
He was still a backend developer. The backend was just bigger now.
And for the first time in either of his lives, he wasn't working alone.
