Chapter 220: Thresholds and Margins

Five in the morning. The alarm had not gone off, yet Lin Chen was already awake.

The hospital room was still dim, lit only by the bluish glow of the monitor screen. Xiaoman slept deeply, breathing evenly, his left hand unconsciously clutching the corner of the blanket. Lin Chen got up as quietly as possible. When his left foot touched the floor, a familiar dull ache rose from his ankle. Bracing himself on the bedframe, he stood straight, took a collapsible basin from his bag, and went to the hot-water room at the end of the corridor. The water was just the right temperature. He wrung out the towel and wiped Xiaoman’s face and hands. His movements were very gentle, afraid of waking him. When the towel brushed past his younger brother’s temple, he could feel that the skin was a little warmer than usual. He noted it silently and said nothing.

Six twenty. Lin Chen returned to the apartment. Last night’s notebook of mistakes and half a packet of instant noodles still lay open on the table. He boiled water, made himself a fresh bowl, and added a braised egg. Then he sat down at the computer and powered it on. The terminal window popped up, the log stream frozen at the breakpoint from the night before. He did not rush to run the data. Instead, he opened a browser first and logged into the National Copyright Administration system. The PDF of the software copyright acceptance notice had already been downloaded, its registration number clearly visible. He created a new folder and named it “IP_Compliance_Package_20241114.”

Inside, he placed three things: a scanned copy of the acceptance notice, screenshots of the core code repository’s Git commit history from the past three months with timestamps and commit hashes, and the key pages from the draft third-party security assessment report. He also wrote a brief “Declaration of Independent Intellectual Property Rights for the Core Algorithm,” phrased with restraint and stating only facts: the algorithm architecture was independently developed, the official filing had been submitted and accepted, repository permissions were access-controlled, and there were no external licensed dependencies. At the end, he attached a legal liability undertaking. What finance wanted was not technical principles, but written proof of risk isolation. He understood that clearly.

Seven forty. He packaged the files, encrypted them, and sent them to Chen Hao. Attached message: “The backing finance asked for is here. Please proceed with the advance payment milestone according to the original contract, otherwise the final stress test for Thursday’s demo environment cannot be completed. Compliance is a bottom line, not a bargaining chip.”

Sent successfully. He closed the email client and opened the data-cleaning script. Five hundred thousand rows of raw data had already been decompressed. He adjusted the fault-tolerance parameters for version 3.0, relaxing the anomaly-capture threshold from 10% to 15%, while adding an automatic quarantine mechanism. Dirty data would no longer freeze the main process, but would instead be diverted into an independent queue and marked “Pending Manual Review.” He pressed Enter.

The screen began to scroll. CPU usage crept upward, and the fan let out a low hum. He leaned back in his chair and closed his eyes. His left foot rested on another chair, knee slightly bent to ease the pressure on venous return. The braised egg and noodle broth brought a little warmth to his stomach. He knew there were no shortcuts in technology—only parameter tuning and boundary testing. Every line of code consumed computing power, and consumed the margin of his own energy as well.

Eight fifteen. His phone vibrated. A hospital caregiver had sent a message: “Mr. Lin, there are quite a lot of people waiting for the EEG room. We suggest arriving half an hour early.”

Lin Chen opened his eyes. The script’s progress bar had reached 32%. He saved the logs, closed the laptop, went out, and hailed a cab.

There were already more than a dozen people lined up outside Neurology Room One. The smell of disinfectant mingled with the scent of old newspapers. Holding Xiaoman’s medical file, Lin Chen sat on a plastic chair and waited. His left foot could not bear standing for long, so every ten minutes he shifted his weight. An elderly woman beside him muttered complaints about how hard it was to get an appointment. He listened without replying. Reality was simply like this: resources were always scarce, and waiting in line was the norm. The only thing one could do was prepare early and keep variables within an acceptable range.

Nine twenty. Their number was called. Xiaoman was wheeled into the examination room. Standing outside the glass window, Lin Chen watched the technician attach electrode pads to his head. Xiaoman looked a little nervous, his fingers curling slightly. Through the glass, Lin Chen gave him a nod. Xiaoman recognized him and tugged faintly at the corner of his mouth—a sort of smile.

The examination would take forty minutes. Lin Chen walked to the vending machine at the end of the corridor and bought a bottle of mineral water. He unscrewed the cap and took a sip. The cold water slid down his throat and pressed down the faint, restless unease in his stomach. He took out his phone and checked WeCom. Chen Hao had replied: “Finance has received the materials. The advance payment process has been expedited and is expected to arrive tomorrow morning. I’ve already spoken to President Wu. The demo will proceed as originally planned.”

Lin Chen replied with a single: “Received.” Nothing more.

Ten o’clock. Xiaoman was wheeled out. The technician handed over a preliminary report: “Background activity is basically normal. No obvious epileptiform discharges observed. Clinical observation is recommended in conjunction.”

Lin Chen took the report, his fingertips tightening slightly. He thanked the technician and helped Xiaoman back to the ward. His younger brother looked a little better than he had the night before and could sit up to drink water on his own. Lin Chen tucked the report into the medical file and said nothing. He knew an EEG was only a slice, not a verdict. Illness fluctuated, just like hidden bugs in code: when they were not triggered, everything seemed normal; once triggered, they became an avalanche. The only thing to do was keep monitoring and keep contingency plans ready.

Eleven thirty. Lin Chen returned to the apartment. The script’s progress bar had reached 89%. He opened the terminal and checked the logs of the quarantine queue. The dirty data was mainly concentrated in two categories: chaotic timestamp formats and missing fields. He wrote a temporary patch, using regular expressions to batch-repair the timestamps, while filling missing fields with default values and tagging them. Then he reran the validation. The pass rate rose to 94.6%.

He rubbed the bridge of his nose. His left foot had started to go numb, as if fine needles were pricking beneath the skin. He stood up and walked two circles around the room. His gait was slightly limping, but steady in rhythm. He went to the window and pulled back the curtains. The early winter sunlight streamed in, falling across the desktop, and dust drifted slowly in the shaft of light.

One in the afternoon. He changed into a dress shirt and packed the demo USB drive, the contract draft, and a photocopy of the EEG report into his briefcase. He checked the sandbox environment’s access permissions one more time. The IP whitelist had been updated, and read-only mode was locked. At last, he glanced at the notebook of mistakes.

“Article 220: Compliance materials are a door-opener, not an immunity card. The fault-tolerance rate for data cleaning must align with the SLA. Stable symptoms are a short-term positive, but the long term still depends on medication and monitoring. Time management is not squeezing water from a sponge; it is cutting a cake. Each piece has a fixed use and cannot be misappropriated.”

He closed the notebook and left.

One fifty. He arrived at the office building. The elevator went up. The corridor was quiet. He pushed open the meeting-room door. President Wu and his assistant were already there. Chen Hao sat to one side and gave him a slight nod.

Lin Chen connected his computer to the projector. The screen lit up. Without exchanging pleasantries, he opened the terminal directly. The sandbox environment launched. The log stream rolled onward. He pulled up the data-quality dashboard. Five hundred thousand rows of data. Cleaning completion rate: 94.6%. Quarantine queue ratio: 5.4%. System latency stable at 11 ms.

“These are the actual results from a live run,” Lin Chen said. “We are not concealing dirty data, and we are not exaggerating performance. The SLA commits to 99.5% availability, based on the current data-source quality. If any new data the client provides later exceeds the preset fault-tolerance range, the cleaning cost will need to be reassessed.”

President Wu looked at the screen, fingers tapping lightly on the table. The assistant handed over a document. “Mr. Lin, finance has approved the advance payment process. But the CTO added a temporary requirement: after the demo, you’ll need to provide an interface document for ‘data lineage tracing.’ By next Monday.”

Lin Chen paused. Data lineage tracing. That meant adding a metadata-management layer to the current architecture to record the source, transformation logic, and destination of every piece of data. Development alone would take at least a week, and testing another three days. By next Monday—that was too tight.

“That can be done,” Lin Chen said. “But the client will need to open access to the raw data source and provide a field mapping table. Otherwise the lineage chain will break. We can deliver the interface document next Wednesday, leaving two days for integration testing.”

President Wu glanced at him without speaking. The assistant made notes in a notebook. Chen Hao cut in, “President Wu, technical implementation takes time. If we force the schedule, it’s easy for vulnerabilities to appear. Next Wednesday would be safer.”

President Wu nodded. “Do it your way. But the demo environment must remain stable. There’s an internal review at two thirty this afternoon. Prepare yourselves.”

Lin Chen closed the computer. He knew the review meeting was only a formality; the real test would come in operations after deployment. He rose and shook hands with President Wu. His grip was still measured.

As he walked out of the meeting room, his phone vibrated. It was not a work message, but one from the hospital caregiver: “Mr. Lin, Xiaoman has a slight fever this afternoon, 37.8°C. The doctor has seen him and says it’s an ordinary infection. They prescribed antipyretics. But the formal EEG report will be out this afternoon, and your signature is required for confirmation.”

Lin Chen stopped walking. Cold air poured from the ventilation outlet into the corridor. He looked down at the screen, his fingers hovering over the keyboard for two seconds.

He replied: “Understood. Give the antipyretics on schedule. Send me a scan of the formal report once it’s out. I’ll be back before three this afternoon.”

Sent. He strode toward the elevator. The pain was sharp when his left foot hit the ground, but he did not stop. In his mind, the timetable was already being rearranged: two thirty internal review, three o’clock back to the hospital, four o’clock verify the advance payment had arrived, evening run through the architecture draft for data lineage tracing. Time had been cut into even smaller pieces, but each piece still had a clearly defined boundary.

The elevator descended. He leaned against the wall of the car and closed his eyes. In his mind, he was already breaking down the modules for lineage tracing: metadata capture, transformation logs, dependency graph. The technical path was clear, but manpower was insufficient. He needed to hire a backend engineer, or make the current team work overtime. Cash flow had only just begun to recover. Expansion was impossible for now. He could only carry it himself.

His phone vibrated again. A message from Chen Hao: “President Wu is very satisfied with the demo. But someone internally raised a point—if your cleaning engine were connected to a real-time stream, could the latency be pushed below 5 ms? They want to use that as a selling point for phase two planning.”

Lin Chen stared at the line of text. Real-time stream. 5 ms. That meant rebuilding the message queue and replacing the existing batch-processing architecture. It was not something a patch could solve.

He stepped out of the building. Early winter wind scraped across his face. He took out his phone and replied: “A real-time streaming architecture would need to be redesigned from the ground up. A 5 ms latency is a theoretical value under current hardware conditions; in an actual production environment it would be affected by network fluctuation. We can discuss it for phase two, but phase one must prioritize stability. Technology does not sell fantasies; it delivers verifiable metrics.”

Sent. He flagged down a taxi and gave the hospital address. Outside the window, the city slid backward. He opened the notebook of mistakes, and the tip of his pen scratched softly across the paper.

“Article 221: Requirements always expand; resources always contract. Holding the phase-one SLA matters more than promising phase-two performance. A low fever is a variable; the advance payment is a buffer. Next steps: return to the hospital to sign the report, work on the architecture draft, assess the feasibility of a real-time streaming overhaul. Bottom line: do not overload, do not cross the red line.”

He closed the notebook. The taxi turned onto the hospital side road. The beeping of monitors, the tapping of keyboards, the howl of wind through the buildings wove together in his mind into a single net. He knew there would be new checkpoints tomorrow. But tonight, all he needed to do was elevate his left foot and sleep for five full hours.

The car came to a stop. He pushed open the door and stepped out, limping slightly, but certain of his direction. The light in the hospital room at the end of the corridor was still on, like an unfailing star.