He went to the Watchtower immediately.
Minjae was at his primary panel with the expression he used when information had arrived that required a different framework than the one he'd been using, the specific look of someone whose analytical architecture was being rebuilt from the inside while they were still using it.
Junho came up the stairs and stood beside him and looked at the panel.
The log format reverse-engineering had produced a structural map of the system's backend architecture, rendered in the only visual language the forum's interface could support: a network diagram, nodes and connections, the system's internal components represented as points and the relationships between them as lines. Most of it was unremarkable — standard system functions, the lord management infrastructure, the territory assignment protocols, the forum's communication layer. Junho recognized the shapes of things he interacted with daily, now visible from the inside rather than experienced from the surface.
But in the center of the map, connected to everything and visually distinct from everything, was a cluster of nodes that the reverse-engineering had flagged in a different color.
Not because Minjae had colored them. The flagging was the system's own architecture distinguishing between its standard components and something else, the same way a body distinguished between its own tissue and something embedded within it.
"The correction protocol," Junho said.
"The correction protocol is here," Minjae said, pointing to a specific node cluster on the map's left side. "Standard architecture. Clear function. It's connected to the log access layer the way I expected — it reads the decision log to identify access points and closes them sequentially."
"And the center cluster."
"That's what I didn't expect," Minjae said. "The center cluster is also connected to the correction protocol. But not as a component of it. As a counterweight to it."
Junho looked at the center cluster. At its connections: running to the correction protocol on one side, to the lord management infrastructure on another, to the deep structure registration events on a third.
"The null sender," he said.
"The null sender's account structure matches the center cluster's architecture exactly," Minjae said. "The null sender is not a person using the system. It's one of those nodes. It's the system's own counterweight to the correction protocol sending messages through the forum's communication layer."
"Two opposing functions built into the same system," Junho said.
"Built in at the same time," Minjae said. "The architecture timestamps show they were implemented simultaneously. The correction protocol and the counterweight are the same age. Whoever built the system built both of them together."
Junho looked at the center cluster.
The system had been designed with a correction function to manage anomalous development. And it had been designed simultaneously with a function that opposed the correction, that sent warnings through the forum when the correction was activated, that pointed at the things the correction would try to reach.
"The system was designed to be contested," he said.
Minjae looked at him. "That's one interpretation."
"What's the other."
"The system was designed with a self-limiting function. Not a counterweight that opposes the correction but a monitor that ensures the correction operates within intended parameters." He paused. "The null sender's messages have warned you about Seojun's moves as much as about the correction protocol itself. If it were purely a correction monitor it would only communicate about system functions. The fact that it communicates about Seojun's backend access suggests it's monitoring more than just the correction protocol."
"It's monitoring everything that uses the system's architecture in ways that weren't intended," Junho said.
"Seojun's mark gives him access to the backend. That access is being used in ways the system didn't intend," Minjae said. "The null sender flags it the same way it flags the correction protocol's initiation."
Junho looked at the map.
"The correction protocol," he said. "You said the architecture is not what we thought. What did you mean."
Minjae moved to a section of the map he had annotated since calling Junho up.
"The correction protocol operates in two phases," he said. "Phase one is what the Ancestor described: closing access points sequentially, one function at a time, over eleven days. That's the visible phase."
"And the invisible phase."
"Phase two initiates simultaneously with phase one but operates on a different layer. It doesn't close the bloodline's access to the deep structures. It reclassifies them." He looked at the panel. "The third lord's territory looked complete from the outside because it was complete from the outside. The structures were still there. The lairs were still there. The units were still there. What changed was how the system categorized them."
"The bloodline was reclassified as a growth talent," Junho said. "The deep structures were categorized as standard territory buildings. The correction didn't destroy anything. It renamed it."
"And renaming changed the lord's relationship to what they'd built," Minjae said. "The territory was the same. The lord's access to its Pre-System functions was gone because the functions had been categorized as standard system functions, and standard system functions don't respond to Pre-System bloodline frameworks the same way."
Junho sat down.
The Rank B advancement had given him a clarity of perception that Rank C hadn't provided, and he was using it now to hold the full weight of what Minjae was describing without the usual instinct to begin solving it before he'd finished understanding it.
The correction didn't close. It renamed.
Which meant the reversal — the keeper's push from outside and the lord's hold from inside — wasn't fighting against closed doors. It was fighting against a reclassification protocol. Arguing the system back into recognizing what the bloodline and the deep structures actually were rather than what the correction had categorized them as.
A semantic battle fought at the level of the system's own architecture.
"The Gwansuju's function," he said. "Han Sorim said the keepers survived the correction with their function intact because the correction protocol couldn't close what wasn't open in the same way. She meant the keepers' function is categorical, not access-based. It doesn't open doors. It defines what constitutes a threshold."
"If the correction reclassifies the deep structures as standard buildings," Minjae said slowly, "the Gwansuju's threshold function could argue the reclassification is invalid because the structures meet the definition of threshold spaces regardless of what the system calls them."
"The keeper defines what a threshold is. The correction protocol can't overwrite a definitional function with a reclassification because definition precedes categorization."
Minjae looked at him. "That's — that's the mechanism. The record chamber's keeper documentation was telling Han Sorim that her function is definitional, not reactive. She doesn't fight the reclassification. She defines the thing being reclassified in terms the correction protocol has to accept."
"Because the Gwansuju predates the system," Junho said. "Its definitions are Pre-System. The correction protocol is a system function. Pre-System definitions have priority over system reclassifications in the architecture."
He looked at the structural map on the panel.
The center cluster — the null sender — had connections to the correction protocol that he now understood differently. Not opposition and not monitoring. Something more precise: the null sender was the architectural record of the system's own acknowledgment that Pre-System frameworks had priority over system functions in cases of definitional conflict.
The system had been built by someone who knew that Pre-System things existed and had built in a function that protected Pre-System definitional priority from system override.
And then had also built the correction protocol, which targeted Pre-System bloodlines.
"Two people built this system," Junho said.
Minjae looked at him.
"The correction protocol and the counterweight aren't opposing functions built by one designer with competing goals," Junho said. "They're two different designers' work, integrated into the same system. One built the correction. One built the protection against it."
"Seojun's mark and your bloodline," Minjae said quietly. "If the system was built by two people — one who wanted to manage anomalous Pre-System development and one who wanted to protect it —"
"Then Seojun's mark is the correction designer's legacy," Junho said. "And the Cheoksa bloodline is the protection designer's."
The Watchtower was quiet.
Outside, the marsh ran its constant indifferent sound.
"There's one more thing," Minjae said. He moved to a different section of the annotated map. "The correction protocol's phase two — the reclassification. I found the trigger condition for its initiation."
"The forty-two day countdown," Junho said. "From the Dokkaebi Grove's self-activation."
"That's the trigger for the preparation phase," Minjae said. "The correction protocol preparation is a system function. It prepares the reclassification architecture for deployment." He pointed to a specific node on the map. "The initiation trigger — when the preparation deploys into active correction — is different."
"What is it."
Minjae looked at the node.
"The Sovereign Games," he said. "The correction protocol initiates when the lord registers for or participates in a system-wide event that creates an anomalous development comparison point. The Games' ranking function requires the system to formally assess all participants against standard development parameters. When Blackfen is assessed against standard parameters, the anomaly classification triggers the correction."
Junho looked at the panel.
"I registered for the Sovereign Games four hours ago," he said.
"Yes," Minjae said. "The eleven-day window the Ancestor described — it was based on the assumption that registration would happen within the preparation phase's remaining window." He paused. "The registration already happened. The correction protocol's active phase may initiate faster than eleven days."
"How fast."
Minjae looked at the map.
"The preparation phase has to complete before initiation. Based on the architecture, the preparation has approximately — "
He stopped.
His panel updated. Not from the forum. From the system's own notification layer, the kind that overrode all other displays and appeared whether requested or not.
One line.
"Cheoksa Bloodline — System Assessment initiated. Correction Protocol: active."
Junho looked at the notification.
The Ancestor had said eleven days.
The registration had accelerated it.
The correction protocol had initiated twelve minutes after he had consciously decided to face it, and it had begun while he was in the Watchtower understanding exactly what it was going to do.
He felt the first access point close.
Not the deep structures. Not the resonance link. Something at the outermost edge of the bloodline's framework, where the Ancestor's addition had been placed, where Han Sorim's Gwansuju had stabilized during the advancement.
The correction protocol had found the outermost layer.
And the outermost layer was holding.
The Ancestor's protection was doing exactly what he had told Han Sorim it would do: buying the first day. Possibly the second. The correction was pressing against the outermost layer and the layer was not closing.
He felt through the newly advanced Rank B resonance the quality of that resistance: steady, deliberate, the absorbed-light warmth of the relic's integration holding the outermost boundary against the system's reclassification pressure.
"Day one," he said.
"Is it holding," Minjae said.
"Yes."
"How long."
"Long enough," he said.
He stood up.
The proxy attack was sixty-two hours away. The summit was sixty-eight. The correction protocol was active and being held at the outermost layer by the Ancestor's protection. The Gwansuju reversal couldn't initiate until the correction reached a layer Han Sorim's function could define.
He needed to tell Han Sorim the correction had started.
He was moving to the Watchtower stairs when the Dokkaebi appeared at the upper level's entrance, which required it to have climbed the exterior of the Watchtower rather than the interior stairs, which was the kind of thing the Dokkaebi did without announcement.
It was holding its piece of deadwood. Its bright eyes were on him with a quality that was different from its usual observational register — more directed, less amused, the ancient awareness focused rather than distributed.
"The correction has started," it said. Not in his grandmother's voice. Not in the in-between voice it had used when it wasn't performing grandmother. Something that was its own voice, finally, older than either.
"Yes," he said.
"Good," the Dokkaebi said.
He looked at it.
"Good," he said.
"The correction starting means the counterweight activates fully," it said. "The null sender has been operating at partial function since world fusion. When the correction protocol goes active, the counterweight goes active at the same level."
"The null sender becomes more active," he said.
"The null sender becomes something more than a sender," the Dokkaebi said.
It looked at the map on Minjae's panel. At the center cluster. At its connections running in every direction through the system's architecture.
"The person who built the counterweight," Junho said. "You know who it was."
The Dokkaebi looked at him with its ancient eyes.
"We know many things," it said. "We've been waiting for you to ask the right questions."
"Who built the counterweight," he said.
The Dokkaebi tilted its head.
"The third lord," it said. "In the eleven days after the correction was applied. While they were losing access to the deep structures one function at a time, they were using the access they still had to build something into the system that would help the next sufficient carrier."
Junho looked at the center cluster on the map.
"The third lord built the null sender into the system," he said. "While the correction was taking everything from them, they used what remained to build a protection for whoever came after."
"Yes," the Dokkaebi said.
The Watchtower was very quiet.
"Why didn't you tell me this before," he said.
"You asked who built the correction," the Dokkaebi said. "You asked about the dual mark. You asked about the preparation phase. You asked about the Ancestor." It tilted its head the other way. "You never asked who built the counterweight until now."
He looked at it.
"What does the counterweight becoming fully active mean," he said. "Concretely."
"It means," the Dokkaebi said, "that somewhere in the system's architecture, the third lord's final eleven days of work are about to do what they were built to do."
"Which is."
The Dokkaebi looked at the eastern horizon. At the direction of Highland Dominion's boundary.
"Contact the person who built the correction," it said. "Through the only channel that exists between the system's two designers."
"Seojun," Junho said.
"Not Seojun," the Dokkaebi said. "Seojun carries the correction designer's mark the same way you carry the protection designer's bloodline. The mark and the bloodline are the contact points."
It looked at him.
"The third lord's counterweight is going to send a message," it said. "Through the system's architecture. From your bloodline to Seojun's mark. A message the third lord composed eleven days before they died."
"To Seojun."
"To whoever carried the correction designer's mark when the counterweight activated," it said. "The third lord didn't know who that would be. They wrote it for the mark, not the person."
Junho looked at the eastern horizon.
"What does the message say," he said.
"We don't know," the Dokkaebi said. "We can observe. We can't read what was written between the two frameworks."
His panel updated.
Not a system notification. A private message. From an account he had never received a message from before, with a territory name he recognized, with a faction tag that was Highland.
From Lee Seojun.
Three words.
"What did you send?"