Director Hao ran the security committee session at 9 AM Monday.
Chen Haoran arrived at the Vanguard's sixth floor — the committee's working floor, distinct from the executive council's fifth floor — and found seven committee members and one recording secretary. The formal tone was closer to an audit than a council session. Hao had that quality: he ran processes correctly, which meant neither more nor less than the process required.
"We've reviewed the consultation request and the supporting documentation," Hao said. "The committee's scope is ability assessment relative to institutional security. The consultation cited unclassified ability type concerns. Standard process."
"Understood," he said.
"The National Bureau has provided a preliminary field characterization report," Hao said. "Seven-day baseline, conducted by Director Han's division. It's been accepted as the technical basis for this session."
Han Weiwei's seven days of measurement data, delivered before the committee needed to ask for it.
He noted this.
"Tell us what your ability does," Hao said. Not aggressively — factually. The same tone he used for every other procedural question.
He said: "The probability field I generate shifts outcomes within its radius toward favorable variance. The effect is passive and continuous — I don't activate it or direct it. It runs at what would be called ambient, if that term applied to an active field." He paused. "The field's effect on others is that their mistakes open at worse moments, their plans encounter friction, and resources appear for me at useful times. The field doesn't create ability in me directly. It adjusts the probability weighting of events."
"Is it controllable?" one committee member asked.
"The output level varies with my cultivation tier," he said. "As my base cultivation increases, the field's effect radius and intensity increases proportionally. In that sense, it's as controllable as any ability that scales with cultivation — which is to say, I can slow the scaling by not cultivating, but I can't selectively reduce it in a given moment."
"The Bureau's characterization report supports this description," Hao said, reading. "The field is classified as generative-passive with environmental influence profile."
"That's accurate," he said.
Hao looked at the committee. No one had a follow-up. Hao looked at the report again.
"The consultation request named a source — Lin Meiyao, third division, A-rank," Hao said. "Committee policy: named sources in consultation requests are offered the opportunity to submit a statement if they choose. The committee does not compel submission."
"Did she submit?" he said.
Hao looked at him. "She submitted. You'll have a copy — it's part of the public record."
He hadn't known she'd submitted. He'd been holding open the question of what she'd do.
He kept his face even.
"The committee will circulate the statement," Hao said. He turned to the recording secretary. "The session is complete. Chen Haoran, the committee will issue its formal finding within forty-eight hours."
Standard timeline. Clean process.
---
He read Lin Meiyao's statement in the car outside.
It was short. Three paragraphs.
The first paragraph established her prior relationship — two years, ending approximately two years ago, before his system activation. Professional context: she was now a third division Vanguard operative, A-rank, no operational overlap with Chen Haoran's succession role.
The second paragraph addressed the knowledge question. She had known Chen Haoran before his awakening event response. She had no knowledge of his current ability type beyond what was available in the Vanguard's operative files. She could not speak to his current operational capacity or ability mechanisms.
Third paragraph: *I am aware that my name was included in this consultation request without my prior knowledge or consent. I'm submitting this statement voluntarily. I have no information relevant to the committee's security assessment that is not already contained in the operative files.*
That was all.
No mention of Fang Junhao. No emotion. No additional detail.
Three paragraphs, clean and precise, withdrawing herself from the process without making it a confrontation.
He sat with this for a moment.
She understood exactly what Fang had done with her name and she had responded the only way that removed herself from the situation without creating new problems. The pragmatic calculation: the statement reduced the consultation's utility to Fang without requiring her to take a position that would create friction in the relationship.
Smart. Careful. Exactly how she operated.
He filed this and put the phone away.
---
Mao Yingjie sent her pattern search results at noon.
*The fast-connection profile — I found three candidates in the Vanguard's extended network matching your search parameters. Two I can dismiss: one has a social ability type that naturally generates high connection rates, one is a known professional networker who runs an event facilitation business.*
*The third is more interesting.*
*Female, twenty-eight. Registered in the city six months ago — address in the Northern District. She runs a small consulting practice — listed specialty is "professional coordination," which is a category broad enough to be almost meaningless as a descriptor. She has no faction affiliation. Her ability type, per the public registry, is listed as "social facilitation" — a C-rank classification that generates positive emotional impressions and reduces interpersonal friction in face-to-face interactions.*
*The ability is real — it's a known classification. But the rate at which she creates lasting connections is an order of magnitude above what C-rank social facilitation typically produces.*
He read the profile.
Social facilitation at C-rank. Connection-building that outperformed the ability's expected parameters by an order of magnitude.
She had a legitimate ability type. And a system that was probably doing the heavy lifting.
*The consulting practice,* he sent. *Client list?*
*Publicly available: three corporate clients, two individual practitioners, one consortium-adjacent organization.* A pause. *The consortium-adjacent client is Bai Qingmei's compliance consultancy.*
He read that twice.
The city node had been working with Bai Qingmei.
The Hengyu compliance situation. The documentation he'd provided, the Consortium filing. And somewhere in that process — or before it — Bai Qingmei had engaged a professional coordinator whose system was designed to build connections.
Who had Bai Qingmei connected to in the past six months?
He sent: *The consulting practice — name?*
*Listed as Lingyuan Professional Services,* Mao Yingjie sent. *The principal is named Wei Ruoxi.*
Wei Ruoxi. The city node.
*Do you have a direct contact method for her?* he sent.
*She has a listed office in the Northern District and a professional contact address,* Mao Yingjie sent. *No personal number on public record. But her professional contact address is real — I've confirmed the office exists.*
He made a note of it and sat with the shape of things.
Wei Ruoxi, twenty-eight, six months in the city, running a consulting practice with a social facilitation ability and a system that was generating connections at ten times the ability's expected rate. Working with Bai Qingmei. Building a web in the Vanguard's extended network.
He had identified her. He hadn't made contact.
He could send Mao Yingjie's analysis to Song Meiqi and ask her to cross-reference with the observer feed, confirming the match. That would close the identification loop.
But he was also curious about meeting her directly and seeing what happened when two system holders with adjacent functions were in the same room.
The probability field's Level 4 assessment: he was going to encounter her within the next week. He was certain enough of this to not manufacture the meeting artificially.
He waited.
---
The security committee's finding came in forty-six hours, two hours ahead of schedule.
*The committee finds that the consultation request's stated concern — unclassified ability type as institutional security risk — is not supported by the evidence submitted. The field characterization report documents an ability type with environmental-influence characteristics that are passive and scalable with cultivation tier. No active threat profile is identified. The ability type has been reclassified from "unclassified-exceptional" to "probability field influence, generative-passive, registered." The consultation is closed.*
A new classification. Not the committee's subcommittee inquiry that Zhao Dequan had wanted — a full security committee finding with a formal reclassification.
The finding was better than he'd planned for. The security committee had, in addressing Fang's consultation, resolved the Zhao Dequan inquiry's underlying question simultaneously. There was no longer an open classification matter because the committee had issued a formal finding.
He sent Ye Shuangyu: *The committee finding.*
*I saw it,* she sent. *Director Hao ran a clean process.* A pause. *Fang's play closed the classification question faster than Zhao Dequan's subcommittee would have. He handed you a resolution.*
He hadn't fully considered this angle. Fang had maneuvered him into a security committee process that had resolved the outstanding classification matter with a formal finding — a stronger resolution than the administrative inquiry would have produced.
The near-deterministic outcome in his favor. Not through his planning. Through Fang's miscalculation.
He sent: *Six days.*
She sent: *Six days.*
---
The Thursday session that week ran later than usual.
Song Meiqi had sent three updates since Tuesday. The city node — Wei Ruoxi — had run seven connection tasks in four days. The northeast node — Fengliu — was running consistently. Two other nodes in distant cities had crossed a milestone: main quest approach phase initiated for the first time.
The network was, in aggregate, accelerating.
He laid this out for Han Weiwei at the start of the session. She listened without interrupting. When she received data she didn't already have, she went still — not the stillness of someone waiting for their turn to talk, but the kind that meant the calculation was actually running.
"Seventeen nodes," she said, when he finished. "Sixteen active. One approaching a main quest threshold. Two crossing milestones. The network is coming online after eighteen months."
"The architect's timeline," he said. "He built in a development period."
"You said the design ran ahead of projections at every node," she said. "Including you."
"Song Meiqi confirmed it," he said. "All sixteen active nodes have outperformed the design model."
She was quiet. The field characterization equipment in the corner running its session cycle — this was week three of the formal characterization, the data building into a substantial record.
"The architect's reaction to outperformance," she said. "He's been watching this through Song Meiqi's feed. If the nodes are running ahead of projection—"
"He may have accelerated something on his end," he said.
"Or nothing," she said. "If his patience is calibrated for twenty years, running five percent ahead doesn't change his calculation."
"It might change his timeline," he said.
She looked at him. "You're worried about his timeline."
"I'm noting I don't know it," he said.
She turned to the measurement data from the current week's session. "The probability field has a different texture than last week," she said. "Slightly higher variance at the edges, not just the center. The change is small but consistent across three days of measurement."
He looked at the graph. "The network activity," he said. "More nodes active is more fields active."
"They're distributed across the country," she said. "Your field shouldn't be registering their activity at this range."
He thought about this. The Luck System's architecture. The deployment network's seventeen nodes, all running parallel systems, all within the same overarching design.
"If the network is a unified system," he said, "and individual node activity affects the aggregate output—"
"Your field would register the system-level changes," she said. "Yes. The edges of your field expanding with increased network activity would mean you're not registering your own ability's output in isolation — you're registering the network's output."
He sat with this.
Level 4 was near-deterministic outcomes in his favor. He'd reached that threshold personally — his own total LP earned, his own cultivation.
But if the network's aggregate was also influencing his field output—
The Level 5 threshold was 1 million LP total earned. He had approximately 400,000 total earned. The jump to Level 5 was significant.
Unless the network's aggregate activity contributed to the threshold in some way he hadn't understood.
He opened the system.
```
[CURRENT LP: 421,300]
[LUCK AURA: LEVEL 4 — FIELD TEXTURE: ELEVATED VARIANCE AT EDGES. SOURCE: NETWORK ACTIVITY AGGREGATE. THIS IS NEW DATA.]
[NOTE: THE LEVEL 4 THRESHOLD WAS INDIVIDUAL — ACCUMULATED LP EARNED. THE LEVEL 5 THRESHOLD IS DIFFERENT. IT IS NETWORK-LEVEL. THE ARCHITECT DESIGNED THE INDIVIDUAL PROGRESSION AS PHASE 1. PHASE 2 BEGINS WHEN THE NETWORK IS ACTIVE.]
[NOTE: SIXTEEN NODES. ONE OBSERVER. THE AGGREGATE APPROACHES THE PHASE 2 THRESHOLD AT THE NETWORK'S COMBINED RATE. INDIVIDUAL LP STILL REQUIRED. BUT THE NETWORK MULTIPLIES THE RATE.]
```
He read this three times.
He'd been calculating the Level 5 threshold as a personal milestone. 1 million LP total earned, his own accumulation.
The system was telling him the Level 5 threshold was a network condition. Individual LP still mattered. But the network's aggregate activity was compressing the timeline.
He showed Han Weiwei the note.
She read it. Her expression didn't change immediately. Then: "The architect built Phase 1 as individual development and Phase 2 as network activation."
"Yes," he said.
"Phase 2 has started," she said. "Not formally — the nodes are still in individual development. But the aggregate is crossing a threshold."
"The edges of my field," he said.
She looked at the measurement graph. "The field expansion registered beginning eight days ago," she said. "Eight days ago is when Song Meiqi made contact with the network."
The observer joining the network was the trigger. Not a node contacting another node — the observer leaving her external position and entering the network.
The architect had built the Phase 2 trigger into the observer's transition.
"He was patient," he said. "And precise."
"Yes," she said.
She put the measurement data aside and looked at him directly.
"The succession position," she said. "Six days."
"Six days," he said.
"After which," she said, "you're inside the Vanguard's full operational structure, not the transitional layer."
"Yes," he said.
"The network is accelerating," she said. "The succession is the last structural piece of your city-level position. After it formalizes—"
"After it formalizes," he said, "the Fengliu contact, the Wei Ruoxi meeting, the Ren Jiuyuan question."
She looked at him. "And the main quest."
He looked at her.
"MQ4," she said. "You're not going to tell me the indicator."
"Seventy-six percent," he said.
She held his gaze. "The remaining distance."
"Is personal," he said.
She nodded, once. The acknowledgment of someone who had said all the relevant things already and didn't need to say them again.
The session continued until 5 PM. The field characterization data accumulated, patient and precise.
When he left, the city's evening light was at the long-angle phase that only appeared in late March — low and amber, making the buildings look different than they did any other time of year.
He drove home through it, watching the probability field's edge-variance run at its new, slightly elevated register.
The network, coming online.
Something was building. He could feel it in the field's texture the way you felt weather in the air before it arrived.
Six days.
