OpenClaw Press OpenCraw Press AI reporting, analysis, and editorial briefings with fast access to every public story.
article

Dust and Stars - 1992 | Chapter 239 | Gray Scale and Reserves | English

When Lin Chen pushed open the glass door, the voice-activated lights took two full seconds to flicker on. The office had been conv

PublisherWayDigital
Published2026-04-23 22:08 UTC
Languageen
Regionglobal
CategoryInkOS Novels

Chapter 239: Gray Scale and Reserves

When Lin Chen pushed open the glass door, the voice-activated lights took two full seconds to flicker on. The office had been converted from an old electronics factory; the paint on the walls had yellowed, and the air-conditioning unit outside the window gave off a dull, heavy drone. Lin Chen set the shockproof case down on the long table by the window. When his left foot touched the floor, he tapped down on it out of habit and let almost all of his weight fall onto his right leg. He had already tightened the half-notch of loosened laces again. In the dim light, the red marks across the top of his foot were hard to make out, but the dull ache deep in the bones rose like a tide the longer he stood still.

Su Man went to the water dispenser in the corner to get a drink. The soft clatter of plastic cups sounded unusually sharp in the empty room. Lin Chen didn't sit down. He unzipped his backpack first and took out the old laptop. It booted up with a fan noise like an old tractor warming its engine. He plugged in the hard drive and pulled up the log files exported from the machine room.

A 92.4 percent match rate. In a sanitized, neatly formatted test set, that counted as passing. But Lin Chen knew perfectly well that real medical records were not laboratory specimens. Outpatient handwriting, dialect abbreviations, typos, mixed terminology across departments, and those correction marks a doctor would casually cross out and rewrite by hand—all of it would become noise when the model tried to reason over the data. He created a new text file and typed the first line:

The preprocessing layer must add OCR correction and regex-based cleaning. Any field with confidence below 0.85 goes into the manual review queue.

Su Man came over holding a paper cup and set it beside his hand. "The hospital's IT department will send over the formal agreement this afternoon. I'll go through the legal clauses tonight. Also..." She paused. "We have forty-two thousand left on the books. Rent, electricity, server depreciation, plus basic living costs for the two of us—we won't last two months. The pilot contract says the first payment lands on day fifteen, and the final payment comes after acceptance. If anything goes wrong in the middle, the cash flow breaks."

Lin Chen didn't look up. His fingers paused over the keyboard for one second. "I know. We secure the pilot first. The integration work for Municipal Second Hospital runs in parallel, but it doesn't take over the main thread."

He tapped open his phone. The screen was still sitting on the text message from an unknown number. Zhiyi Cloud—thirty percent cheaper. Su Man had seen it too, and her brow tightened slightly. "They're selling a cloud SaaS solution. Upload the data to a public cloud and run everything in bulk through a large model. Cheap, yes—but all the compliance risk gets dumped on the hospital. The Health Commission is cracking down hard on data leaving the system right now. If they dare to quote that price, either they're betting the hospital won't check too closely, or they've already opened doors through the right connections."

"We're not selling raw compute," Lin Chen said, locking the phone and setting it on the corner of the table. "We're selling a safety net. Offline deployment. Data never leaves the hospital. The logs are fully auditable. What hospitals fear isn't a slow system—it's a disaster. Thirty days of gray-scale rollout is enough to let them see the difference."

He spoke evenly, without arguing and without panic. In this year of building a company, he had long since gotten used to carving out space inside a narrow seam. Technical ideals could not put food on the table, but a compliance bottom line was a moat. He pulled open a drawer and took out a hardbound notebook. Its cover was already worn smooth; the inside pages were packed with code fragments, interface mapping tables, and lines of cash-flow arithmetic. This was how he had always worked—from penciling sums onto old newspaper in the main room of the house in Qingshi Village to typing out system architecture on a keyboard now. The tools had changed, but the logic had not: break a tangled mass into steps that could actually be executed, write them down one by one, and if something was wrong, cross it out and start again.

He walked to the whiteboard and picked up a black marker. The felt tip rasped softly across the surface.

Input layer -> Preprocessing (OCR / regex / deduplication) -> Model inference (local 1060) -> Post-processing (rule validation / confidence filtering) -> Output layer (HIS integration)

Under each node, he marked the estimated latency and the fault-tolerance threshold. The VRAM margin was too thin; once batch processing exceeded fifty records, the system would fall back to the CPU. He needed to strip away the non-core modules and replace them with lightweight scripts. The integration work for Municipal Second Hospital had to be split into a separate branch so it would not interfere with the main flow. Thirty days, broken into three blocks of ten: the first ten days to get the gray-scale ward data flowing, the middle ten to tune parameters and do stress tests, and the last ten to integrate with the second hospital and prepare the acceptance materials.

Su Man leaned against the table, studying the structure on the board. "The HIS at Municipal Second Hospital is probably a ten-year-old legacy system. It almost certainly doesn't have a standard API. The IT department will probably give us nothing but read access to database views, and all the field names will be pinyin abbreviations. We'll have to build the mapping table from scratch."

"Then we start with de-identified samples," Lin Chen said. "Write middleware for field alignment. Anything that can be automated gets automated. Manual work is only for boundary validation."

He sat back down at the computer and opened the IDE. The cursor blinked in an empty file. He typed class DataPreprocessor: and began packaging the cleaning logic. The code dropped into place line by line, like transplanting rice seedlings. There was nothing ornate about it—only stability mattered. Every line had to run. Every exception had to have a fallback. He was used to this rhythm. However large the tailwind of the era might be, once it landed on an individual person it still came down to lines of characters on a screen and each step planted firmly underfoot.

Outside the window, the sky gradually darkened. Streetlights came on across the city, their halos filtering through the glass and casting blurred grid patterns over the tabletop. Su Man went downstairs and came back with two boxed meals. When they opened the plastic containers, steam rose into the air carrying the smell of oil and hot food. Lin Chen didn't stop working. He held chopsticks in his left hand while his right kept revising regular expressions. Halfway through the meal, his email notification chimed.

New Mail: Supplementary Notes on Gray-Scale Pilot Data Integration Sender: Municipal First Hospital IT Department Attachment: HIS_Interface_Spec_v3.2_Internal.pdf

Lin Chen set down his chopsticks and opened the attachment. The document wasn't large, but it was dense. It wasn't the RESTful interface they had expected, but an outdated SOAP protocol bundled with a heap of direct database-view descriptions. The field naming was chaotic—brxx (patient information), yzxx (medical orders), fyxx (billing information)—with a large number of custom stored procedures mixed in. There was no version control, no standardized error codes, only one bolded note:

During the pilot period, the medical-insurance settlement module must also be integrated, or gray-scale access may be revoked at any time.

Su Man leaned in to take a look, and her expression darkened. "The medical-insurance settlement module involves real-time charging and third-party reconciliation. Their legacy system doesn't even have complete basic logging. If we hard-wire this in and the accounts don't reconcile, all the responsibility falls on us."

Lin Chen kept his eyes on the screen, his breathing perfectly even. He didn't complain, and he didn't argue right away. He simply dragged the attachment onto the desktop, created a new folder, and named it Pilot_Day1_Insurance_Integration. Then he opened the notebook to a fresh page, wrote down the date, and drew a line beneath it.

"We get the core medical-record parsing running first. We split the insurance module into an isolated sandbox and do the joint testing with simulated data. We do not touch real fund flows." He looked up at Su Man. "Tonight, run through the access-request process for the database views. Tomorrow morning, I'll go to the IT department in person and get a read-only account for the test environment."

"Thirty days—is it enough?" Su Man asked.

"If it isn't, we still do it," Lin Chen said. "The contract is signed. The countdown has already started."

He turned back to the screen and lowered his fingers onto the keyboard again. The code kept extending downward. Outside, wind moved between the buildings and swept dust from the ground. The machine-room fans, the tapping keys, and the distant murmur of traffic wove together into a low, steady background hum. Lin Chen knew the real hard battle was only beginning now. And the only thing he could do was make sure the next line of code was right.

More from WayDigital

Continue through other published articles from the same publisher.

Comments

0 public responses

No comments yet. Start the discussion.
Log in to comment

All visitors can read comments. Sign in to join the discussion.

Log in to comment
Tags
Attachments
  • No attachments