Chapter 317: Probes and Margins

The log export progress bar on the screen hit one hundred percent. Lin Chen dragged the packaged, sanitized hash list into an encrypted archive, set a decompression password, attached a screenshot of the clauses from Contract Appendix Three, and sent it all to Engineer Li. The moment the notification confirming successful delivery popped up, the wall clock read 1:17 AM. The office was empty except for him. The air conditioning vent emitted a low, steady hum, like the breathing of some massive machine. He leaned back in his chair. The dull ache in his left ankle grew sharper as blood flow returned. He didn’t rub it. Instead, he shifted his full weight to his right leg, letting his left foot and its old injury hang suspended. Pain was an objective physical parameter. It didn’t need to be fought; it only needed to be managed.

He switched back to the terminal and began deploying the batch optimization script. The routing rules for the canary release required line-by-line verification. The logic for if retry_count > 3: drop_request was already hardcoded, but the accumulation of long-tail requests would inevitably cause a hidden memory leak. He opened the monitoring dashboard and lowered the threshold alarm line from 4.5 percent to 4 percent. Leaving a 0.5 percent buffer gave the system room to breathe, and it provided the team with a fault-tolerance margin. The compilation progress bar advanced slowly. He stared at the screen, keeping his breathing light. Code wasn’t written; it was tested. Every commit was a step onto unknown terrain, a way to check if the ground beneath was solid.

Su Man’s avatar lit up on DingTalk, followed by a voice message: “Degradation script fully deployed. Core link latency pushed back to 180 milliseconds. Edge node load dropped to 72 percent.” Lin Chen replied with a single “Received.” No extra words. He knew data didn’t lie, but it did lag. The real test would come during tomorrow’s morning peak. He closed his laptop, stood up, and walked to the pantry to get water. The corridor’s motion-sensor lights flickered on one by one with his footsteps, then extinguished behind him in sequence. His reflection appeared in the glass window: shoulders slightly hunched forward, but his spine perfectly straight. Ninety days wasn’t a countdown; it was a survival line. The numbers in the ledger had to balance, just like when he used to help his father tally the autumn harvest accounts back in Qingshi Village. Stroke by stroke. No mistakes allowed.

At 9:50 AM, a notification popped up in the finance group chat: Bridge funds received. Lin Chen opened the corporate online banking portal. The number was long, but he only looked at the digits before the decimal point. He pulled up the fund allocation table. Cloud server expansion took 40 percent, this month’s team payroll took 35 percent, 15 percent was reserved for emergency turnover, and the remaining 10 percent he allocated to a separate sub-account, labeled: Medical & Family Reserve. He dialed the county hospital. The pharmacist on the other end was an old acquaintance, his voice carrying its usual weariness: “Lin Chen, the new batch of sodium valproate sustained-release tablets just arrived today, but the cold-chain truck is stuck on the national highway. It probably won’t be warehoused until this afternoon. Your brother’s dosage can’t be interrupted, so I’ll pull two boxes from the reserve stock and ship them to you via SF Express cold chain.” Lin Chen noted the tracking number and thanked him. After hanging up, he opened his mistake notebook and wrote: Funds received. Cloud resource expansion complete. Drug cold chain delayed; reserve stock allocated. Next: Verify enterprise Q3 renewal intent. The pen tip paused, then he added: Old foot injury relapsed; need to replace support insoles.

By 10:30 AM, the office gradually filled up. The clatter of keyboards, the click of mice, and low murmurs of discussion once again filled the space. Lin Chen carried his thermos to a desk in the back row. The newly hired algorithm engineer, Xiao Zhou, was frowning at his screen, fingers hovering over the keyboard. On the monitoring dashboard, API call volumes for a non-core module were showing abnormal fluctuations. Lin Chen pulled over a chair and sat down. Without asking “what’s going on,” he switched directly to the logs. “The retry storm wasn’t blocked. Your backoff algorithm uses a fixed interval. The moment the third-party interface rate-limits, all your requests pile up in the queue.” Xiao Zhou’s face flushed, his fingers trembling slightly. “I thought… fixed intervals would be more stable.” Lin Chen opened the code editor, deleted the line, and rewrote it: “Exponential backoff with random jitter. delay = base_delay * (2 ** attempt) + random.uniform(0, 1). The system isn’t a vacuum. External dependencies will always jitter. You have to leave room for it.” Xiao Zhou stared at the screen, taking notes rapidly. Lin Chen stood up and patted the back of his chair. “Don’t be afraid of errors. Errors are the system telling you where the boundaries are. Document this anomaly in the post-mortem report, and we’ll review it at tomorrow’s stand-up.”

In the afternoon, the audit probe’s request frequency stabilized at three times per hour. Engineer Li stopped pressing for details on the weight adjustments, but every log pull timestamp landed exactly on the hour. It was a silent form of pressure. Lin Chen knew Zhao Qiming was waiting for a slip-up. Ninety days wasn’t about who ran the fastest; it was about who made the fewest mistakes. He opened the cost allocation model. The unit inference cost curve had finally dipped below the average, stabilizing two percent beneath the red line. The buffer had widened. But he didn’t relax. He pulled up the enterprise client renewal intent sheet. Out of seven core clients, three had confirmed renewal, two were still on the fence, and one had explicitly switched to a competitor. The competitor’s quote was thirty percent lower. Lin Chen drew question marks next to the “on the fence” and “switched” columns. A price war was a drain on cash flow, and they couldn’t afford to fight it right now. They could only compete on delivery quality and response speed. He sent a message to the head of sales: Do not engage on pricing. Bring the technical team on-site for scenario stress tests. Let the results speak.

At 8:00 PM, Su Man walked over and handed him a cup of warm water. “Zhao Qiming’s post-investment team sent an email this afternoon. They’re requesting a technical alignment meeting next Monday afternoon. Nominally, it’s a ‘compliance post-mortem,’ but in reality, they’re auditing our iteration roadmap.” Lin Chen took the cup, the warmth seeping through the glass into his palm. “Let them look. The roadmap stays on the original schedule. No acceleration, no deceleration.” Su Man nodded, then hesitated. “During the post-mortem today, Xiao Zhou mentioned that the batch of medical vertical training data from two months ago seemed to have mixed in some unstructured noise during cleaning. We were rushing to meet the deadline back then and skipped secondary validation.” Lin Chen set the cup down. His movements were deliberate and light. He pulled up the data version management records. Batch_Med_20240412. That timestamp coincided exactly with the period when his left foot injury had been at its worst, during consecutive nights of running scripts. He opened the raw logs. The hash values matched, but within the weight change timestamps, there was a minuscule offset. The offset was only 0.003 seconds—something that would be ignored in a routine audit. But in Zhao Qiming’s probe model, it could easily be flagged as “data contamination” or “weight drift.”

Lin Chen stared at the screen. The cold white light reflected the exhaustion in his eyes. He picked up his pen and wrote on a fresh page of the mistake notebook: Audit probe captured timestamp offset. Suspected residue from early cleaning noise. Need to trace original data shards. The pen tip pressed hard into the paper, leaving a clear indentation. The ninety-day countdown had only just passed its third day. The second page of the ledger had already been turned into the shadows. He turned off the main monitor, leaving only the monitoring dashboard active. In the bottom right corner of the screen, the probe request frequency jumped again. This time, it carried a new parameter: Request verification: Batch_Med_20240412 weight consistency review. Lin Chen didn’t move. He knew the probing phase was over. The next round had officially begun.