Chapter 169: Template and Margin

At six in the morning, gray-white light seeped through the gap in the guesthouse curtains. When Lin Chen woke, the swelling in his left ankle had already spread to his calf. He sat on the edge of the bed, slowly lowered his foot into a plastic basin, and applied a warm compress. The rippling water reflected the dark circles under his eyes. On the nightstand lay a kraft paper envelope. He tore it open, pulled out the bills, and counted them one by one. Twelve hundred. Rough-edged, worn notes carrying the mixed scent of machine oil and sweat. He set aside one hundred fifty, bound the rest with a rubber band, and tucked it into his inner pocket. One hundred fifty would cover two tubes of Yunnan Baiyao, three days of boxed meals, round-trip bus fare to the provincial department, and printing and binding fees. The remainder was his buffer. He couldn’t put all his eggs in one basket, even if the basket looked like it was forged from iron.

At seven, he sat at the desk and opened the shockproof case. Inside were the terminal, a TF card, and printed log sheets. He spread out the iteration records for V2.0 and V3.0, selecting the three most critical pages: the uneven wear characteristic curve, the sliding window filtering logic, and the offline caching mechanism. With a black gel pen, he annotated key parameters in the margins. His handwriting was neat, devoid of a single wasted word. The provincial department wanted “reference value,” not an academic paper. He had to translate technical jargon into the language of cost: how much downtime would be reduced, how much the false alarm rate would drop, and within what range hardware costs would be kept. He opened his mistake notebook and wrote on a blank page: Meeting objectives: 1. Confirm data compliance; 2. Clarify pilot scope; 3. Obtain subsequent interface permissions. The pen tip paused. He remembered Director Wu’s words: “The factory doesn’t feed idle hands.” It was the same within the system. They didn’t care how elegant the code was; they only cared whether risks could be contained and whether the accounts balanced.

At eight-thirty, he slung the shockproof case over his shoulder, locked the door, and headed downstairs. When his left foot touched the ground, the fascia felt as though it were being scraped by a dull blade. He shifted his weight, stepping forward with his right leg first and dragging his left half a step behind. His gait was slightly limping but rhythmically steady. At the bus stop, the morning rush hour crowd pressed in. He stood in a corner, keeping clear of the shoving. The shoulder strap of the case dug into his collarbone, its weight pressing down on his spine. He closed his eyes and ran through his reporting logic in his head: conclusion first, then data, finally boundaries. Never promise what couldn’t be delivered; never hide known flaws. The bus swayed for forty minutes before pulling into the Provincial Government Center stop. The building was gray-white, its glass facade reflecting the early autumn sun. Security check, registration, visitor badge issued. Outside the third-floor conference room, people were already waiting. A middle-aged man in a jacket, a young man carrying a briefcase, and two technicians wearing factory ID badges. The air carried a faint scent of tea and paper.

At two o’clock sharp, the door opened. The deputy director of the Equipment Division from the Provincial Department of Industry and Information Technology led his team in, followed by two note-takers. There were no pleasantries; they went straight to the point. “Student Lin Chen, right? We’ve reviewed your logs. The field data is very solid.” The deputy director flipped through the printouts. “But a pilot isn’t a laboratory. The production line environment is complex—dust, voltage fluctuations, operator errors. How long can your script hold up?” Lin Chen stood up and connected the terminal to the projector. The screen lit up, and the curves expanded. “It’s currently deployed on the stamping press of the Phase II line, running continuously for thirty-six hours. The hardware uses an industrial-grade three-proof board, and the script has built-in sliding window filtering and offline caching. Voltage fluctuations within ±10% do not affect the core logic. The false alarm rate has dropped from twelve percent to one point four percent.” His voice was quiet, his pace steady. “Hardware cost per unit is kept under eight hundred. Deployment takes two hours. It doesn’t require modifying the original PLC; it only reads sensor data.”

The deputy director nodded and turned to the note-taker beside him. “Write that down. Cost: eight hundred. Deployment: two hours.” He looked back at Lin Chen. “What about the boundaries for data cleaning? If the raw sensor itself drifts, how does your algorithm distinguish between equipment failure and sensor aging?” Lin Chen was prepared. He pulled up another chart. “Node B’s temperature probe showed a slow drift of half a degree at the thirty-second hour. The script didn’t trigger an alarm because of the baseline adaptive threshold setting. But I flagged it in the log. I recommend the factory calibrate the probes quarterly, or add a drift compensation module to the script. That would require additional calibration data.” The deputy director was silent for a few seconds, his fingers tapping the tabletop. “The factory can provide the calibration data. But for now, the pilot scope is limited to a single line. Run it for a full quarter. If the downtime rate drops by fifteen percent, we’ll discuss Phase II expansion.”

The meeting ended at three forty. There was no applause, only the rustle of paper and the scrape of chairs. The deputy director handed over a business card. “Old Chen, Equipment Division. Send the pilot implementation plan and budget breakdown to my email before next Monday. Format it according to the provincial department’s standard template.” Lin Chen accepted it with both hands and nodded in thanks. Stepping out of the building, the wind felt cooler than it had in the morning. He leaned against the steps and slowly took off his safety shoes. His left ankle was swollen and shiny, the skin pulled tight. He sprayed the medicine; the cold sting was piercing. His phone vibrated. It wasn’t Old Chen. It was Professor Zhou. The text was only two lines: How did the provincial department meeting go? I have a Yangtze River Delta industrial IoT project here lacking a data cleaning interface. If you're free, come to the lab on Thursday. Bring your V3.0 source code.

Lin Chen stared at the screen, his thumb hovering over the reply key. He typed: Went well. Secured pilot intent. Will be there on time Thursday. Sent. He slipped the phone back into his pocket and picked up the shockproof case. Sycamore leaves carpeted the steps below, emitting a faint crunch under his weight. He began walking down, his gait still slightly uneven, but his breathing steady. The next step was drafting the proposal. But the provincial department’s template required a corporate seal and a legal representative’s signature. He currently only had a personal identity. Thursday’s visit to the lab meant another, longer road ahead. The wind swept through the corridor, stirring the fallen leaves on the ground. He glanced down at the dust on the toe of his shoe and kept walking forward.