Chapter 221: Blood Ties and Margins

The motion-sensor light in the corridor came on with the sound of footsteps, then went dark again the instant he pushed open the door. In the hospital room, there was only the steady ticking of the monitor. Xiaoman was asleep, breathing lightly and evenly. On the bedside table sat half a cup of warm water and an opened blister pack of fever medicine. Lin Chen set his bag on the chair as gently as possible. When his left foot touched the floor, a dull ache crawled up from his ankle along his calf. Out of habit, he shifted his center of gravity and put the weight on his right leg.

The nurses’ station was still lit. He walked over and handed over his ID card and the patient information card. After checking them, the night nurse pulled a report from the printer.

“The EEG results are back. The background rhythm is basically normal, and there are no typical epileptiform discharges. But during sleep there were a small number of scattered sharp waves. The doctor recommends continuing the current medication and coming back for another check in three months.”

Lin Chen took the report, his fingertips brushing over the page. Scattered sharp waves. That meant the neurons’ abnormal discharges had not been fully suppressed; the medication had only kept them below the threshold. He signed where indicated. The pen tip paused on the paper for a second before he finished with a clean stroke.

“Family member’s signature confirmed,” the nurse said. “The fever medicine is once every six hours. Keep an eye on the temperature. If it goes over 38.5, call us right away.”

“Understood.” Lin Chen nodded.

Back in the room, he pulled out the chair and sat down. He didn’t turn on the main light, only twisted on the small bedside lamp. Its dim yellow glow pooled over the table. He opened his notebook of corrected mistakes and flipped to a blank page. The pen came down:

“Rule 221: A medical report is the current state, not a verdict. Sharp waves are a hidden risk; medication is a buffer. Don’t be anxious about seizures that haven’t happened. Focus only on the doses already given.”

He closed the notebook and took his laptop from his bag. The screen lit up, washing the dark circles under his eyes in cold light. The time read 1:40 a.m. There were less than ten hours until the advance payment arrived, and less than thirty until the architecture draft for the data lineage tracing system had to be delivered.

He created a new Markdown document. Title: Data_Lineage_Architecture_V1.0.

The core logic itself was not complicated: plant probes at every node in the existing cleansing pipeline, capture input and output metadata, write it into an independent message queue, then have a parsing service assemble it into a directed acyclic graph. The real difficulty was performance overhead. With five hundred thousand records, if every single one logged every field in full, storage costs would rise exponentially and latency would blow past the 11 ms SLA red line.

He typed the first line of the architecture notes:

“Adopt a sampling + hash fingerprint strategy. Non-critical fields record only schema version and data volume level; core business fields retain full mapping. Use a lightweight graph database for metadata storage to avoid the Join overhead of relational databases.”

In the quiet hospital room, the sound of the keyboard was crisp. His left foot was beginning to stiffen; every forty minutes he got up, braced himself against the wall, took a couple of steps, and stretched his calf muscles. The pain was like a thin wire cinched around his nerves—not fatal, but a constant reminder of where his body’s limits lay. He could no longer force himself through all-nighters the way he had in college. Now his margin for error had to be calculated.

At three in the morning, the first draft of the architecture sketch was done. He opened a local sandbox, imported a simulated data stream, and started the probe service. Logs began scrolling down the terminal window.

INFO: Lineage probe initialized. Sampling rate: 10%. INFO: Metadata queue connected. Latency: 8ms. WARN: Graph write bottleneck detected. Node degree > 500.

A warning popped up. Node degree too high. That meant certain core fields were being referenced by dozens of downstream tasks, clogging the graph database’s write queue. Latency spiked instantly to 23 ms.

Lin Chen stared at the screen, fingers hovering over the keyboard. No irritation—only calm disassembly. The problem wasn’t the graph database. It was the probe’s trigger logic. Full capture had created a hotspot skew. He needed another layer of local cache to aggregate high-frequency fields before writing them in batches.

He opened a new Python script and rewrote the probe’s buffering logic. He introduced a ring buffer and set a threshold to trigger batch commits. The code wasn’t long, but every line had to account for memory leaks and concurrency safety. He wrote slowly, checking the granularity of the locks again and again. Outside, the sky was beginning to pale. Early winter mist clung to the glass, blurring the outlines of the buildings in the distance.

At 5:40 a.m., the modification was complete. He redeployed. Restarted.

The logs began to scroll again.

INFO: Batch write triggered. Queue size: 1000. INFO: Graph write success. Latency: 12ms. INFO: SLA check passed. Availability: 99.6%.

Latency was forced back down to 12 ms. Availability was up to standard. He leaned back in the chair and let out a long breath. A hollow acidic emptiness rose in his stomach. He fished out half a compressed biscuit and swallowed it with cold water.

His phone screen lit up. A bank message:

“RMB 45,000.00 has been deposited into your account ending in xxxx at 06:15. Current balance: RMB 45,035.30.”

The advance had arrived. Forty minutes earlier than expected.

Lin Chen did not feel happy right away. He opened his financial spreadsheet and checked it against the contract milestones. Forty-five thousand would cover server expansion, three months of cloud-service leasing, and Xiaoman’s next phase of medication. Just enough. No surplus. He took a screenshot and sent it to Chen Hao:

“Payment cleared. I’ll send you the architecture draft before ten this morning. The deployment environment will need the client to open the internal network whitelist in advance.”

Chen Hao replied almost instantly:

“Got it. Boss Wu’s side just finished the morning meeting. They’re pushing hard for real-time streaming internally, but the budget won’t get approved. They want to use the first-phase cleansing engine as the data foundation for now, then add real-time in phase two. Just get the lineage docs over first and stabilize the base.”

Lin Chen looked at the message. Budget not approved—that was normal. The logic of capital was always to validate with the minimum cost first, and only then decide whether to invest more. He replied:

“Understood. Phase one prioritizes stability; phase two leaves the interfaces open. The lineage docs will reserve extension fields for real-time streams.”

He closed the laptop and went to the washroom to splash cold water on his face. In the mirror, the man staring back had sunken eyes and stubble showing at his chin, but his gaze was clear. When he returned to the room, Xiaoman was already awake, quietly staring at the ceiling.

“Ge,” Xiaoman said softly.

“Mm.” Lin Chen walked over and touched his forehead. Normal temperature.

“You didn’t sleep last night,” Xiaoman said.

“I slept.” Lin Chen handed him the warm water. “Drink some. The doctor said your EEG is fine. Just keep taking the medicine.”

Xiaoman took the cup, drank a sip, then suddenly asked, “Ge, does your foot still hurt?”

Lin Chen paused. He lowered his eyes to his left foot. His ankle had swollen a little from sitting too long. “No. Old problem. I’m used to it.”

Xiaoman said nothing. He only pulled the blanket a little higher, up to his chin. The room fell quiet again. Lin Chen knew his little brother was watching him. There was no judgment in that gaze, only simple confirmation. Confirmation that his brother was still here. Confirmation that everything was still running.

At nine in the morning, Lin Chen packaged the architecture document and sent it through an encrypted channel to Boss Wu’s technical liaison. The message tone confirming successful delivery had barely sounded when his phone vibrated again.

This time it was neither Chen Hao nor the hospital. It was an unfamiliar local number.

He walked to the far end of the corridor and answered.

“Lin Chen?” The voice on the other end was a little hoarse, with obvious fatigue in it, but the speech was quick. “I’m Su Man. We met once at the provincial tech summit years ago. You gave a talk on fault tolerance in data cleansing.”

Lin Chen searched his memory for two seconds. Provincial capital. Several years ago. A woman in a gray shell jacket who had asked him three questions during the tea break, all about outlier handling. At the time he had just started taking Old Zhao’s outsourced work and was still grinding through low-level logic with brute-force scripts.

“I remember,” Lin Chen said.

“I’ve been looking at the underlying logic of the cleansing engine you just open-sourced,” Su Man said. “The architecture is clean, but your choice of graph database for lineage tracing is too heavy. If you want to move toward AI data preprocessing, this setup won’t sustain the throughput of large-model training datasets. I’ve got a project in a vertical annotation platform. I need a partner who understands low-level data flow. No empty promises—just profit sharing and equity. If you’re interested, meet me at three this afternoon at the café downstairs in Building C of the Tech Park.”

The call ended. The busy tone echoed down the corridor.

Lin Chen stood where he was, phone in hand. An early winter wind poured in through the window at the end of the hall, making his back go cold. AI data preprocessing. Vertical annotation platform. Partner.

The words dropped into him like stones into a deep well, setting off layered echoes. His current role was contractor—the one who took jobs, the one walking a tightrope between SLAs and cash flow. What the other side had thrown out was a fork in the road: from executor to decision-maker.

He lowered his eyes to the notebook of mistakes. The pen hovered above the page.

He did not write at once. Instead, he turned and walked back to the room, opened the laptop, and pulled up the sandbox monitoring dashboard. The latency curve was stable. Availability held steady at 99.6 percent. Everything was under control. But under control also meant the ceiling was already visible.

He turned to a new page and wrote:

“Rule 222: Technical debt can be repaid; windows of opportunity do not wait. Su Man’s invitation is a variable, not a certainty. At three this afternoon, bring two questions: one, how many months can the project’s cash flow sustain itself; two, what is the core barrier in data preprocessing. Bottom line: no gambling clauses, no gray-market data sources. If the talk falls through, keep being a contractor. There’s no shame in being a contractor. Going hungry is the shame.”

He closed the notebook. The time read 10:20. Less than five hours until three in the afternoon. He needed to elevate his left foot, ice it for twenty minutes, and change into a clean shirt.

His phone screen lit up again. A message from Boss Wu’s assistant:

“Mr. Lin, we’ve received the document. The technical team’s feedback is positive. But the client has made a last-minute request: complete a demo of the first batch data-lineage visualization dashboard by next Wednesday. We’ll need you to assign one engineer for on-site support.”

On-site. That meant he would have to leave the hospital, leave Xiaoman, for at least three straight days.

Lin Chen stared at the line of text. A sharp stab of pain shot through his left foot. He drew in a deep breath and typed on the keyboard:

“Received. On-site staffing is being arranged. We’ll be there Wednesday at 9:00 a.m. sharp.”

Sent.

He stood up and walked to the window. Below, the traffic had merged into a slowly moving river. He knew that from this point forward, not a single step could be taken on inertia alone. He would have to take the helm himself.

At the end of the corridor, the elevator gave a soft ding. The doors opened, then closed again.

Like the beat of some countdown.