"Too aggressive," Kwon said. "Remove the second clause."
Alex deleted the second clause. They'd been drafting the message for ninety minutes, and it was the fourteenth revision. The administrator communication protocol required formal code-layer syntax, a blend of natural language and System architecture commands that the original builders had designed for clarity across millennia. Writing in it was like composing a legal brief in a language you'd learned six months ago.
"Try this," Kwon said. He leaned over and typed a phrase in the overlay's composition field, his gestures precise and practiced. Four years of studying the protocol showed in the economy of his movements. "'Administrator Prime. We acknowledge receipt of your compliance protocol and the terms stated therein. As a registered administrator operating within the system's operational parameters, we request a formal review period to assess the orientation framework. The Administrative Charter, Section 3, provides precedent for independent evaluation prior to compliance commitment.'"
"'We,'" Alex said.
"The formal pronoun. Prime uses it exclusively. Matching his register signals respect for the protocol without signaling submission." Kwon deleted a word, replaced it. "The Charter citation is the important part. If he knows you've accessed the Charter, that changes his calculus."
"It tells him I've been in a node."
"He may already know that. The scout report includes energy signatures from the mountain approach. If his analysis is thorough, and Prime's analysis is always thorough, he's already identified the node's proximity to the engagement zone." Kwon sat back. "The Charter citation does two things. It tells him you have legal standing within the system's own framework. And it tells him you're not a rogue element. You're an administrator who has read the founding documents and is acting within their scope."
"Even if what I'm doing contradicts what he wants."
"Especially then. Prime does not respect compliance. He respects competence. An administrator who complies without understanding is a tool. An administrator who understands and then negotiates is a peer." Kwon paused. "He will not treat you as a peer. But he will recognize the posture."
Alex read the message again. Fourteenth revision. The language was careful, the tone calibrated somewhere between deference and assertion. Not groveling. Not challenging. The bureaucratic middle ground of someone who takes the institution seriously while disagreeing with its current management.
"Send it," he said.
Kwon ran the transmission protocol. The message entered the System's administrative communication layer, routed through channels that had been carrying messages between administrators since before recorded human history. The delivery was instant. The response would come when Prime chose to send it.
"Now we wait," Kwon said.
"Now we work." Alex closed the composition field. "Bridge exercises. I need to recover what I lost."
---
The exercises were worse at 51%.
Kwon's bridge calibration protocol was a series of controlled overlay activations, each one designed to stress the neural interface at a specific threshold, then release. Stress, release. Stress, release. The repetition was supposed to strengthen the bridge's capacity the way physical therapy strengthened a damaged tendon. Incremental loads, carefully managed, building tolerance over sessions.
At 58%, the exercises had been uncomfortable. The mental equivalent of stretching a sore muscle. Unpleasant but functional.
At 51%, the exercises were an argument with his own nervous system.
The first activation sent a spike through the back of his skull, behind his eyes, the specific kind of pain that came from hardware trying to run software it wasn't built for. The overlay flickered, stuttered, came up at half resolution. The code layer was readable but soft, like text seen through dirty glass.
"Hold it," Kwon said. He was monitoring Alex's bridge output on his own overlay. "Fifteen seconds. Then release."
Alex held it. Fifteen seconds of the dirty-glass overlay, the bridge complaining in frequencies that translated to headache and jaw tension and a faint ringing in his left ear. Then he released, and the overlay dropped back to passive, and the pain receded to a dull background hum.
"Again," Kwon said. "Twenty seconds this time."
They did twelve cycles over forty minutes. Each cycle slightly longer, slightly higher activation, the bridge being pushed to its current limit and then slightly past it, the damaged interface stretching against its constraints. Between cycles, Alex sat with his eyes closed and concentrated on the secondary channel. The 0.28% required more active attention at 51% bridge. What had been background maintenance was now foreground effort, the difference between carrying a bag on your back and carrying it in your hands.
"You're compensating," Kwon said, watching the readouts. "Your bridge output is uneven. The left hemisphere is running twelve percent higher than the right to cover the deficit."
"What does that mean?"
"It means the damage from the Watcher interference is asymmetric. The left bridge connection is intact. The right is degraded." Kwon adjusted something in his overlay. "The exercises need to target the right side specifically. Different protocol."
He switched to a variant Alex hadn't done before. The activations were the same concept but the load distribution was skewed, pushing harder on the weaker side, like doing single-leg squats on the injured leg. It was worse. Significantly worse. The pain behind Alex's right eye became a focused point, a hot nail driven sideways, and the overlay on that side went dark twice before stabilizing.
After the eighth cycle of the new protocol, Kwon checked the readings.
"Fifty-three percent," he said.
Two points. Forty minutes of work for two percentage points. The 58% he'd had before the Watcher interference had taken weeks of daily exercises to build. He'd need weeks more to get back there, if he could get back there. And every day of exercises was a day of limited overlay capacity, limited admin function, limited ability to do the work that needed doing.
"That's enough for today," Kwon said. "More will cause regression. The bridge needs rest between sessions."
Alex opened his eyes. The fieldwork station's ceiling was white and cracked and ordinary. He stared at it until the hot-nail pain faded to something manageable.
"Sera called," Kwon said.
Alex turned his head. Kwon was looking at his phone, not his overlay. His face was doing the thing it did when he was worried and didn't want anyone to know.
"When?"
"While you were in the eighth cycle. I didn't interrupt." Kwon set the phone down. "She's finished the documents."
"All forty-seven?"
"All forty-seven. In three days." He paused. "I estimated a week. She finished in three days and called to tell me she's already started independent work."
"What kind of independent work?"
"She's been experimenting with her code vision. Reading the fragments she can see in her daily environment, learning to distinguish structural code from operational code, building a personal taxonomy of what she's observing." Kwon's voice was neutral, but the concern was in the spaces between words. "She described it as 'teaching myself to read without a textbook.' She's using the forty-seven documents as a reference framework and mapping everything she sees against it."
"That's initiative."
"That's dangerous." Kwon folded his hands. "Unsupervised interaction with System code at the partial-visibility level creates risks. She can see fragments but not context. She can read individual words but not sentences. If she misinterprets a structural parameter as an operational command, or if she attempts to interact with code she can see but doesn't understand—"
"She draws Watcher attention."
"Or worse. She destabilizes something she doesn't realize she's touching. At her visibility level, the difference between observing code and influencing code is smaller than she thinks." Kwon looked at Alex. "She needs structured guidance. Bridge exercises. Supervised practice. The same progression you went through, but adapted for her access level."
"We don't have the bandwidth. You're running the prospective outreach, the administrative communications, my bridge therapy—"
"I know what I'm running." Kwon's voice tightened by a degree. Not anger. Frustration with constraints he'd already calculated and couldn't solve. "Sera is the first prospective who's shown this level of aptitude. She's also the first one who's shown this level of impatience. If we don't get someone to her within the week, she's going to teach herself something that costs us."
Alex sat up. The bridge ached. The channel hummed. The clock on Prime's window was at two days, give or take whatever the response to their message would do to the timeline.
"Can she come here?"
"To the fieldwork station?"
"If she's going to train, she trains here. Under supervision. You or me, whoever's available." He paused. "She also gets to see the operation. See the people. See the scale of what we're doing. That matters for the network we're building."
Kwon considered this. "The station's location is operationally sensitive."
"The station's location is already known to Wells, who has Association resources. It's known to Bug, Mira, Echo. If Sera is in the network, she's in the network." Alex looked at him. "You vetted her for two years. Is she in or not?"
"She's in." No hesitation. The concern wasn't about Sera's loyalty. "I'll arrange her travel. Tomorrow, if the Prime situation allows."
"Tomorrow."
Kwon picked up his phone and left the room. Alex heard him dial, heard the measured cadence of his voice through the wall, his prospective-outreach voice. Careful. Precise. Four years of practice at bringing people into a secret without breaking them or the secret.
---
Maya came in at 6:00 PM with food from the convenience store down the mountain road. Rice triangles, packaged kimchi, two cans of coffee. She set the food on the table and sat across from Alex.
"Fifty-three," she said.
"Kwon told you."
"Kwon tells me the numbers. I figure out what they mean." She opened a rice triangle. "Two points in forty minutes. At that rate, you're back to fifty-eight in two and a half weeks."
"If the exercises work consistently. Which they might not at this level of asymmetric damage."
"Kwon's good at what he does."
"Kwon's good at what he does," Alex agreed. "The bridge might not cooperate regardless."
Maya ate the rice triangle. She ate the way she did everything: fast, focused, no wasted motion. You learned to eat like that when meals happened between operational windows and skipping one meant going eight hours empty.
"The three cult members," she said.
Alex stopped reaching for the kimchi.
"Have you thought about it?"
"I've thought about it constantly."
"And?"
"And they're dead because I redirected a Watcher toward their equipment and they ran the wrong direction." He picked up the kimchi. "There isn't a version of thinking about it that changes the outcome."
"No." Maya looked at him. "But there's a version where you decide what it means for the next time."
"The next time I redirect a weapon?"
"The next time you make a decision that costs lives." She said it plain. No softening, no comfort. The delivery of someone who'd made those decisions herself and had come out the other side with a specific opinion about dwelling. "You said you can't do this alone. That's the lesson from the mountain. The question is whether you've actually changed how you operate, or whether you've just said the words."
He didn't answer immediately. She didn't push. They ate in the quiet of the fieldwork station, the secondary channel holding steady, the bridge at 53%, the mountain visible through the window in the fading October light.
"Sera's coming tomorrow," he said.
"Good. She's fast?"
"Faster than expected. Kwon's worried."
"Kwon worries about everyone who moves faster than his protocols." Maya finished her coffee. "That's his job. Your job is to decide whether fast is what we need right now."
"It's what we need. It's also what's dangerous."
"Same thing." She stood, collected the wrappers. "It's always the same thing."
---
Prime's response arrived at 11:42 PM.
Alex was alone in the back room, running the Archivist's passive monitoring while the rest of the team slept or worked in other parts of the station. The message came through the same administrative channel they'd used, the same ancient protocol, the same formal syntax.
He expected threats. He expected a shortened timeline, a demand for immediate compliance, the cold authority of an entity that had been maintaining order for ten millennia and didn't appreciate being cited the Charter by a nine-month-old administrator.
The message was four lines.
*"Admin_01.*
*Your invocation of the Charter is noted. Section 3 provisions are acknowledged.*
*We have a question, before the review period is formalized.*
*What did you find in Node Eleven?"*
Alex read it three times.
Prime wasn't threatening. Wasn't demanding. Wasn't escalating.
He was asking.
And the question wasn't about the interference, wasn't about the Watcher redirect, wasn't about the cult engagement or the standing wave or any of the operational details the scout report would have contained.
He was asking about the node. Specifically Node Eleven. By name.
Which meant Prime knew which node they'd accessed. Which meant the scout report was more detailed than Kwon had estimated, or Prime had other sources of information, or the node itself had reported the access through channels Alex hadn't detected.
And the question itself. *What did you find?* Not *why did you access it*. Not *by what authority*. What did you find. As if the answer mattered to him. As if there was something in that node that Prime wanted to know about.
Alex sat in the back room of the fieldwork station and looked at the message and tried to read the mind of a ten-thousand-year-old administrator from four lines of formal syntax.
*What did you find in Node Eleven?*
There were two possible readings. Either Prime was testing him, probing for how much he'd learned, mapping the scope of his knowledge before deciding how to respond.
Or Prime genuinely didn't know what was in Node Eleven. Nine thousand years of archived data, the complete Charter including the sections he'd suppressed, the consent architecture, the bridging protocol. If Prime had lost track of what his own nodes contained, if the system had grown beyond even his ability to monitor every component—
Alex closed the message. Opened it. Read it again.
He needed to talk to Kwon. He needed to talk to Echo. He needed to decide what to tell a ten-thousand-year-old being who had just asked a question that might, depending on the answer, be either a trap or an admission of ignorance.
Two days left on the clock. A question in the overlay. And somewhere in the System's deepest architecture, Prime was waiting to see how a nine-month-old administrator would answer.
