Chapter 19 · 2419 words · 11 min

19: The Office Test

The assignment came through Director Liang directly, which was the first indicator of its character — a direct assignment from the Director rather than a tasked item through the section's regular flow meant the item had a specific sensitivity that the regular flow wasn't designed to handle.

Director Liang called Lin to his office on a Tuesday morning, seven days after the planning committee session where the infrastructure review had been received well enough that one of the committee members — the agriculture deputy — had asked a follow-up question that had required Lin to provide a clarifying answer on the spot, which he had done. The Director had been present. The clarifying answer had been accurate.

In the office: "The Vice-Mayor's office has a press release to coordinate," Director Liang said. He said it the way he said things that were more complicated than they appeared at the surface level — not with the cautious framing of someone who was concerned about the complication, but with the specific economy of someone who was giving information rather than managing it. "Vice-Mayor Pang is announcing the county's winter infrastructure maintenance schedule. Public communication. The General Office coordinates the public communication process for all senior officials." He looked at Lin. "The coordination contact is Secretary Tang Wei, in Vice-Mayor Pang's administrative office."

"I'll contact Secretary Tang this morning," Lin said.

"Yes," the Director said. He looked at his desk. "The process is: Secretary Tang provides the content and factual basis, you format and coordinate the communication protocol, the final version goes through the General Office review before release." He paused. "The process is standard. Follow it." He met Lin's eye for a moment — the specific look, the one that gave information rather than instruction. "Follow it exactly."

Lin said: "Understood." He meant the second sentence.

---

Secretary Tang Wei was in the Vice-Mayor's administrative office on the second floor, north wing — a different building section than the General Office's third-floor south, which was a longer walk than the usual cross-section routes Lin had established. He arrived at the Vice-Mayor's office at ten forty-five, gave his name and purpose to the outer desk, and waited twelve minutes, which was longer than the standard waiting time for a scheduled inter-office coordination contact.

Tang Wei came to the outer desk rather than sending someone. He was forty-seven, with the specific type of administrator face that had organized itself around managing access rather than managing information — the person who controlled who got to speak to the senior official, who understood the official's preferences and moods, whose loyalty was personal rather than institutional. He assessed Lin with the assessment of a person who is deciding whether the person in front of them is a threat or an inconvenience.

He arrived at: inconvenience.

"The press release coordination," Tang said. "Sit."

Lin sat.

Tang provided the briefing in the manner of someone who has provided briefings to many coordinating officers and has calibrated the briefing to the minimum necessary information. The winter infrastructure maintenance announcement: eleven projects, three districts, timeline running December through February, public communication purpose was to set expectations about road closures and service interruptions. The factual basis was a document set from the Engineering Bureau's maintenance division. He would provide the document set.

Lin noted: *document set*, not *document.* A set implied multiple documents. Tang was offering to provide a set that he had already curated, which was different from providing the original documents. The distinction was the kind of distinction that was easy to miss in a routine briefing and easy to notice if you were paying the right kind of attention.

He was paying the right kind of attention.

"I'll need the source documents from the Engineering Bureau," Lin said. "The maintenance schedule and the project specifications."

Tang looked at him. The inconvenience assessment recalibrating slightly. "I'll provide the summary," he said. "The General Office coordination doesn't require the full source documents."

"For accurate public communication, I prefer to verify against the source," Lin said. "Standard process."

"The summary is accurate." Tang's tone: not hostile, but the tone of someone who does not expect to be challenged on the adequacy of what he provides. "The General Office process doesn't require the source documents."

Lin looked at him. He thought: the Director said *follow the process exactly.* He thought: Tang is telling me the process doesn't require source documents. These two things might not be in conflict. He thought: I'll take the summary now and request the source documents through the official channel if I need them.

"The summary, then," he said. "And I'll note that the source documents are available if the review process requires them."

Tang produced the summary. Lin took it, confirmed the coordination timeline, established the draft deadline, and returned to the third floor.

He read the summary at his desk.

---

The summary was a one-page document: eleven projects listed by name and location, timeline table, brief description of the service interruption for each project. Clean formatting, professionally produced.

Lin worked through the summary systematically, cross-referencing against the county's standard infrastructure terminology for public communication purposes, beginning the draft framework. At the fourth project — Huadong District underground water main replacement, planned January 5 through January 28, Lane Three through Lane Seven of the Huadong residential block — he paused.

Something was wrong.

He could not immediately locate the wrongness. The description was coherent, the timeline plausible, the project scope consistent with the scale of a water main replacement. He read it again. He looked at the adjacent projects in the table. He looked at the project number — 7 of 11.

The project number was sequential. But the geographic sequence in the table was not: projects 1-6 ran north to south through the county, as the standard Engineering Bureau organization did; project 7 jumped from the south district back to the central district. Which was not necessarily wrong — infrastructure didn't follow geographic sequence. But it was unusual enough to pause on.

He thought: Tang said the summary is accurate. He thought: the summary came from Tang, not from the Engineering Bureau directly. He thought: the Director said *follow the process exactly.*

The world rolled.

The splice: clean, the frame replaying, the corridor-entry quality. He was at his desk. The summary was in front of him. He had not yet drafted anything — he had been reading.

Lin set the summary face-down.

He sat still and breathed and thought.

---

He had sixty seconds.

The trigger had come mid-read, which meant his processing had caught something in the document before his analytical attention arrived. The something was not the geographic sequence discontinuity — that was the thing that had made him pause, but the pause had preceded the cheat. The cheat had triggered before the conscious analysis was complete. His subconscious had run the full pattern and arrived at *wrong* before he had.

He thought: what in project 7 is wrong?

He started from the beginning of the project description and tested each element against what he knew. Not against what the summary said — against what he actually knew from independent sources. The infrastructure review's seven-township data had given him a detailed picture of the county's physical infrastructure. The planning committee session had added the committee's strategic priorities. His two months of administrative correspondence had added the specific texture of how each bureau communicated about infrastructure projects.

He went through the project 7 description: Huadong District, underground water main, Lane Three through Lane Seven, January 5 through January 28. He tested each component. Huadong District: one of the three districts in the county, central position, primarily residential. Underground water main: standard maintenance category. Lane Three through Lane Seven: the Huadong residential block's internal lanes. January timeline: standard for winter infrastructure work.

The service interruption description: *Water supply interruption during construction, January 5-28, affecting 2,300 residential units. Residents advised to store water January 4.*

He paused on 2,300.

He thought: Huadong District's Lane Three through Lane Seven. He had been through Huadong District twice, once for a cross-bureau errand and once when he'd taken a wrong turn on the way back from the PSB. Lane Three through Lane Seven was not a large section of the district. The residential units in that section were the older courtyard-house type, dense but not high-rise. 2,300 units across five lanes of old town courtyard houses.

He had memorized the infrastructure review's county-wide data. He tested the number against what he remembered: Huadong District's total registered residential units were approximately 8,600, across twelve internal lanes, plus the high-rise residential block at the district's north edge. Lane Three through Lane Seven: approximately five-twelfths of the district's lanes, excluding the high-rise. At roughly 700 units per lane in the courtyard section — which was the density range from the district data — five lanes would produce around 3,500 units, not 2,300.

The number was wrong. The announced service interruption was undercounting the affected residents by approximately 35%.

This was not a rounding error. This was not a formatting error. A public communication that announced a 23-day water interruption affecting 2,300 residents when the actual number was closer to 3,500 would produce: inadequate preparation by residents who were not notified, complaints attributable to the General Office for insufficient public communication, and a discrepancy between the announced and actual impact that would be visible in retrospect.

The trap was the number.

Tang Wei had provided a summary with a wrong number. When the press release went out with the wrong number, the General Office — and Lin specifically, as coordinating officer — would have produced a public communication that misinformed residents. The complaint would not fall on the Vice-Mayor's office, which had provided the briefing internally. It would fall on the General Office's communication process. It would fall on the junior coordinating officer.

He had sixty seconds. He had identified the trap.

The counter: verify against the source documents before publishing.

---

He lifted the summary and turned it face-up and wrote, at the top in red pen: *PROJECT 7: VERIFY UNIT COUNT AGAINST ENGINEERING BUREAU SOURCE.* He dialed the Engineering Bureau's infrastructure division directly — the contact was in the General Office's standard reference list, not through Tang's office.

The Engineering Bureau maintenance coordinator, Officer Zhao, answered on the third ring. Lin identified himself, gave the project reference number, asked for the residential unit count for the Huadong District Lane Three through Lane Seven water main project.

Officer Zhao checked. He came back with: 3,480 residential units. Not 2,300.

"The briefing document I received from the Vice-Mayor's administrative office has 2,300," Lin said.

A pause from Officer Zhao. "The correct figure is 3,480. That's from the project specification filed with the Bureau."

Lin thanked him, ended the call, made the correction in the draft, and submitted the verification request through the official channel — a formal note to Director Liang's office noting the discrepancy between the Vice-Mayor's briefing summary and the Engineering Bureau's source document, with both figures cited, and requesting Director Liang's guidance before the draft was finalized.

The Director's response came within the hour: "Use the Engineering Bureau figure. Source document controls."

The press release went out the following morning with 3,480 units.

---

The Vice-Mayor's office acknowledged receipt. Pang's public acknowledgment of the communication was the standard favorable response — the press release was distributed through the county's media channels without incident, the resident notification period was sufficient, no complaints reached the General Office about inadequate preparation.

Secretary Tang Wei called Lin once, on the afternoon the correction was submitted. He said: "The summary figure was adequate."

"The Engineering Bureau figure is the source," Lin said. "Source document controls the public communication."

A pause. "Yes," Tang said. The pause had the quality of a recalibration. "The process is correct." He ended the call.

Lin put the phone down and looked at the section floor. Across the section, Sun Tao was at his desk with a document in front of him, not reading it. His face was oriented toward the document. His attention was not on the document.

Their eyes did not meet. Lin did not try to make them meet. Sun's expression was unreadable in the deliberate sense — not the naturalism of a person thinking about something else, but the carefully controlled non-display of someone who had decided not to show what he was observing. Whatever assessment Sun was making of the press release situation, the display of that assessment was being managed. Which was itself information: Sun was not reacting openly. He was watching and filing. The crude error trap had been followed by the sophisticated forgery, and now by whatever came after sophisticated forgery.

Lin returned to the afternoon's correspondence.

In the evening: private notebook entry. *Day 84. Third cheat use. Trigger: mid-read, project 7, unit count discrepancy. Trigger came before conscious analysis complete — subconscious pattern recognition again, same as Day 72. Cost: mild headache, 10 minutes. Lowest cost yet. Mechanism is calibrating.* He paused, then added: *The counter required: a phone call and a formal verification note. Two minutes of work. The cheat gave me sixty seconds to identify that the two minutes were necessary. The exchange remains favorable.*

He sat with the notebook open for a moment before closing it. Three uses. Day 4, Day 72, Day 84. The gaps between uses were decreasing — sixteen days between the second and third — which did not necessarily indicate that the situations requiring use were increasing in frequency. The situations were what they were. The mechanism was simply becoming more sensitive to them: the threshold for trigger was calibrating along with the cost, responding faster to patterns that earlier versions of the mechanism might have missed until the situation was further along.

He noted this and closed the notebook. He thought about the Director's instruction: *follow the process exactly.* The process required source documents. Tang had tried to shortcut the process. The process had been the protection.

He thought about Lao Wei's thirty-one years of understanding which processes existed for which reasons.

---

Previous19 / 110Next

Comments (0)