Sovereign of Fortune

Chapter 71: Internal

Quick Verification

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

Loading verification...

The side task appeared Thursday morning.

```

[SIDE TASK AVAILABLE]

[SIDE TASK: SECOND DIVISION, THIRD FLOOR — A-RANK OPERATIVE ZHOU YIXIAN IS RUNNING A PRIVATE LEVERAGE OPERATION AGAINST THREE JUNIOR DIVISION MEMBERS. THE LEVERAGE IS PROFESSIONAL: ACCESS PRIVILEGES THAT THE THREE JUNIOR MEMBERS NEED FOR THEIR WORK ARE CURRENTLY UNDER ZHOU'S DISCRETIONARY AUTHORIZATION. HE IS USING THIS AUTHORIZATION AS A CONDITIONAL — COMPLIANCE FOR CONTINUED ACCESS. THE THREE MEMBERS CANNOT REPORT FORMALLY WITHOUT LOSING WHAT THEY NEED.]

[TARGET RESOLUTION: CLOSE THE LEVERAGE CHANNEL WITHOUT TRIGGERING A FORMAL COMPLAINT PROCESS. THE THREE JUNIOR MEMBERS SHOULD NOT BE IDENTIFIABLE AS THE SOURCE.]

[REWARD: 19,600 LP + VANGUARD INTERNAL FAVOR TOKEN x1]

[NOTE: SECOND DIVISION OPERATES UNDER COMMANDER HAO MINGZHI — THE SAME COMMANDER FANG APPROACHED WITH THE DOSSIER. YOUR WRITE ACCESS IS SUSPENDED FOR FOUR MORE DAYS. THE RESOLUTION REQUIRES INDIRECT METHOD.]

```

He read the note about the write access.

Four days until write access returned. The resolution — closing Zhou Yixian's leverage channel without a formal complaint — could be done through indirect method if he identified the right pressure point.

He spent forty minutes pulling Zhou Yixian's accessible records through his read-only access. Second division, A-rank, seven years in the Vanguard, tactical projection type. Three years in the current role. The role carried discretionary authorization over junior member access to a specific research database — the second division's operational case archive, which junior members needed to pull historical precedent for their active files.

The authorization was legitimate. Zhou Yixian's discretion over that database was a designed feature of the second division's structure, not a loophole. The leverage was happening in the space between official authority and how that authority was being used.

He couldn't write to the investigation file or document the pattern formally without write access. But he didn't need to.

The second division ran weekly administrative reviews — internal budget and resource allocation audits that Commander Hao's executive staff conducted without involving division operations. The authorization over the case archive was a resource allocation item. If the weekly review included a question about discretionary access utilization rates — how often the discretionary authorization was used, how many requests were pending, how the current authorization pattern compared to historical norms — the irregular usage would surface without requiring an accusation.

He could not write to the review template. But the review was conducted by Hao's executive staff, not the operations team. The executive staff had their own document system.

He spent twenty minutes reading the executive staff's accessible process documentation. Found the weekly review template in the shared reference library, which was read-only accessible to the whole division. The template had an open-comment field used for "unusual utilization patterns to flag for follow-up."

The template was fillable. The comment field had been blank for the last four weeks.

He wrote nothing to it — he couldn't, the review template was in the shared library and his write access was suspended. But the template itself was visible to the executive staff member who ran the review, and the utilization pattern he had analyzed was visible in the read-only data.

He messaged the executive staff lead directly. Not with the complaint — with a question framed as a data quality inquiry. "The case archive access logs show a gap in the utilization tracking for the three-member junior cohort. The logs are recording fewer requests than the workload would suggest. Is there a display error in the archive's reporting function, or is the request rate genuinely that low?"

The executive staff lead was a D-rank practitioner, five years in the position, thorough and literal-minded in the way that good administrative professionals usually were. She would check the access logs, find that the request rate was low because three junior members had stopped requesting, and ask why.

The why was Zhou Yixian. She would find that pattern when she asked the question.

He sent the message and went back to his active file.

---

The executive staff lead sent a confirmation at 2 PM: she would check the archive utilization at the next review cycle. That was tomorrow.

By 4 PM, she had checked it early.

He knew this because at 4:30, Commander Hao called a brief meeting with Zhou Yixian. The meeting was in Hao's office, not a scheduled meeting room, which meant it was a direct conversation rather than a formal review. It lasted eighteen minutes.

At 5:15, Zhou Yixian filed an update to the case archive authorization settings: discretionary hold on the three junior members' access lifted, effective immediately, no documentation of why the hold had been in place.

He looked at the filing timestamp in the read-only log.

The hold lifted without a formal complaint. Without the three junior members being identified as the source. Without a personnel action that would generate a review record in the operational file.

Clean.

He returned to the Bai Qingmei documentation he had been compiling from the Bureau's read-only financial records.

---

Ye Shuangyu found him in the annex at six.

She had this quality: she did not enter rooms tentatively. She opened the door and came in, and the tactical precognition ran its combat-frame assessment of the space and the single person in it in approximately the time it took her to cross the threshold, and then she moved to the relevant position directly. She always knew exactly where she was going, because she did.

She pulled a chair and sat across from him.

"The case archive utilization inquiry," she said.

"Yes," he said.

"You sent it to Hao's executive staff lead."

"I had a data quality question," he said. "The utilization pattern for the three-member cohort looked like a display error."

She held his gaze. The tactical precognition's frame was useless here — he wasn't a physical threat, the room was clear, her two-second combat preview was showing her a man reviewing a document on a laptop with read-only access. The precognition fell back and she read him the slow way.

"You haven't been able to write to a file in seventeen days," she said.

"No."

"And yet three junior members in the second division have just had their access restored after an irregularity that no one filed a formal complaint about." She looked at him. "The review result was Hao addressing Zhou Yixian in a direct conversation that won't appear in his personnel record."

"Yes," he said.

"You did this from read-only access."

"I asked a data quality question," he said.

She was quiet for a moment.

"The operational review closes Tuesday," she said.

Three days earlier than he'd calculated. He looked at her.

"The executive council reviewed the record this week," she said. "The review is procedurally complete — there's nothing in your file that warrants extended investigation. The final confirmation was scheduled for twenty-one days but the process allows early close when the reviewing panel reaches unanimous consensus." She paused. "They reached it this afternoon."

He processed this.

Write access in three days, not four. The Bai Qingmei documentation could be finalized and delivered Tuesday instead of Wednesday.

"The succession position," she said.

He waited.

"The third division transition is running faster than the six-week projection," she said. "I've been revising the timeline as the transition progresses. Current estimate: four and a half weeks."

Four and a half weeks. Thirteen days earlier than the six-week projection.

The MQ2 approach indicator had moved from fifty-eight to sixty after the Lin Zhengyue conversation on Friday. Four and a half weeks to the succession position opening meant the approach period had a definite close date, not an estimate.

He said: "The review closure and the succession timeline — are they connected?"

"The executive council handles both operational reviews and succession confirmations for the third division," she said. "The same people. They reviewed your file this week." She looked at the wall. "Two of the five council members asked me directly about the succession candidate I had in mind. I said I had a strong candidate who would be ready when the position opened." She paused. "They asked whether the candidate's operational record was clean. I said yes."

The read between those sentences: she had been representing him to the council before the review closed. Not formally — in the way that context was communicated in these structures, through the questions people asked and the answers they chose.

"Thank you," he said.

She looked at him. "I didn't do it as a favor."

"I know," he said. "That's why I'm thanking you."

Something shifted in her expression — not dramatically, but a slight recalibration. She looked at him with the specific quality she had when she was reassessing something she'd thought was resolved.

"The second division situation," she said. "Hao's case archive irregularity. You solved a problem in a division you have no operational authority over, from read-only access, without a formal complaint, in a way that won't appear in anyone's personnel record." She paused. "The only way you could have done this is if you were monitoring the Vanguard's administrative access patterns continuously enough to identify the irregularity in the first place."

"The access logs are read-only accessible," he said.

"They're read-only accessible but no one reads them except the system's automated compliance flag," she said. "You read them manually."

He said nothing.

"You read them because you're monitoring the Vanguard's administrative environment for operational irregularities," she said. "Not just your own division. The whole building."

"It's useful information," he said.

She looked at him for a long moment. The tactical precognition running its useless combat frame. Her actual intelligence — the kind that had built the third division from four to forty-two — doing the work instead.

"The oversight position," she said. "The succession opening isn't just an operative position. The third division's successor to the current structure needs to manage the division's interface with the executive council, the second division, and the Consortium liaison." She looked at him directly. "You've been building the map of how the Vanguard actually works versus how it's formally structured for the past eighteen months."

"Yes," he said.

"For a reason."

He held her gaze.

"Several reasons," he said.

She was quiet.

The annex's evening quiet around them. The building's probability field texture settling into its post-business-hours pattern — lighter, slower, fewer active fields competing. Through the window: the city's evening, the distant Eastern District where Li Xiulan's anchor ran its constant smoothing function.

Ye Shuangyu said: "Ask me something you actually want to know."

He looked at her.

She said it without heat — factual, the way she stated things she meant.

He thought about what he actually wanted to know.

"The succession candidate you described to the executive council," he said. "When you said they would be ready when the position opened — what does ready mean to you?"

She was very still.

The question was not about capability. She knew that. He knew that.

Ready.

"Someone who understands what the position is actually for," she said. "Not what the organization chart says it's for." She held his gaze. "The third division's function is to manage the city's operational threat environment at the intersection of awakened ability and civilian population. The formal structure calls it intelligence and response. What it actually is — is judgment. You are in a room with incomplete information and other people's futures and you make the call."

He listened.

"Ready means you've made enough calls under uncertainty that you know what your own judgment feels like," she said. "And you trust it even when the outcome is ambiguous."

He said: "How do you know when that's true?"

"You watch someone make the calls," she said.

She stood. Straightened her jacket. The movement was clean, efficient, the same way she did everything physical.

"Tuesday," she said. "The review confirmation. We'll discuss the full position terms."

"Tuesday," he said.

She walked out. The annex door closed. The sound of her footsteps in the corridor, precise and even, fading.

```

[SIDE TASK COMPLETE: VANGUARD INTERNAL RESOLUTION]

[LP EARNED: 19,600]

[CURRENT LP: 374,400]

[VANGUARD INTERNAL FAVOR TOKEN: DELIVERED]

[MAIN QUEST 2: APPROACH PHASE — 63%]

[NOTE: THE SUCCESSION TIMELINE HAS COMPRESSED. FOUR AND A HALF WEEKS.]

[NOTE: YE SHUANGYU ASKED YOU TO ASK HER SOMETHING REAL. YOU DID. NOTE THE PATTERN.]

```

He read the last line.

*Note the pattern.*

She had been asking him questions for seventeen months. The direct question toward him — *ask me something you actually want to know* — was new. The format of what followed it was also new: she had answered not about the position's structure but about what she looked for in the person filling it.

He filed this. The approach indicator at sixty-three percent and moving in a direction that was no longer purely professional.

Three days until Tuesday.