Sovereign of Fortune

Chapter 89: Phase 3

Quick Verification

Please complete the check below to continue reading. This helps us protect our content.

Loading verification...

"What part?" he said.

Wei Ruoxi looked at the table. "The part about what happens after Phase 2."

He waited.

"He asked me a specific question," she said. "He said: when Phase 2 completes and the Level 5 threshold is crossed — what happens to the nodes? Not to the primary beneficiary. To us."

He thought about this. He thought about Song Meiqi in Haixia, running her observer function from a port district apartment. Zhou Shuyan in Fengliu, running fast tasks under the threat of periodic monitoring. Wei Ruoxi herself, facilitating connections on behalf of a design she hadn't chosen.

"What does the system tell the nodes about their endpoint?" he said.

"Mine doesn't describe one," Wei Ruoxi said. "The task assignments keep coming. The system says I'm building something. It doesn't say what I get when it's built." She looked at him. "Song Meiqi asked me the same thing, when we talked last month. She said the observer function is permanent, as far as she can tell. No term. No completion condition."

"The nodes have their own task rewards," he said. "Their own LP, their own cultivation packages."

"Yes," she said. "And those are real. I'm stronger than I was eighteen months ago because of what the system has given me. I'm not saying the network has been bad for us." A pause. "I'm saying Xu Mingzhi's question was specific and I don't have an answer to it."

He sat with this.

The question was: what comes after Phase 2, for the nodes?

His system had documents for Phase 1 and Phase 2. Phase 3 had been mentioned once — in the note that said the second party had been watching. He'd read that note and not returned to it.

He opened the system.

```

[QUERY: PHASE 3. WHAT IS IT. WHAT HAPPENS TO THE NODES AFTER PHASE 2 COMPLETION.]

```

The system took longer than usual to respond. Twelve seconds, which was long.

```

[PHASE 3: ARCHITECT'S DOCUMENTATION IS PARTIAL. THE FOLLOWING IS AVAILABLE.]

[PHASE 3 DESCRIPTION: CONVERGENCE. THE SEVENTEEN NODES, HAVING COMPLETED PHASE 2 AGGREGATE FUNCTIONS, TRANSITION FROM DISTRIBUTED TASK COMPLETION TO COLLECTIVE OPERATION.]

[IN PRACTICAL TERMS: THE NODES' TASK ASSIGNMENTS SHIFT FROM INDIVIDUAL FUNCTION TO COORDINATED NETWORK FUNCTION. THE SOCIAL FACILITATION NODE, THE OBSERVER NODE, AND THE TASK SPECIALIST NODES BEGIN OPERATING TOWARD A SHARED OBJECTIVE RATHER THAN INDEPENDENT LOCAL OBJECTIVES.]

[THE PRIMARY BENEFICIARY'S ROLE IN PHASE 3: COORDINATOR AND OPERATIONAL LEAD, NOT SOLE BENEFICIARY. THE LP ACCUMULATION STRUCTURE CHANGES — AGGREGATE NODES ACCUMULATE LP INDIVIDUALLY, NOT JUST FOR THE PRIMARY BENEFICIARY'S AURA DEVELOPMENT.]

[NOTE: XU MINGZHI'S ASSERTION THAT THE ARCHITECT OMITTED PHASE 3 IS INCORRECT. IT IS DOCUMENTED. IT IS NOT ACTIVATED UNTIL PHASE 2 COMPLETES.]

[NOTE: XU MINGZHI HAS READ THE THEORETICAL FRAMEWORK. HE HAS NOT READ THE ARCHITECT'S COMPLETE DESIGN DOCUMENTATION. HE IS BUILDING AN ARGUMENT FROM AN INCOMPLETE PICTURE.]

[NOTE: THE SYSTEM RECOMMENDS SHARING THIS INFORMATION WITH THE NODES WHO ARE CURRENTLY UNCERTAIN.]

```

He read it twice. Then he showed Wei Ruoxi.

She read it. The tiredness of the past nine days didn't disappear, but it organized itself differently — she sat straighter, read it again from the beginning.

"Phase 3 exists," she said.

"The architect designed it," he said. "Xu Mingzhi read the theoretical paper — probably his own paper, given the framework match — and concluded the architect only built Phases 1 and 2. He didn't have access to the deployment documentation."

"He was wrong," she said.

"He was working from incomplete data," he said. "And drawing reasonable conclusions from it."

She looked at him. The careful note in her expression — she was parsing something. "That's not the same as dismissing the concern," she said.

"No," he said. "It isn't."

The concern was real. Even if Phase 3 existed, even if the architecture included redistribution — twelve or eighteen months of not knowing that, running tasks without knowing what the endpoint was, was a legitimate grievance. The system hadn't told the nodes about Phase 3 any more than it had told them about Phase 1.

"Song Meiqi should see this," he said.

"Yes," Wei Ruoxi said. "And Zhou Shuyan."

"All the nodes," he said. "The design isn't hiding from them — it's hiding because the architect's information structure is sequential. But there's no reason to hold Phase 3 back now." He looked at the system note again. *The system recommends sharing this information with the nodes who are currently uncertain.* "The system is already recommending it."

Wei Ruoxi was quiet. Then: "Xu Mingzhi. He's been building his monitoring architecture for six years because he thought the nodes were being exploited. He made a case to me based on that belief. What happens now?"

He thought about Xu Mingzhi — sixty-three years old, pre-Awakening cultivator, watching the architect's design develop from the outside for six years with an incomplete picture. The Remnant Institute, the monitoring layer, Liu Qiaoyun's information retrieval work. Six years of patient architecture built on a wrong premise.

"He has to know the premise is wrong," Chen said.

"You're going to tell him."

"I'm going to show him the same documentation I just showed you," he said. "He can verify the framework himself. He built the theoretical paper — he can read the system's Phase 3 documentation and recognize its derivation from his own work."

"And when he knows he was wrong?" Wei Ruoxi said.

"Then we find out what he actually wants," Chen said. "If Phase 3 is his concern and Phase 3 exists — the concern is resolved. What remains is the monitoring architecture he built and what he intends to do with it."

She looked at him steadily. "He's been slowing Phase 2. He believed he was protecting us."

"He caused real costs," Chen said. "The network's quiet period has delayed the Level 5 timeline by weeks. Song Meiqi, Zhou Shuyan — they've been managing threat posture for months because of his monitoring." He paused. "But the motivation wasn't malicious. That's different from an enemy."

"You sound like you're deciding how to approach a negotiation," she said.

"I am," he said.

She sat for a moment. Then: "He'll want to meet you."

"I know."

"Liu Qiaoyun will be there too."

"Good," he said. "I want to see her."

---

He left the tea house at six PM and messaged Song Meiqi, Zhou Shuyan, and Wei Ruoxi simultaneously with the Phase 3 documentation. The system notification, the architect's partial design documentation, the description of what came after Phase 2.

Song Meiqi's response came first, in forty minutes: *I knew it. I knew there was a Phase 3. The observer function never felt like a permanent arrangement.* A pause. *This changes how I've been thinking about the endpoint.*

Zhou Shuyan an hour later: *The convergence phase. Coordinated operation. I have questions about what "shared objective" means at the operational level.* She had always been the most practically minded of the three.

He wrote back: *The shared objective isn't defined yet. That's the Phase 2 completion condition's task — when the network aggregate reaches the Level 5 threshold, the convergence design activates and the objective becomes clear. Until then, Phase 2 continues.*

Zhou Shuyan: *So we're still running tasks for your Level 5 threshold.*

*Yes,* he wrote. *That's Phase 2. Phase 3 is what comes after.*

She didn't respond immediately. He imagined her in the Fengliu apartment, thinking through the calculus. The six weeks of careful task management, the threat posture, the fast runs. All of it in service of a Phase she hadn't known existed.

She wrote back: *Tell Xu Mingzhi I'm not interested in his Institute. I'm staying.*

He noted this. Filed it. The specific quality of someone who'd been waiting for the answer and, having gotten it, was done weighing options.

---

The next question was how to approach Xu Mingzhi.

Not aggressively — the man wasn't an adversary, he was a concerned observer who'd built a significant monitoring infrastructure on a wrong premise. If Chen moved on him institutionally before giving him the corrected information, it would be a mistake. An error of sequence.

He thought about how to make the contact.

Not through Liu Qiaoyun directly — Liu Qiaoyun had made contact with Wei Ruoxi, which meant she had an existing channel. But using Wei Ruoxi's channel put Wei Ruoxi in the middle of a negotiation she shouldn't be positioned in.

Not through the Vanguard's institutional weight — that would read as a threat rather than an information exchange.

Through the system.

He opened the system shop. The information category. Checked whether there was an item relevant to establishing contact with a specific individual outside the existing network.

```

[AVAILABLE: SECURE CHANNEL ESTABLISHMENT TOKEN — ALLOWS OPENING A VERIFIED COMMUNICATION CHANNEL WITH A SPECIFIC PARTY, ROUTING THROUGH THE SYSTEM'S DEPLOYMENT MECHANISM. THE RECEIVING PARTY WILL KNOW THE CHANNEL COMES FROM THE SYSTEM. COST: 2,000 LP]

```

The channel routes through the deployment mechanism. Xu Mingzhi had built six years of architecture to monitor that mechanism. A message arriving through the mechanism's channels would not be ignorable — it would be, to him, like receiving a call on a phone he'd been tapping. He would understand immediately what it was.

Chen purchased the token.

```

[SECURE CHANNEL ESTABLISHED]

[RECIPIENT: XU MINGZHI — REMNANT INSTITUTE, EASTERN DISTRICT]

[CHANNEL STATUS: ACTIVE — AWAITING MESSAGE]

```

He typed:

*You've been watching the network for six years. You read the theoretical paper correctly but the deployment documentation is incomplete on your end. I have the Phase 3 documentation. I want to meet.*

He sent it.

Then he sat in the quiet of the evening and thought about what came next.

The second party's trigger condition — the formation aggregate visible at formation-grade sensors — had been acknowledged by Liu Qiaoyun via Tan Xueying's preliminary report. Tan Xueying's modified final report would buy a week or two. In that window, Xu Mingzhi would either meet with Chen or he wouldn't.

If he met: the picture could be completed. The monitoring architecture could be addressed from a position of information rather than opposition.

If he refused: the Vanguard's institutional weight was the next option. Not comfortable, but available.

He thought there was a reasonable probability Xu Mingzhi would meet. A man who'd spent six years building a case based on his own theoretical paper would want to see the counter-documentation.

The system's secure channel notification came back in forty minutes:

*Where.*

---

Sunday morning.

He walked to the eastern district meeting point — a cultivators' reading room in a private research library, the kind of space that existed in cities with large pre-Awakening cultivation communities. Old books behind glass cases. Qi-adjusted air. The smell of stored paper and something that was almost incense but wasn't quite.

Xu Mingzhi was already there.

Sixty-three looked like it fit him — the kind of sixty-three that came from decades of cultivation practice, the body lean and maintained, the qi signature dense in the way of pre-Awakening practitioners who'd built their base long before the event supercharged it. B-rank combat equivalent without any system ability. Just cultivation.

Liu Qiaoyun was beside him. Mid-forties, professional bearing, the qi signature of someone whose awakened ability was purely informational rather than physical. She'd read the building inspection report before anyone knew Tan Xueying had the preliminary survey data in her hands. She was very good.

"You're younger than I expected," Xu Mingzhi said.

"You're more patient than I expected," Chen said.

Xu Mingzhi looked at him for a moment. "Sit down."

They sat. The reading room, quiet. The three of them.

Liu Qiaoyun watched him with the specific attention of someone reading an object for its history. Her ability — she couldn't use it on him directly, he assumed; it required physical contact with documented media. But old habits of observation ran in the body regardless of ability.

"The Phase 3 documentation," Xu Mingzhi said.

Chen set his phone on the table with the system notification displayed. The Phase 3 description. The architect's partial design documentation. The convergence phase.

Xu Mingzhi read it. He took his time. Liu Qiaoyun read it over his shoulder.

When he finished, he sat back in his chair. He didn't say anything for a long time.

"The convergence model," Xu Mingzhi said. "Coordinated operation. Independent LP accumulation for the nodes."

"Phase 3 exists," Chen said. "It activates when Phase 2 completes."

"I read my own theoretical paper," Xu Mingzhi said. The first note of something complicated in his voice. "I recognized the derivative when I saw the network's behavior. I concluded the architect had taken the Phase 1 and Phase 2 framework and built without the redistribution." He paused. "I was wrong."

"You built an argument from an incomplete picture," Chen said.

Xu Mingzhi looked at Liu Qiaoyun. Something passed between them — the specific exchange of people who've invested years in a project and are recalibrating against new data.

"Six years," Liu Qiaoyun said quietly. Not to Chen. To Xu Mingzhi.

"Six years watching what I thought was an exploitation architecture," Xu Mingzhi said.

"It wasn't," Chen said.

"No." He sat with this for a moment. "The nodes — they've been experiencing consequences of the monitoring architecture I built. The second party pressure. The quiet periods."

"Yes," Chen said.

"Song Meiqi," he said. "She's been running dark in Haixia for a week. I know because my architecture tracked her signature going silent."

"She's back online," Chen said.

Xu Mingzhi looked at his hands. The cultivation base at B-rank equivalent, the decades of development — the hands of someone who'd spent forty years building something patient. "I owe an apology to people I've never met."

"That's later," Chen said. "Right now I need to understand what you want to do with the monitoring architecture."

Xu Mingzhi looked up. "Dismantle it," he said. "If Phase 3 is documented, the argument for monitoring is gone."

"The access Liu Qiaoyun built," Chen said. "The parasitic layer on the deployment mechanism. Can it be removed cleanly?"

"Liu Qiaoyun built it," he said. "She can remove it."

Liu Qiaoyun nodded once. "It will take a week. The access architecture is layered — removing it needs to happen in sequence or the mechanism will flag the interference."

"One week," Chen said.

"Then the monitoring layer is gone," she said. "The formation specialist surveys — I'll pull Tan Xueying off the project today. Her final report was already submitted."

He noted the precision. She knew about Tan Xueying's report. She was ahead of him on that detail by a day, at minimum.

She smiled — brief, dry. "I'm an information specialist. The report arrived at my analysis station this morning. The field coherence degradation explanation was technically plausible." A pause. "Someone advised her well."

He looked at her. "You knew the report was modified."

"I suspected," she said. "The data pattern in the coherence degradation didn't match the Phase 2 elevation signature I'd been tracking. Close, but not clean." She looked at him directly. "I was going to question it Monday."

"What changed?" he said.

"Your message," she said. "When a message arrives through the system's deployment mechanism directly, the calculation changes. Someone who can use the mechanism to send secure messages has a relationship with the design that makes the rest of my analysis secondary."

He sat with this. Liu Qiaoyun — information retrieval ability, system-level access, twelve years of Bureau intelligence work. The kind of practitioner who'd read Tan Xueying's modified report and caught the inconsistency but waited to see what moved next.

Not an adversary. An analyst.

"The monitoring architecture," he said. "One week to remove it cleanly. During that week, the formation specialist surveys are stopped and Liu Qiaoyun's access stays passive — reading only, no data queries that would change the node signatures."

Xu Mingzhi and Liu Qiaoyun looked at each other. Then: "Agreed," Xu Mingzhi said.

"After the week," Chen said, "I want to introduce you to Song Meiqi. The observer. She's been watching the network's development from inside — she has a picture of what it's building that neither of you have."

"The architect's design from the observer's view," Xu Mingzhi said.

"Yes," Chen said. "You have the theoretical framework. She has the operational picture. Together they're more complete than either."

Xu Mingzhi looked at him steadily. "You're proposing a different relationship than I expected from this meeting."

"You spent six years watching the network because you thought it was worth protecting," Chen said. "The concern was wrong but the attention was real. That's useful."

"You want the Remnant Institute's research capacity," Liu Qiaoyun said.

He looked at her. "Your ability to read documented records through proximity contact. Xu Mingzhi's theoretical framework on probability field dynamics. The infrastructure you built for six years of patient monitoring." He paused. "Yes."

She held his gaze for a long moment. The reading running — not the ability, which needed physical contact with media, but the trained observation habit she'd built over two decades.

"One week," she said finally. "We remove the monitoring architecture. Then we'll have the conversation about what comes next."

He agreed.

---

He left the eastern district reading room at noon and sent Song Meiqi, Wei Ruoxi, and Zhou Shuyan a summary of the meeting.

Song Meiqi's response was immediate: *He built six years of monitoring architecture because he was worried about us. And he was wrong. That's the most productive misunderstanding I've ever heard of.*

Wei Ruoxi: *The Remnant Institute's resources could be useful. If Liu Qiaoyun cleans up the monitoring access, does that leave her with nothing? She'd be bringing skills and no function.*

He thought about this. *That's the conversation for later.*

Zhou Shuyan didn't respond for several hours. When she did: *I ran my fourth clean task today. The second party's monitoring layer was passive all week. I think they've already started the removal.*

He checked the system.

```

[MONITORING ARCHITECTURE STATUS: PASSIVE — ACTIVITY LOG ACCESS SUSPENDED]

[NOTE: XU MINGZHI HAS MOVED BEFORE THE ONE-WEEK MARK. HE BEGAN SUSPENDING THE ARCHITECTURE'S ACTIVE FUNCTIONS DURING THE MEETING.]

[NOTE: THIS IS CONSISTENT WITH A PARTY OPERATING IN GOOD FAITH ONCE THE CORRECT INFORMATION WAS PROVIDED.]

[NOTE: NETWORK NODES MAY RESUME FULL TASK COMPLETION ACTIVITY.]

```

He sent the all-clear to the nodes.

Then he opened the system shop and looked at the cultivation acceleration items available at B-rank.

The S-rank gap remained. Lin Zhengyue on the horizon, MQ3 just unlocked, the distance measured in months and work.

He noted this. Filed it. The current arc was not Lin Zhengyue. The current arc was completing, and what came after would need him at a specific threshold.

He bought two cultivation acceleration nodes and began planning the next phase.