Tuesday ran clean.
Mao Yingjie made the social connection at ten AM — a twenty-minute conversation with the Tier-2 faction's logistics coordinator, routed through a professional contact she'd cultivated for eight months without knowing why until the network task gave her the answer. The coordinator had the faction's intelligence asset's operating log in a shared backup server. Mao Yingjie's contact had casual administrative access to that server for billing reconciliation purposes.
The access existed. She used it.
She sent him a message at ten forty: *Done. The log is in an encrypted package at the handoff node you specified. I've never seen a task close that fast.*
He had specified the handoff node on Monday night — a routing architecture through three dead-drop servers that would arrive in Han Weiwei's research file by Wednesday morning with no traceable origin. The technical construction took about ninety minutes total.
```
[NETWORK TASK — COMPLETE]
[LP DISTRIBUTED: 6,133 PER NODE]
[YOUR TOTAL LP: 183,433]
[REMAINING TO LEVEL 4: 16,567]
[HAN WEIWEI RESEARCH TIMELINE: ADVANCED 6 WEEKS]
[NOTE: MAO YINGJIE'S TASK COMPLETION VELOCITY HAS INCREASED BY 340% SINCE NETWORK INITIALIZATION. THE ISOLATION HABIT BREAKS QUICKLY ONCE THE ARCHITECTURE MAKES COORDINATION POSSIBLE.]
```
340 percent. That was what four years of operating alone had cost her — not the absence of mechanism, but the absence of the right conditions to use it. She had the tools. She'd been waiting for something to make the tools make sense.
He filed this and went back to the morning product.
At eleven thirty, he got a message from Lin Zhengyue. Not a meeting request — just a message, three words: *We need to talk.*
He called immediately.
"Fang Junhao," she said, when she picked up.
He waited.
"He called this morning. Requested an urgent meeting." A pause. "He came in person at ten o'clock, which means he made the request at nine and was already at the door by the time I confirmed. He had prepared something."
"What did he bring?" Chen said.
"A concern." The word had a particular dry quality in Lin Zhengyue's voice — not mockery, just the precise naming of what it was. "He framed it as a professional concern about irregular conduct by a Vanguard senior operative. He brought a summary of the phone call between you and Meiyao. A partial summary." She paused. "He had the section of the call where you told her that what happened with me was between you and me."
"He's been running surveillance on her communications," Chen said.
"Yes. Through an assistant in her immediate environment, from what the framing suggested. He didn't disclose the source." She paused. "He presented the partial call summary as evidence of inappropriate conduct — a senior operative using a family relationship to circumvent professional disclosure requirements. His recommendation was that I request a formal review of your administrative access to the Lin Family Faction's integration project."
Chen looked at the morning product queue. Then he looked at the city through his office window.
"What did you say?" he said.
"I listened to him for six minutes," Lin Zhengyue said. "Then I told him that the professional relationship he was describing was fully documented in the Lin Family Faction's formal engagement records and that I had reviewed and approved every element of it. I told him the call summary he had presented was incomplete in a way that misrepresented the call's substance. I told him that bringing incomplete information to a faction head as a basis for a formal concern was a choice that I would remember." A pause. "Then I asked him to leave."
"He left," Chen said.
"He left," she confirmed. "He looked like a person who had made a calculation that had not produced the outcome the calculation predicted."
Chen set his phone down for a moment — not to put it down, just the fraction of a second's pause. He picked it up again.
"He's going to process this debrief," he said. "He'll land on: I brought incomplete information. He'll go back to the source and try to get the full call before attempting anything further."
"Can he get the full call?"
"The assistant who was running the surveillance caught the call on a partial frame," he said. "The first four minutes and the final exchange weren't captured. If Fang pushes for more thorough surveillance, he'll get fragments — but the full call isn't accessible from the surveillance architecture he was running." He paused. "What he'll be left with is the accurate debrief, which is: I tried to use Lin Zhengyue to constrain Chen, and Lin Zhengyue already knew the situation better than I did."
A pause.
"He's going to be angry," Lin Zhengyue said.
"Yes."
"And then?"
"And then he'll make a second poor decision," Chen said. "Or he'll go quiet for a while and try to build a stronger approach. His personality type — the specific kind of exceptional that has never had to develop patience — tends toward the former."
"You predicted this," she said.
"The system did," he said. "I read what it predicted."
She was quiet for a moment. "He cares about Meiyao," she said. Not defensively. Accurately. "That's genuine. What he's doing is misguided and handled badly but the underlying motive isn't cynical."
"I know," he said. "He's not the problem. He's a consequence of incomplete information combining with a specific kind of pride. The combination produces poor decisions. That's the problem."
"And the solution?"
"Wait," he said. "The situation will resolve itself. The only intervention that would accelerate it is direct, and direct creates debris."
She was quiet for a beat longer.
"Thursday," she said. "The section six draft needs your notes on the final boundary condition before I write it."
"I'll send them tomorrow," he said. "First draft."
"All right." A pause. "Haoran."
"Yes."
"The surveillance on Meiyao," she said. "She doesn't know."
"No."
"Should she?"
He thought about this carefully. Whether knowing that her current partner had been surveilling her communications would change something for Lin Meiyao — the calculation she was already running, the seam that had appeared in the correctness of her decision sixteen months ago. Whether telling her was useful, or whether it was the kind of information that looked useful and actually served a different purpose.
"It's not mine to tell her," he said. "If she finds out on her own, that's what the situation produces. If I tell her, I'm making myself the cause of the outcome rather than a witness to it."
"You're already part of the cause," Lin Zhengyue said.
"Yes," he said. "But there's a difference between being part of the cause and actively constructing it. I don't construct outcomes for people who aren't in my task structure."
A long pause.
"Sometimes I forget how precise you are," she said.
"The precision is what got me here," he said.
She was quiet for another moment, and then she ended the call.
---
He pulled up the system notification that had appeared while they were talking.
```
[NOTE: FANG JUNHAO'S APPROACH TO LIN ZHENGYUE PROCEEDED AS PROJECTED.]
[NOTE: LIN ZHENGYUE HANDLED THE INTERACTION WITHOUT ADDITIONAL INPUT REQUIRED FROM YOU. THIS IS THE EXPECTED OUTCOME.]
[NOTE: FANG'S DEBRIEF WILL PRODUCE: INCOMPLETE INFORMATION + UNSUCCESSFUL APPROACH. HIS OPTIONS ARE NOW: ACQUIRE BETTER INFORMATION, TRY A DIFFERENT TARGET, OR ESCALATE DIRECTLY. HIS PERSONALITY TYPE MAKES ESCALATION THE MOST LIKELY NEXT STEP.]
[NOTE: THE ESCALATION TIMELINE IS APPROXIMATELY 4–8 WEEKS. HE NEEDS SUFFICIENT EMOTIONAL BUILD AND A SPECIFIC TRIGGER. THE TRIGGER WILL LIKELY BE A PUBLIC SETTING WHERE THE PERCEIVED SLIGHT CAN BE ADDRESSED IN A PUBLIC FRAME.]
[NOTE: THIS IS A FUTURE PROBLEM. CURRENT LP PRIORITY IS CORRECT.]
```
He read it, filed it, closed it.
Current LP priority was correct. 183,433. 16,567 remaining to Level 4.
The estimate was seven to ten days, now likely closer to five given the network task pace.
He returned to the morning product.
---
Wednesday morning, Han Weiwei's message arrived at seven forty-three.
*There's a file in my research archive that wasn't there yesterday. It's exactly what my current research needed and I have no idea where it came from. I'm not asking. I'm thanking.*
He sent back: *Thursday at seven. I want to see what you do with it.*
She sent: *Bring coffee. I'm going to need it.*
He looked at that for a moment.
He sent back: *What kind?*
A pause. Then: *Flat white. One sugar. Don't be late.*
He put his phone down. The morning product queue had four items. He worked through them in order, taking notes, flagging two for follow-up with the intelligence annex team.
At nine thirty, the system generated a standard side task. B-rank level — moderate complexity, primarily analytical work involving a Central District cultivation supply chain irregularity that had been running for two months and would take about two hours to resolve cleanly.
He ran it before lunch.
```
[SIDE TASK COMPLETE: +4,800 LP]
[TOTAL LP: 188,233]
[REMAINING TO LEVEL 4: 11,767]
```
11,767.
At the current rate — with two more individual side tasks already queued and the network generating its own stream — he was looking at four days. Maybe three.
He sent Mao Yingjie a message: *Two more individual tasks this week. The network generated one more for Thursday — check your mechanism.*
Her response: *Already on it. The pattern layer flagged it an hour ago. This is different.*
*Yes*, he sent. *That's what it's supposed to feel like.*
---
The Thursday morning session with Han Weiwei ran two hours and forty minutes.
She had spent two days with the operating log data. Not sleeping, or not sleeping much — the session notes she'd prepared were too detailed for someone who had gone home at a normal hour. Twenty-two pages of annotated cross-references, the log data mapped against her existing distribution research at seven different analytical levels.
She had built something substantial in forty-eight hours.
He brought the flat white with one sugar. She took it without looking up from the table.
"Sit," she said. "I need to walk you through the third section before I can explain what it means."
He sat.
The third section was where the operating log data intersected with her distribution pattern research — the surveillance records of independent practitioners in three districts, running over fourteen months, generating a secondary dataset of unauthorized ability monitoring that had, inadvertently, produced more accurate ability-type tracking than the Bureau's official registration records. The faction's intelligence asset had been thorough.
"The sampling is biased," she said. "They were tracking practitioners they considered security concerns, which skews toward higher-tier individuals and non-standard ability types." She pulled the relevant page forward. "But the non-standard ability type data is exactly what I needed. Look at the distribution here."
He looked.
The non-standard types. The cases that didn't fit the primary distribution model — the ones the standard awakening mechanism couldn't interface with correctly. In the surveillance data, they were flagged as *unclassified* with a secondary notation in some cases: *possible anomalous development pathway.*
"The faction's intelligence asset noticed them," he said.
"Without understanding what they were," she said. "They flagged them as security concerns because unclassified ability types generate a threat assessment by default — you don't know what they can do. But the data they generated gives me—" She paused. "It gives me the most complete city-level picture of non-standard development cases I've ever had."
She looked up at him.
"Twenty-two confirmed," she said. "In this city alone. Not fourteen. Twenty-two."
He held her gaze.
"The surveillance dataset found eight cases the Bureau's standard follow-up records didn't have," she said. "Eight people operating under mechanisms your system apparently didn't generate the data for — or the data wasn't flowing to you."
"The data exists on the mechanism network," he said. "We didn't have the city-level confirmation."
"Twenty-two," she said again. "That's more than double the original fourteen. The compensation mechanism was deployed more broadly than I thought." She paused. "How many globally?"
"The current working figure is seventeen," he said.
She looked at him.
"Seventeen globally," she said. "Twenty-two in this city alone."
He hadn't said globally. He had said seventeen, and she had supplied globally from context.
"You've been building a global model from the start," he said.
"The distribution research covers eight cities across three provinces," she said. "Scale was always implicit." She set the page down. "Seventeen globally is inconsistent with twenty-two city-local."
"Unless the global figure is out of date," he said. "Or refers to a different category of deployment."
She was quiet for a moment. The spatial field ran at its cognitive-activation register — that higher compression he'd learned to read over the past weeks.
"Different category," she said.
"Different category," he agreed.
She looked at the research spread across her table. The twenty-two cases. The eight cities' distribution maps. The operating log data that had just expanded her picture by fifty-seven percent.
"Thursday two weeks from now," she said. "I need time to integrate this. I'll have something more definitive."
"Two weeks," he said.
He finished the coffee. She was already making notes, the pen moving quickly across the annotation page with the specific energy of someone who had just found what they'd been working toward for two years.
He walked out through the administrative area and pressed the elevator button.
The city ran its Thursday morning register fourteen floors below.
```
[CURRENT LP: 188,233]
[REMAINING TO LEVEL 4: 11,767]
[NOTE: THE TWENTY-TWO CITY-LOCAL CASES ARE NOT IN YOUR CURRENT DATA. THE OPERATING LOG HAS GENERATED NEW INFORMATION.]
[NOTE: HAN WEIWEI'S RESEARCH IS NOW 8 WEEKS AHEAD OF THE PRIOR PROJECTION.]
[NOTE: THE NETWORK ARCHITECTURE IS FUNCTIONING CORRECTLY. THREE NODES, THREE ROLES, ONE DIRECTION.]
```
He read it in the elevator.
The elevator opened at the ground floor. The building's lobby ran its morning traffic.
He had a side task queue and a network task and eleven thousand LP to cover.
Four days. Maybe three.
He went back to work.
