The first structural issue was in the training pipeline.
He had three days of access to the division's workflow data before he identified it. The third division processed new recruits through a six-week onboarding program, after which they were assigned to operational units. The issue was in the handoff: the onboarding program was standardized for general A-rank combat types, but the third division had increasingly specialized toward information and infiltration roles in the past eighteen months. The mismatch between the standardized training and the actual operational requirements meant that new recruits spent their first three months in the field learning the skills the onboarding program hadn't taught.
The result: a six-month effective onboarding period instead of six weeks, wasted field resources, and experienced operators spending more time as informal trainers than as operators.
He wrote it up in two pages. The inefficiency, the mechanism, three options for addressing it.
He delivered it to Commander Ye on Wednesday morning.
She read it in four minutes. She said, "I've seen this problem for fourteen months and couldn't find where it was in the architecture. You found it in three days."
"The data pattern makes it visible," he said. "When you're inside the system you adapt to the inefficiency. An external view sees it as a structural feature."
She made a note. "The second issue is harder," she said.
---
The second structural issue was in the intelligence-sharing protocol between the third division and the Vanguard's central command.
This one took him longer. The data pattern was subtler — not an obvious bottleneck but a gradual drift in reporting accuracy over the past six months. The division's intelligence products were being compressed during the upward reporting process, with nuance and uncertainty quantification being stripped out in favor of cleaner, more decisive summaries.
The problem: clean, decisive intelligence summaries were more useful to command but less accurate. Decisions being made at the command level based on the compressed summaries were operating on reduced information quality.
He identified this on day eight of his extended access.
He brought it to Ye with more care. "This one affects your relationship with senior command," he said. "The mechanism is in the reporting format requirement — command wants summary products, but the summary format is stripping information that the raw products contain. The division isn't the source of the problem, but the division is where the information is lost."
She looked at his analysis. "Recommending a format change to senior command's reporting requirements is a political statement," she said.
"Yes," he agreed. "The approach that avoids the political issue is a hybrid product: standard summary for command, supplementary detail annex that's available on request. Command gets what they asked for. The information is preserved for decisions that need it."
She looked at the hybrid format template he had included. "This is actually what we were doing two years ago," she said.
"I know. The shift to summary-only happened during a restructuring eighteen months ago. The logic at the time was efficiency. The secondary effect wasn't tracked."
She set the analysis down. She was quiet for a moment. "How do you know about the restructuring eighteen months ago?"
"Research," he said. "External news coverage, public filings, professional network context."
She looked at him steadily. "You've been studying this organization."
"Yes."
"How long?"
"Twelve months."
She absorbed this. He watched the recalibration — not surprise, but the specific acknowledgment of a detail that changed the scale of what she was assessing. He had been studying the Vanguard before he was in the Vanguard's environment. That meant the contractor application was not spontaneous. The succession documentation briefing was not spontaneous.
He was not hiding this. He had stated it plainly.
"You've been building toward being here," she said.
"Yes."
She held his gaze for three seconds. "Why this division?"
He considered what answer was available.
"You built the best operational unit in the Vanguard from nothing," he said. "You understand how to make something function. I'm interested in that." He paused. "And your division's work — intelligence and infiltration rather than direct combat — is the category of work I'm suited for."
"The third structural issue," he said.
She nodded and moved on.
---
The third issue was the personnel development record system.
He had been looking at it for three days and was still not sure whether it was a structural problem or an intentional design choice he didn't fully understand. He brought it to her with the uncertainty explicit.
The uncertainty was genuine. The system had three possible explanations: intentional organizational design, inherited legacy structure from a previous administration, or a gap that no one had noticed because everyone above B-rank had informally normalized around it. He had evidence for each. He had presented it honestly because presenting false certainty to Ye Shuangyu would be noticed, would be remembered, and would cost more than the brief discomfort of saying *I don't know which of these is true.*
This, he had come to understand, was one of the primary differences between working with her and working with most people in positions of authority. She did not punish appropriate uncertainty. She evaluated it accurately as information quality rather than as competence failure.
"The personnel development records stop updating after operators reach B-rank," he said. "Below B-rank, the system tracks cultivation advancement, skill acquisition, operational performance. At and above B-rank, the tracking becomes minimal — basic status, no advancement metrics."
She looked at his documentation. "That's how the Vanguard-wide system is built," she said. "At B-rank and above, the organization trusts operators to manage their own development."
"I understand the logic," he said. "The consequence is that the division doesn't have a clear picture of where its B-rank and above operators are in their development trajectories. You can't plan succession paths accurately without that picture. And you can't identify advancement bottlenecks that might be affecting the division's capability ceiling."
She was quiet.
"This is the third division's Duan Weiting problem in a different form," he said. "The succession issue with Weiting exists partly because you didn't have documentation of his limitations. If you had a development picture of your entire upper tier—"
"I would have seen it earlier," she said.
"Yes."
She leaned back in her chair. "Changing the development tracking system at B-rank requires Vanguard-wide authorization."
"The third division could implement a voluntary supplementary tracking system," he said. "Not mandatory, not replacing the standard system. A parallel track for operators who want to participate. Data goes to the division leadership only. Optional participation builds the picture over time."
She looked at him. "You're suggesting I build a development intelligence capability for my own division."
"I'm suggesting you know your operators," he said. "The voluntary nature makes it non-threatening. The data quality improves as participation increases."
She was quiet for a moment. Then: "I had a second-in-command who didn't have the capability he needed and I didn't know the extent of it for three years because I wasn't tracking it." She said this as a statement, not a complaint. "If I'd had the picture—"
"You would have acted sooner."
"Yes."
She picked up all three analyses and stacked them. "These are good," she said.
"Thank you."
She looked at him. The assessment quality of her gaze had changed over the course of the past two weeks — not softer, but more specific. She was looking at him as a known thing rather than an unknown one. The category she had placed him in had been updated.
"I want to extend the consulting arrangement," she said.
"All right."
"Through the end of the year. Monthly retainer, access adjusted upward." She paused. "You'd be doing the same kind of work — identifying structural problems, proposing solutions. No operational role."
"I understand."
"For now," she said. The two words landed precisely. *No operational role. For now.* She was leaving the door open and knew she was leaving it open.
He filed this.
They finalized the arrangement in twenty minutes. He signed an updated contract. She gave him a new access credential.
He shook her hand and left.
In the hallway outside her office, he paused for exactly two seconds. The extended contract meant Monday-through-Wednesday access, a new credential level, and a direct reporting relationship that bypassed the standard contractor intake process. He was now inside the third division's organizational structure in a way the contractor application had not been designed to produce.
The system's predicted timeline said four to six weeks to MQ2 completion.
He walked to the elevator.
---
In the elevator going down, floor seven, the system notification:
```
[MAIN QUEST 2 — PROGRESS: 2/4 INTERACTIONS COMPLETE]
[NOTE: SHE IS DECIDING WHAT TO DO WITH YOU. SHE HAS NOT FINISHED THINKING ABOUT THE LIN MEIYAO CONNECTION. SHE WILL ASK BEFORE THE END OF THIS ARC.]
[NEXT INTERACTION: SIDE TASK FORTHCOMING — OPERATIONAL CONTEXT. YOUR FIRST SITUATION THAT REQUIRES B-RANK CAPABILITY IN PRACTICE, NOT JUST DOCUMENTATION.]
[RECOMMENDED SHOP PURCHASES: COMBAT SKILL — BASIC APPLICATION: 2,000 LP. CONSIDER PURCHASING BEFORE NEXT INTERACTION.]
```
A situation that required B-rank capability in practice.
He got out at the ground floor and walked to the exit. The Celestial Vanguard's lobby moved around him — operators and staff and the particular organized motion of a faction in continuous operation.
A B-rank, unaffiliated, unclassified, moving through it without friction.
He bought the combat skill application package on the subway home.
The LP balance dropped to 17,800. He noted it without stress. The accumulation rate had been consistent — side tasks in the mid-tier awakened community generated between 800 and 2,500 LP each, and he had been running approximately one per week since the D-rank threshold. At that rate, he would have the B-rank high threshold within two months if the MQ2 side tasks continued at the current reward structure.
The package was not a combat training manual. It was something more like a translation layer — a comprehensive module on the principles of B-rank physical engagement, covering how to use his cultivation's enhanced response time, how to apply the sensory enhancement in active situations, how to read an opponent's qi output as a form of anticipation. Three days of dense absorption work.
He ran through the material carefully. He had no combat history. The physical training manual had given him fundamentals — how to move, how to fall, how to generate force from his frame correctly. The combat application module took those fundamentals and showed him how they worked in the context of the power levels he would now be operating near.
The most important section: B-rank versus A-rank differential. How it felt, what it meant, what options existed. An A-rank combat operator with a combat-type ability could handle him in direct confrontation without much effort. That was simply true. The module was explicit about it.
What it also showed him: direct confrontation was not the only option. A B-rank with sensory enhancement and a level 2 luck aura operated in an environment where information was continuously available. The A-rank's advantage was physical force and trained instincts. His advantage was knowing more about the situation than the A-rank expected.
He filed this. He would not fight above his weight class. He would not need to.
---
Day one hundred and ninety-three. The side task arrived.
```
[SIDE TASK: A FACTION DISPUTE IN THE SOUTHERN DISTRICT HAS ESCALATED BEYOND MEDIATION. THREE C-RANK OPERATORS FROM A MINOR FACTION HAVE TAKEN A MEDIATOR HOSTAGE — THE MEDIATOR IS CHEN MEILING, WHO YOU HELPED SEVEN MONTHS AGO. THE SITUATION HAS BEEN DEVELOPING FOR FOUR HOURS. LOCAL ENFORCEMENT IS PRESENT BUT CANNOT ACT WITHOUT A COMMANDER-RANK AUTHORIZATION DUE TO THE FACTIONS INVOLVED.]
[AVAILABLE TO YOU: YOUR B-RANK CULTIVATION, THE ENHANCED SENSORY ABILITY, THE COMBAT APPLICATION SKILL, AND YOUR LUCK AURA AT LEVEL 2.]
[NOT AVAILABLE TO YOU: ANY VANGUARD AUTHORITY OR OPERATIONAL BACKING.]
[REWARD: 3,500 LP + [NOTE: COMMANDER YE SHUANGYU WILL HEAR ABOUT THIS. WHAT SHE HEARS IS UP TO HOW YOU HANDLE IT.]]
```
He read this and immediately stopped walking.
Chen Meiling. The mediation officer he had helped in month three. The contact token he had been holding.
He was three subway stops from the southern district.
He kept moving.
