Chapter 31 · 2458 words · 11 min

31: Tier II

[TIER II ACHIEVED]

March.

The feasibility study was in its second week and the section floor had the particular quality of a week with something unresolved at its center. Not the open unresolved quality of a question without an answer — the tighter unresolved quality of a thing that had been put in motion and was developing without Lin's direct participation. The routing log photograph was in Lao Wei's hands. What Lao Wei would do with it and when was entirely Lao Wei's question. Lin had given him the complete picture and had given him it accurately and at the correct time. The decisions from that point were not Lin's.

He understood this intellectually. The understanding did not entirely remove the specific tension of knowing that a mechanism was in motion and not knowing when it would arrive at its critical point. He worked through the feasibility study's data collection — the Finance Bureau's projection methodology, the Engineering Bureau's infrastructure load tables — and noted, at the end of each working day, that he was holding something with more readiness than the work itself required.

---

The tense quality expressed itself through three specific moments during the week.

The first: Tuesday morning. Sun routed a sensitive inter-bureau coordination document through Lin for counter-signature — technically correct routing, Lin was the counter-signature officer for that document category. But the document's routing log had a notation that Lin recognized from his December review: it shared an administrative registration number with the category of documents Lao Wei had co-signed in November. The notation was not the same discrepancy; it was a different instance of the same category. Lin read the document, verified its content was accurate, and signed. He said nothing about the routing log notation because saying something would mean saying how he knew about the routing log notation, and that would mean revealing that he had spent a Friday evening in December with unauthorized access to the cross-bureau log.

He signed. He filed his copy. He moved to the next item.

The second: Thursday. Director Liang called a brief section standing meeting — five minutes, unexpected, about the feasibility study's interim progress. Lin gave the update: three of four bureaus' data collected, Finance Bureau data expected Friday, analytical framework drafted, on schedule for the March committee brief. Director Liang nodded and said: "Good. Your name will be on the summary as well as the analytical sections." He said this to Lin, in the section's presence, with the tone of someone establishing a fact rather than making an announcement.

Lin said: "Understood." He did not look at Sun. He was aware of Sun's position in the section during this exchange — the specific quality of a person whose surveillance of someone else has been confirmed as redundant by the Director's direct communication pattern. He noted: this is the thing Sun cannot do anything about, which means it is the thing Sun will eventually try to work around rather than directly oppose.

The third: Friday afternoon. Peng came to Lin's desk with a request for a cross-reference from the quarterly correspondence archive — a routine matter that did not require Peng to come to Lin's desk rather than the filing room. Peng stayed four minutes. He asked about the feasibility study in the casual way of a person making conversation; Lin answered in the brief professional way of a person who was working. After Peng left, Lin processed the encounter: a probe, sent by Sun, to assess whether Lin's demeanor had changed in any way that would indicate he had information he shouldn't have. Lin had given him nothing to work with. His demeanor had been professionally neutral throughout.

After the probe, Lin noticed what he had been doing for three days: holding the cheat ready.

---

Not deliberately — it had become a background presence, the way a person who has been in situations requiring quick response develops a peripheral awareness of the tools available. He had used the cheat three times in seven months. In each case he had not had time to think about it; the situation had reached the crystallization point and he had used it. Now, in the tense week, he was aware of it the way you were aware of a window when you were in a room that might need to be exited.

He had not used it. The week had not required it. But the awareness had been there: available, held ready, the specific quality of a prepared resource that might become necessary. He noted this change in his relationship with the cheat and considered it for a long moment on Thursday evening. It was becoming a habit of readiness. This was not bad — a tool that was available when needed was more useful than a tool that took time to locate — but it was a change in how he carried it, and changes in carrying habits were worth noticing.

He thought about the three uses and what they had in common. All three had been reactive — the situation had reached its crystallization point and he had responded. The first: Sun's forged document in month one, Day Four, when the crystallization had been the moment he realized the signature was wrong and the wrong signature was going to be attributed to his co-signature. Sixty seconds to find the correct document and substitute it cleanly. Moderate headache for an hour. The second: Sun's forged budget authorization in month three, Day Seventy-two, when the crystallization had been the realization that signing would implicate Lao Wei retroactively. Sixty seconds to identify the forgery and prepare the counter. Mild headache. The third: the press release in month four, Day Eighty-four, when the wrong industrial unit count would have been published under the General Office's name. Sixty seconds to identify the source discrepancy and correct it. Ten-minute mild. Three uses, three emergencies, three correct responses. Cost calibrating downward with experience.

In none of these cases had he held it ready in advance. It had been triggered by the crystallization event. Now, in the tense week, he was holding it ready throughout the day — before the crystallization event, before the emergency. This was new. He was not sure whether it was prudent or anxious. He thought: probably prudent. A cheat that arrives before the crystallization point is usable. A cheat that only arrives at the crystallization point is not always fast enough. He was pre-loading it.

He thought: three uses in seven months, calibrating downward (moderate, then mild, then ten-minute mild). The cost had been calibrating in the direction of sustainability. He did not know whether the capability had been calibrating in any direction. He knew only what he had: sixty seconds, reliably, at ten-minute-mild cost.

He thought: what if it was more than sixty seconds now?

---

Friday evening. The section floor emptied between five and five-thirty. By five forty-five Lin was alone — Lao Wei had left at five-fifteen, the others at various points between. The feasibility study's Finance Bureau data had arrived and he had it open on his desk. The data was good and his preliminary analysis was clear. He set it aside.

He sat at the empty section desk and thought about the cheat.

He had been thinking about this for two weeks — since the Monday when Lao Wei's almost-smile had confirmed the change, since the Director's assignment had confirmed the move to 行, since the tense week had confirmed that the cheat was now something he held habitually. He thought: I have used Tier I three times. I know it as sixty seconds. I know the costs calibrated. I don't know whether sixty seconds is the ceiling of what exists or a measure of where I currently am. The first use had been the first crystallization of something the cheat had always been capable of; the subsequent uses had been the calibration of that capability's cost. Could the capability itself calibrate?

He would find out.

He sat with the section floor's early-evening quality — the overhead lights still on, the section's ambient noise reduced to the building's background — and tried to rewind ninety seconds.

The first sixty seconds: familiar. The room reorganized with the now-known quality — not literal time reversal, but the functional equivalent, the sensation of the present moment reorganizing itself around a different version of the preceding sixty seconds. He held it. He had always released at sixty seconds before, either because the situation was resolved or because he had not considered going further. Now he held it past sixty. He felt the extension: the same sensation, continuing past the point where he had always stopped, going deeper into the reorganization, the room at sixty-five, seventy, eighty seconds having the quality of something more completely rewritten than the sixty-second version.

He held it to ninety.

The world, at ninety seconds, had the quality of a depth he had not been in before. Not frightening — he understood what was happening. But deeper. More completely reorganized. He had the full ninety seconds.

Then the cost arrived.

---

It arrived all at once, which was different from the previous three uses, where the cost had been delayed by the adrenaline of the situation. This time there was no situation — he had tested it deliberately, in a quiet room, and the migraine arrived with nothing to buffer it. Not the moderate headache of the first use or the ten-minute mild of the third. A genuine migraine: the sharp pressure behind the eyes, the specific intolerance of light that made the section's overhead fluorescents immediately unbearable, the nausea that was the body's response to something that had happened in its neurology that the body did not have good language for.

He turned off his desk lamp. He sat in the reduced light from the corridor for approximately three minutes while the worst of the initial wave passed. Then he packed his bag and signed out and walked home.

The canal path in the early March evening: cold still, the canal running clear again now that the February ice was gone, the plane trees in the pre-spring state before the leaves arrived. He walked it with the migraine pressing steadily against the inside of his skull. He was in no danger — the migraine was sharp but stable, not intensifying. He got home and went to the room and turned off the light and lay down in the dark.

Two hours.

---

He lay in the dark and thought about what he had learned.

Tier I had been sixty seconds. Tier II was ninety. The difference was thirty seconds, which was fifty percent more time. The cost had spiked from ten-minute mild to two-hour migraine. The ratio was not comfortable — the cost had not calibrated downward in proportion to the capability increase; it had spiked upward. He noted this: Tier II costs more per use than Tier I. It costs more because it is more. This was proportion, not disproportionality. The cheat gave what it gave and took what it took, and both had grown together.

He thought about what ninety seconds could do that sixty seconds could not. The most obvious: more time to observe and respond in a situation that was developing rapidly. Sixty seconds had been enough for the three emergency uses. Ninety seconds would be enough for situations that sixty was not enough for. He did not know yet what those situations would look like. He would know when they arrived.

He thought about the three emergency uses and applied the ninety-second frame retroactively, in the way of a person calibrating a tool against known reference points. The first use, Day Four: with ninety seconds rather than sixty, he would have had time not only to identify the document discrepancy but to review the full routing sequence and confirm whether Sun had modified only that document or whether there were companion modifications. He had not had that time with sixty seconds. The second use, Day Seventy-two: with ninety seconds he could have traced the budget authorization discrepancy back to its originating record, which might have given him more than the immediate counter — might have given him the source-document chain. The third, Day Eighty-four: the unit count discrepancy had been resolved in under forty seconds; the remaining twenty had been used for verification. With ninety he would have had the same resolution time and more verification. More verification was more safety.

The capability grew and the capability was useful. The cost grew in proportion. This was the arrangement. He would use Tier II for the situations that required it and Tier I for the situations that did not require more than sixty seconds and he would not use either when neither was necessary. This was the rule he had always been following; it simply now had two tiers instead of one.

He lay in the dark until the migraine passed, which was two hours. Then he got up and made tea and sat at the desk in the lamplight and looked at the 行 character on the wall.

He wrote in the private notebook: *Tier II — 90 seconds confirmed. Cost: 2-hour migraine (sharper than Tier I). Used deliberately, not under emergency. The cheat grows. Use Tier II only when Tier I is insufficient. Note for future: do not test capability changes without time to recover. The pre-loading habit (holding the cheat ready throughout the tense week without deploying) is noted as a development in how I carry the tool. Monitor whether this habit becomes useful or becomes anxiety. Currently: probably useful.*

He closed the notebook.

He thought: the cheat is alive. It is growing the same way he is growing, which suggested some relationship between the two growths that he did not have language for and did not need language for. What he needed was the correct use, which was what he had always used it for: the correct use, the correct moment, the correct tier for the situation. He had these now in a Tier II form as well as a Tier I form. This was strictly better than what he had last week.

He did not know whether Tier III existed. He suspected it did. He was not going to find out tonight.

He slept at ten.

---

Previous31 / 110Next

Comments (0)