Wei Ruoxi arrived at the Bureau at ten AM precisely.
She had the quality of someone who was almost never late and almost never early — a person for whom timing was a professional variable rather than an accident. He was at the reception area when she came through the main entrance.
"Fourteenth floor," he said.
She fell into step alongside him. The field harmonic between them ran at low register — aware of itself, not distracting. He'd felt the same field proximity in the elevator, but here it was easier to assess. Her system generated a different frequency from his — where his field pushed probability toward favorable variance, hers created a frictionless surface between people. The specific feeling of being around her was that the space between people felt slightly smaller than usual. Not intrusive — like a room with good acoustics.
"Song Meiqi sent me the network architecture summary last night," she said. "The seventeen nodes and their functions."
"What's your reaction?" he said.
"That the architect built more carefully than I'd thought," she said. "My system assigns tasks that look local — connection A to connection B, in this city, with these people. The summary shows me how those connections mapped to a larger design that I couldn't see from my position." She paused. "I've been building a structure without knowing what I was building."
"The design is patient," he said. "Individual perspective doesn't let you see it. You need the observer's view."
"Or two years of hindsight," she said.
The elevator. The fourteenth floor.
Han Weiwei was at her desk, two monitors running. She looked up when they walked in. Her assessment of Wei Ruoxi was immediate — the spatial field registering a new person's coordinates, the professional assessment running in parallel.
"Wei Ruoxi," Han Weiwei said. Not a question. She had the name already.
"Director Han," Wei Ruoxi said.
He watched the two of them look at each other. Wei Ruoxi's social facilitation field — the ambient hum that made distance feel smaller — running up against Han Weiwei's spatial awareness, which knew exactly how far away everyone was at all times. The result was something he hadn't predicted.
Neither of them seemed uncomfortable. That was interesting.
"Sit down," Han Weiwei said. "I've read Song Meiqi's observer feed summary. I want to understand your task architecture directly."
Wei Ruoxi sat. She described it in the same clean language she'd used with him — the connection tasks, the facilitation function, the six months of introductions. Han Weiwei listened without interrupting. When Wei Ruoxi finished, Han Weiwei pulled up her network graph.
"The seven introductions," she said. "I have five of them in the model. I was missing the Bureau connection from yesterday and one in the Consortium context from three months ago."
"The Consortium connection was Bai Qingmei," Wei Ruoxi said. "I facilitated an introduction between her and a compliance research specialist."
He looked at this. Bai Qingmei's ability to build a compelling compliance refusal had been helped, three months ago, by an introduction she likely didn't know was facilitated. The research specialist had probably seemed like a chance encounter.
"The connection tasks," Han Weiwei said. "Your system assigns them — you don't choose them."
"No," Wei Ruoxi said. "The system assigns. I complete. I understand the connection's purpose only in retrospect, if at all."
"The architect designed your function to build Chen Haoran's operational environment before he was powerful enough to build it himself," Han Weiwei said. Not a question — she was narrating her analysis.
"That's my best interpretation," Wei Ruoxi said.
"The seven introductions in the Vanguard's extended network," Han Weiwei said. "Three touched Chen Haoran's succession path directly. Two touched his Bureau research collaboration. Two I can't yet map to a specific outcome." She looked at Wei Ruoxi. "The two I can't map yet — what do you know about them?"
"One was six months ago," Wei Ruoxi said. "I connected a junior researcher in the national awakened data registry to a practitioner who works on probability field taxonomy." She paused. "The other was last week. I connected a senior Vanguard operative — external relations committee — to a Bureau researcher who specializes in ability classification history."
The ability classification researcher. Last week, in the week that Zhao Dequan had been considering his inquiry.
"The classification researcher," he said. "Was this person in contact with the security committee process?"
Wei Ruoxi looked at him. "I don't know. I made the introduction. I don't monitor what happens after."
He thought about it. An ability classification historian, newly connected to a senior Vanguard external relations operative, in the week that the security committee was processing the consultation about his ability type.
The security committee's finding had been unusually complete — a full reclassification rather than just addressing the consultation request. The committee had used specific historical language about the probability field ability type that was not in the standard classification documents.
*Where did Director Hao's committee get the historical classification context?* he had wondered at the time, and filed it.
He looked at Wei Ruoxi. "The classification researcher — the one you connected to the Vanguard external relations operative. Did you connect them to anyone else?"
"A third party," she said. "A research administrator at the National Bureau's classification database."
Three people. The classification researcher, the Vanguard external relations operative, and a National Bureau database administrator.
The committee's finding had cited classification precedents that were buried in the National Bureau's historical archive. The kind of precedents you only found if someone with database access knew to look.
The architect had planted the seed for the security committee's complete finding six months before the security committee existed as a relevant factor.
He sat with this.
Han Weiwei was already at her monitor, pulling up the field characterization data. She had registered the pattern at the same moment he had.
"The two unmapped introductions both produce downstream effects that benefited the succession or the Bureau research," she said. "The pattern is complete." She turned to Wei Ruoxi. "Your system isn't just building connections. It's building specific connections that serve specific outcomes the architect predicted months in advance."
"Yes," Wei Ruoxi said. "I've been a very specific kind of gardener."
The word was right. Not the framing of someone resentful about it — the framing of someone who had just understood the nature of their work clearly.
"The succession position in three days," Wei Ruoxi said. "Is there something the system is building toward through me that I haven't seen yet?"
He and Han Weiwei looked at each other.
"Probably," he said.
"Yes," Han Weiwei said.
"That's comfortable," Wei Ruoxi said. She said it without irony. "I'd rather know the architect planned ahead than not."
They worked for another hour on the network topology model — the seventeenth node observer position, Wei Ruoxi's connection function integrated into the architecture, the northeast node's resumed activity, the second party that the northeast node had reported.
"The second party," Han Weiwei said. "System-level access that doesn't match the architect's design."
"Not in the documentation," he said.
"The network architecture runs on the architect's deployment mechanism," she said. "If someone found a way to access the deployment mechanism's monitoring functions without the architect's knowledge—" She paused. "They'd need to understand the mechanism's design at a structural level. Not operational level. Structural."
"Which requires access to the design documentation," he said.
"Or the ability to reverse-engineer it from observing the nodes," she said.
He thought about who had been observing nodes long enough to reverse-engineer the system's architecture.
"Someone who's been watching the field signatures for longer than the nodes have been active," he said. "Which means they predated the nodes. They were watching before."
"Before the Awakening Event," Han Weiwei said.
He looked at her.
"The Awakening Event was designed," she said. "The architect designed it. If someone else was watching the pre-Awakening probability fields — looking for what the architect was building — they would have had time to develop access to the mechanism as it was deployed."
"A third party who knew the architect was building something," he said. "Watched him build it. Developed their own access to the network as the deployment happened."
"Parasitic access," she said. "Not the architect's design. A secondary monitoring architecture built on top of the first."
The three of them sat with this.
"The northeast node," he said finally. "They said the party following them was using system-level monitoring. Not field monitoring. That's consistent with parasitic access."
"Yes," Han Weiwei said.
"The party has been following nodes individually," Wei Ruoxi said. "Song Meiqi was followed. The northeast node was followed. If they have access to the full observer feed—"
"They don't," he said. "Song Meiqi's feed design routes through a specific channel to the architect. A parasitic tap would show variance in the feed — Song Meiqi would have noticed the data being duplicated."
"Unless the parasitic access is below the level of the observer feed," Han Weiwei said. "Not tapping the feed — tapping the raw deployment mechanism's activity logs."
Lower level. The activity logs would show which nodes were active, when they completed tasks, their general location data.
Less granular than Song Meiqi's full observer feed. But enough to track individual nodes.
"They know which nodes are active," he said. "They know general locations when nodes complete tasks. They've been using that to follow individual nodes." He thought about this. "Song Meiqi's running — they tracked her through task completion signatures, not the field monitoring. That's why she could suppress her field and still get found. She kept completing tasks."
Wei Ruoxi looked at him. "My tasks are local and small," she said. "If they're monitoring task completions—"
"They know you're active," he said. "In this city."
She took this in. "Have they approached?"
"Not yet," he said.
"Not yet," she echoed.
He opened his system.
```
[NOTE: THE SECOND PARTY. PARASITIC SYSTEM-LEVEL ACCESS. TRACKING NODES BY TASK COMPLETION SIGNATURES. THIS IS NOT THE ARCHITECT'S DESIGN — IT IS AN EXPLOITATION OF THE DESIGN.]
[NOTE: THE ARCHITECT HAS BEEN WATCHING THIS. THE OBSERVER FEED WOULD SHOW THE NORTHEAST NODE'S REPORT. THE ARCHITECT KNOWS ABOUT THE SECOND PARTY.]
[NOTE: IF THE ARCHITECT KNOWS AND HAS NOT ACTED — HIS TIMELINE HAS ACCOUNTED FOR THE SECOND PARTY.]
[NOTE: OR HE IS WATCHING YOU TO SEE HOW YOU HANDLE IT.]
[NOTE: THREE DAYS TO SUCCESSION. ADDRESS THE SECOND PARTY AFTER. IN ORDER.]
```
He closed the system. Didn't show the note to the others.
"The succession position formalizes in three days," he said. "After that, I go to Fengliu. The northeast node has the most recent direct contact with whoever is following them. I need that intelligence in person."
Wei Ruoxi and Han Weiwei both looked at him.
"The second party is a problem for after the succession," he said. "Not before."
"Because?" Wei Ruoxi said.
"Because they've been operating for months without making direct contact," he said. "Whatever they're building toward, it's patient. Three more days won't change the timeline."
"That's an assumption," Han Weiwei said.
"Yes," he said. "If it's wrong, the field will tell me."
She held his gaze. The skepticism in her expression — the precise skepticism of someone who spent her days testing assumptions against data — was present but not dominant.
"The field has been correct so far," she said.
"So far," he said.
Wei Ruoxi stood. "I need to go. I have a connection task this afternoon." She looked at him. "Song Meiqi told me: when you trust the system, you run better. She said it was the hardest thing she learned."
"It is," he said.
She left.
Han Weiwei turned to her monitors and didn't speak for a minute.
Then she said: "The field characterization data from this morning is the clearest we've collected. The network aggregate effect is registering at eleven percent above individual baseline." She pulled up the graph. "The progression rate suggests Phase 2, as the system described it, has been running for nine days."
He looked at the graph. "Since Song Meiqi joined the network."
"Yes," she said. "The aggregate amplification started the moment the observer transitioned from external to internal."
He looked at the edge variance graph. "How long until the individual LP threshold intersects with the network aggregate at the Level 5 threshold?"
She ran a calculation. "Depends on the network's ongoing task completion rate and your individual rate." She looked at the numbers. "At current rates — six to eight months."
Six to eight months. Down from the projected three years at individual accumulation rate.
"The architect's Phase 2 timeline," he said.
"Compressed," she said. "By the outperformance you mentioned."
He sat with this.
Six to eight months to Level 5 — reality accommodating him. Not magic, not luck in the casual sense — probability, taken to its logical extreme.
"Six months after the succession," he said.
"Roughly," she said.
"The second party," he said. "If they're watching the network and they know Phase 2 has started—"
"They're going to accelerate," she said. "Yes."
He looked at her.
"Then we don't have three days," he said.
"No," she said. "You have three days for the succession. The second party isn't waiting for the succession to finish."
He thought about this.
"The succession still goes forward," he said. "It can't be deferred — the position opens in three days, formal. If I'm not in position when it opens, the political capital is lost."
"I know," she said.
"So both things happen simultaneously," he said. "I close the succession and I start the second party assessment."
She turned away from the monitor to face him directly.
"You need to tell Song Meiqi to be careful," she said. "Her observer position is the most visible data point the second party can access. If they're monitoring task completions, they know a node is in the Haixia port district. They can find her."
He sent Song Meiqi immediately: *The second party's access mechanism. Your task completions are visible to them. Stop running visible tasks until I contact you. Don't run the observer feed at elevated output. Stay quiet.*
Her response in two minutes: *Already stopped. I stopped task completions Tuesday when the northeast node told me about the monitoring. I've been running at minimum observer output for forty-eight hours.*
He looked at the message.
She had already moved without being told. Two days ago.
*You've been managing this since Tuesday,* he sent.
*The northeast node's message was specific,* she sent. *I assessed the threat and reduced my visible signature. I should have told you immediately.* A pause. *I'm still learning when to act and when to report.*
He thought about the right balance of autonomy versus coordination. The observer making independent security decisions was useful. The observer not reporting them was a communication gap he couldn't manage.
*Report first, act second, unless waiting to report creates immediate danger,* he sent. *This was the immediate danger exception. But tell me after.*
*Yes,* she sent. Then: *Wei Ruoxi is also quiet since Tuesday. She stopped running connection tasks.* A pause. *She knew before I told her. Her system flagged the monitoring risk directly.*
Both of them had moved independently before he'd known there was a threat.
The network developing its own situational awareness.
He looked at Han Weiwei.
"They're both quiet," he said. "Since Tuesday."
"Good," she said.
"The northeast node's intelligence," he said. "I need it before the succession, not after. Three days gives me time to read what they know and adjust the second party assessment before I'm formally in position."
She looked at him. "You're going to Fengliu."
"Tonight," he said. "Train. Back Tuesday."
She was quiet.
"The succession orientation is complete," he said. "The committee materials are ready. There's nothing I need to be present for Monday that requires my physical location in the city."
"The succession is Tuesday," she said.
"I'll be back Monday evening," he said. "The formal ceremony is Tuesday morning."
She calculated this. "Nine hours there, whatever time you need in Fengliu, nine hours back. You have forty-eight hours."
"Enough," he said.
She turned back to her monitors. The afternoon light at the window. The field characterization data scrolling.
"Come back," she said. Not a command — just the statement of a fact she was indicating.
"Yes," he said.
---
He was at the train station at seven PM.
Song Meiqi sent at seven-fifteen: *The northeast node's name is Zhou Shuyan. Twenty-six years old. She says: the party following her had access to her system's task list — not just the completion signals, but the content. She completed a task six weeks ago that involved acquiring a specific document. Two days later, someone came to her door asking about the document by name.* A long pause. *They have read access to the task content. Not just the activity signals.*
Read access to the task content.
That was deeper than activity log monitoring. The parasitic access wasn't at the level of "a task was completed in this region." It had content — what the task was, what it involved, what it required the node to do.
If someone could read task content, they could predict the node's movements before the task was completed.
He messaged Song Meiqi: *Have you shared this with Wei Ruoxi?*
*Yes,* she sent. *Wei Ruoxi has gone to a location she didn't tell me. She said she'd check in tomorrow.*
Smart. If they could read task content but not the observer feed's higher-level processing, Wei Ruoxi going dark without filing a location with the observer was safer than staying predictable.
He sat in the train as it left the city.
The probability field at Level 4, running its ambient warm assessment. Near-deterministic outcomes in his favor.
He noted the qualifier. *Near-deterministic.* Not guaranteed.
The second party had read access to the task content.
Three days to the succession.
He thought clearly for the entire nine-hour trip, working through the shape of the second party from what he knew, trying to build the picture from the edges inward.
The window showed the late-night landscape passing — dark fields, occasional lights, the probability field thinning as he left the city's concentrated awakened population behind.
Forty-eight hours.
He worked.
