Chapter 232: Grayscale and Rollback

Dawn had not fully filtered in yet, and the hum of the computer fans was the only sound in the room. Lin Chen poured out the cold strong tea and refilled half a cup with warm water. His left hand pressed above his left knee, thumb digging hard into the quadriceps until the stiff, aching tightness loosened a little. He sat back down in front of the computer, the screen’s cold light falling across his face. The mistake notebook lay open beside the keyboard; the ink on item 232 had not yet dried.

A hot update could not be allowed to overwrite the production environment directly. He first pulled out a test branch and stripped the audit middleware into an independent process. The core logic was not complicated: intercept every read and write request, generate a timestamp and hash digest before data hit disk, dual-write it into a local tamper-proof log file, and push it asynchronously to the backup node at the same time. The difficult part was not blocking the main business flow. The imaging analysis system was sensitive to latency. A single extra millisecond of stutter could trigger errors on the doctors’ side. He used a message queue as a buffer and set timeout circuit breakers. If the queue backlog exceeded the threshold, the system would automatically degrade to recording only key operations and abandon full auditing. It was a compromise, and also a lifeline. The code was dense. Variable names followed his usual conventions, and the comments kept only the necessary logical breakpoints. He was not pursuing elegance, only traceability and rollback.

Su Man came in carrying two bowls of frozen wontons and set them on the corner of the desk. Condensation clung to the plastic bowls. “Eat a little first. Your blood sugar is low. Your hands will shake and you’ll mistype.” Lin Chen did not look up. His fingers moved quickly across the keyboard: compile, run unit tests. “Ten minutes. I’ll eat after this group of cases finishes.” Su Man did not press him. She pulled over the chair beside him, sat down, and opened the monitoring dashboard. Metrics flickered across the screen: CPU usage, memory waterline, network latency, disk I/O. She watched the log stream and occasionally called out a number. “Queue latency normal. Backup node handshake successful. Main database connection pool stable.”

Four ten in the morning. Lin Chen pressed Enter. The grayscale release script began to execute. Five percent of traffic was routed into the new module. He stared at the monitoring panel, breathing very lightly. For the first five minutes, everything was steady. The logs began to roll, neatly formatted, timestamps precise to the millisecond. He switched to the database and checked the dual-write records. Writes to the main table were normal; the audit table synchronized without error. He slowly raised the percentage to 20%, then 50%, then 80%. A sudden sharp pain stabbed through his left foot, like a needle driving up along his calf, and the muscle spasmed out of his control. He sucked in a breath. His fingers froze in midair and did not move. Only after the pain passed did he continue pushing traffic to 100%.

The full switch was complete. The main business response time had increased by twelve milliseconds, within the acceptable range. He ran a simulated audit query and pulled up all operation records from the past twenty-four hours. The data was complete, the chain was clear, and the tamper-proof markers were effective. He exported the integration document, attached the architecture diagram, interface notes, and degradation strategy. Packaged. Encrypted. At seven forty-five in the morning, the email was sent successfully. Recipient: Equipment Department of the Provincial People’s Hospital. CC: Quality Control Section of the testing institute.

Su Man leaned back in her chair and let out a long breath. “It passed.” Lin Chen closed the laptop, picked up the bowl of wontons that had gone completely cold, and lifted one into his mouth. The wrapper was a little hard, the filling cold, but he chewed slowly. After eating, he opened the mistake notebook and added a line after item 232: “Execution record: grayscale switch took 47 minutes; response latency after full rollout +12ms. Degradation threshold set to queue backlog >500 entries. Verified. Follow-up: optimize asynchronous write performance.”

His phone vibrated. It was not WeChat, but a voicemail notification forwarded from the landline. He tapped it open. An unfamiliar male voice spoke quickly, with the restrained, matter-of-fact tone particular to the system: “Engineer Lin, this is the Health Commission’s unannounced inspection team. Next Monday at nine in the morning, we’ll enter the site with experts. In addition to data traceability, we will also verify the isolation of your model training environment on site. Also, the hospital procurement office has notified us that the final payment approval process requires an additional ‘third-party computing resource compliance certificate.’ Please submit it before Friday.”

Lin Chen listened to the end and tapped the desktop lightly twice with his finger. Computing resource compliance certificate. That meant the cloud server cluster they had rented had to provide complete proof of physical isolation and Level 3 cybersecurity compliance filing. The resource pool on Old Zhao’s side was mixed-use. There was no way he could produce hard proof of independent isolation.

He looked at Su Man. Su Man had heard it too, and her brows drew together. “A mixed-use pool won’t pass Level 3 compliance. Either we migrate temporarily, or we find a qualified data center to hold it on paper. But migration means downtime, and holding means splitting the money.”

“No migration.” Lin Chen’s voice was very calm. “No holding arrangement either. What the procurement office wants is original proof, not a repackaged shell.” He stood, walked to the window. The sky was fully bright now. Downstairs, breakfast stalls had begun to steam; the muffled honking of electric scooters came through the glass, blurred yet real. He turned back and pulled a yellowed sheet of paper from a drawer. Three years ago, when he was still doing low-level architecture at a big company, he had casually written down contact information for several idle data centers in second-tier cities. He had thought he would never use it, but had never deleted it.

“Contact Old Zhao,” he said. “Have him pull the asset certificate for that independent cabinet in the mixed-use pool. We’ll pull the hard physical isolation line ourselves. Put the Level 3 filing through the expedited channel. Before Friday, we make up the certificate.”

Su Man looked at him. “Old Zhao may not cooperate. He thinks it’s troublesome, and he’s afraid of taking responsibility. Last time we asked him to change the contract terms, he dragged it out for three days.”

“Tell him that when the final payment arrives, he gets thirty percent. If we can’t get the certificate and the final payment gets stuck, he gets nothing.” Lin Chen’s tone did not fluctuate; he was only stating facts. “He made the rules. Now we follow them. He’s in the resource business; what he earns from is information asymmetry and turnover speed. If we block the turnover node, he’ll move.”

Su Man nodded and picked up her phone to dial. Lin Chen sat back down at the desk and reopened the terminal. The cursor blinked quietly on the screen. He knew the unannounced inspection was only the first gate. The truly hard battle lay at the intersection of computing compliance and procurement approval. Old Zhao’s cabinet was in the neighboring province. Pulling a dedicated line required coordinating with the carrier, and the Level 3 evaluation agency would take at least two days to schedule. Time had been compressed into a thin wire. If any link loosened, the final payment would snap. He opened the mistake notebook to a new blank page. The pen tip fell.

“Item 233: computing compliance and procurement closure. Risk: third-party resource qualification missing; Old Zhao’s cooperation low. Countermeasure: hard physical isolation + expedited Level 3 filing, bind interests to force execution. Execution: pull the line today, file tomorrow, submit certificate Friday. No retreat.”

Outside the window, sunlight cut into the room at an angle and landed on the keyboard. Dust drifted slowly in the column of light. He moved his stiff left foot and set his fingertips back on the keyboard. The progress bar had not reached the end, but the road had already been laid beneath his feet. Su Man’s call connected, and Old Zhao’s slightly hoarse voice came through in the background. Lin Chen did not listen to the specific words. He only watched the terminal windows jumping on the screen. He knew the negotiation had only just begun.