Chapter 217: Gray Areas and Boundaries

At 2:45 in the afternoon, the light in the hospital room dimmed by a degree as the clouds lowered over the outlines of the office towers outside the window. Lin Chen raised the laptop stand to its highest setting so the screen sat level with his line of sight. Beneath his left ankle, he wedged a hardback copy of Computer Networks to ease the pressure on the vein. He unscrewed his thermos and took two sips of warm water, moistening his dry throat. In the lower right corner of the screen, the time ticked toward 14:58. He opened the meeting software, entered the password, and waited to be admitted.

At exactly 15:00, the screen lit up.

On the other side was the client’s CTO, surnamed Wu, around fifty years old, in a gray suit, with a plain bookshelf behind him. Chen Hao’s profile picture sat in the sidebar, muted. President Wu did not bother with small talk. He went straight to the point.

“Engineer Lin, I read the materials last night. The compliance red line is a non-negotiable order from the group. Any cloud-based plan is directly out. How do you intend to solve the compute redundancy problem for localized deployment? And for historical data migration, the business departments can give you no more than a four-hour downtime window.”

Lin Chen opened screen sharing and pulled up the architecture diagram.

“President Wu, we’ve abandoned full-scale migration and adopted a gray rollout plan based on in-place desensitization plus incremental synchronization. Core transaction tables will use direct connections; non-core log tables will go through asynchronous queues. The downtime window can be kept within three hours. Through precompiled scripts and field-level sampling, we can keep performance loss under eight percent. On the compute side, we’ll reuse the three idle physical servers from your company’s phase-two project and add an SSD cache layer, with no additional hardware procurement budget.”

President Wu frowned slightly and tapped two fingers on the desk.

“The idle machines are in the testing environment. If they run production data, who vouches for stability? And if the hashed fingerprint audit database doesn’t line up later during business traceability, how do we assign responsibility?”

“Running production on test machines is indeed a risk.” Lin Chen’s voice remained even; he did not evade the point. “That’s why we define the SLA boundaries clearly in the contract appendix. The desensitization layer is responsible only for compliant data output and format conversion. Business logic validation remains the responsibility of the client’s application layer. Hash fingerprints are generated before desensitization and stored independently; they do not participate in real-time computation. If discrepancies appear during traceability, we will provide the original data snapshots and conversion logs and cooperate in the investigation, but we will not bear consequential compensation for business interruption. That is the technical bottom line, and it is also a compliance requirement.”

There was more than ten seconds of silence on the screen. President Wu lifted his teacup, took a sip, and shifted his gaze back from somewhere off-camera.

“You people are very good at splitting up responsibility. But what group audit wants is results, not process. If there’s a data leak after launch, or a compliance notice is issued, how do you cover that?”

“The desensitization algorithm uses the domestic cryptographic standard SM4. The keys are hosted by your KMS system; we hold only the desensitization rules engine. The data does not leave its domain, and the keys never land locally. The physical path of leakage is cut off. As for compliance notices, after delivery we commit to providing a Level 2 MLPS evaluation report and stationing engineers on-site for two weeks to assist with rectification. All operations are logged, auditable, and reversible.”

Lin Chen paused, then added, “President Wu, technology solves probability problems. Contracts solve responsibility problems. We do not make promises that cannot be quantified, and we do not take on blame beyond our boundary of competence. The pilot period will be three months, accepted by milestone. If the targets are met, you pay the phase-two amount. If they are not, we roll back unconditionally and charge no additional fee.”

President Wu leaned back in his chair, his sharp gaze sweeping over every node in the architecture diagram. In the chat box, Chen Hao typed a line:

“Can the localized deployment timeline for Proposal C be compressed to six weeks?”

Lin Chen glanced at it and replied:

“Six weeks is possible, but the client must complete historical data field mapping confirmation by the end of week three. If mapping is delayed, the timeline extends accordingly. This is a prerequisite dependency and must be written into the contract.”

“All right.” President Wu finally spoke again, his tone somewhat softer. “Then shrink the pilot scope to two East China subsidiaries, with total data volume capped at twenty million records. First get the process running end to end, then we can talk about full deployment. Budget will be set at ninety percent of the original plan, and the payment schedule will be revised to 3-3-3-1. The final amount will be held until the security evaluation passes. If that works, I’ll have legal draft the contract.”

“A ten percent reduction is acceptable.” Lin Chen nodded. “But the payment schedule needs adjustment. The first payment of 30% must be made within five working days after contract signing, for server configuration and script packaging. A middle payment of 40% is due after gray rollout goes live. The remaining 30% can be held until after the evaluation, as you suggested. We don’t want the 1% warranty retention; replace it with settlement in full within thirty days after acceptance. Cash flow is the lifeblood of project execution. If it’s squeezed too tightly, delivery quality will suffer.”

President Wu looked at him for several seconds, then suddenly smiled—a faint one.

“You do keep your accounts very straight. Fine. We’ll go with your schedule. Legal will send the draft this afternoon. Review the terms. Get feedback back to us before close of business Friday.”

“Understood.” Lin Chen cut off screen sharing.

The meeting ended at 15:42. The moment the screen went dark, Lin Chen leaned back in his chair and let out a long breath. The muscles in his left calf suddenly tightened, the cramp climbing upward from his ankle. He clenched his back teeth and pressed his palm hard beneath his knee until the sharp pain slowly ebbed away. A fine sheen of sweat appeared on his forehead. He pulled out a tissue and wiped it off. His breathing was a little heavy, but he did not stand immediately. His heartbeat fell back into place inside his chest, slow and steady, like a server that had just come through a period of peak load—the fan still spinning, but the temperature already dropping.

Xiaoman turned over on the caregiver’s cot. The monitor kept up its regular beeping. Lin Chen stared at the crack in the ceiling and began replaying every line of the conversation in his head. President Wu had yielded, but the ninety-percent budget and the revised payment schedule still meant heavy front-loaded pressure. Six weeks was an ideal timeline. In actual execution, the client’s internal progress on data cleansing was usually sluggish. He had to lock the dependencies down in writing. Otherwise, the liability for delays would invert and land on him.

He opened his laptop and created a new Excel sheet.

Column headers: Expected Revenue, Expense Details, Buffer Margin, Risk Contingency.

As he entered the numbers, red and green interlaced across the screen. Reality had no miracles, only addition and subtraction. He checked each item one by one: server rental deposit, script packaging labor hours, on-site transportation and meals, third-party fees for the security evaluation. After subtracting the first payment, the shortfall still stood at 4,200 yuan. He could not touch his younger brother’s medication money. It could only come out of his own reserve funds.

At seven in the evening, a WeChat message from Chen Hao popped up:

“The contract draft has been sent to your email. President Wu got internal approval and the pilot has been greenlit. Check the liability exclusion clauses and the payment schedule. Also, legal added a line in Appendix 3: ‘If the compliance audit fails due to reasons attributable to Party B, Party A has the right to unilaterally terminate the contract and recover its prior investment.’ Take a look and see if you can accept it.”

Lin Chen opened the attachment. The wording was rigorous, but “reasons attributable to Party B” was too vaguely defined. If the client’s original data itself had missing fields or logical conflicts, and business errors appeared after desensitization, responsibility would be very easy to dispute. He picked up a pen and wrote a note beside the clause:

“Need to clarify that ‘reasons attributable to Party B’ refers only to defects in the desensitization algorithm or failure to follow prescribed operating standards. Failure caused by substandard quality in Party A’s original data, errors in field mapping, or changes in business logic does not fall under Party B’s responsibility. Recommend adding a prerequisite data quality confirmation letter, effective upon signature by both parties.”

He replied to Chen Hao:

“Framework acceptable, but Appendix 3 needs a data quality confirmation letter as a prerequisite condition. Otherwise the risk allocation is unequal. I’ll send you the revised version before ten tomorrow morning.”

After sending it, he closed the laptop and walked to the window. The city’s neon had already come on, and the traffic on the overpass stretched into bands of light. Wind forced its way through the crack in the window, carrying the dry cold of early winter. He touched his pocket. The cigarette pack was empty. He had quit three years ago, but when exhaustion became extreme, he still sometimes wanted one. He did not go downstairs.

Emotions needed an outlet. For adults, the outlet was spreadsheets, contract clauses, and tomorrow’s to-do list.

He returned to the table and opened his notebook of mistakes. The tip of the pen scratched softly across the page.

“Rule 217: Negotiation is not about winning. It is about finding the loss-cutting line both sides can accept. Technology can compromise; boundaries cannot retreat. Cash flow is the lifeline. Payment nodes must be front-loaded. Before gray testing starts, no blind spots can be left behind. Next steps: review the contract, confirm the external pharmacy channel, prepare the server procurement list.”

He closed the notebook.

His phone screen lit up again. Not Chen Hao this time, but an automatic push notification from the hospital billing system:

“Patient Lin Xing (Inpatient No.: 20190814): Prepayment for the next treatment cycle medication (Sodium Valproate Sustained-Release Tablets / Levetiracetam) must be completed before November 20. Medication will be suspended in case of arrears. Current amount due: RMB 2,840.00.”

Lin Chen stared at the string of numbers. The first payment would arrive no earlier than next Wednesday. There was a five-day gap in between. He opened his banking app and checked his wealth management account. One fixed-term deposit was maturing the next day. Withdrawing it early would mean losing the interest, but it would cover the medication fee. His finger hovered over the “Confirm Withdrawal” button for several seconds, then pressed it.

The interest was gone.

The medicine could not stop.

He put away his phone and raised his left foot again. The light in the hospital room had now fully faded, leaving only the green glow of the monitor casting a weak reflection on the wall. Tomorrow he had to visit server vendors, review contract terms, and contact the pharmacy. His schedule was packed, but every step was planted on solid ground.

At 9:15 that night, his email notification chimed. The revised contract from legal had arrived. Lin Chen checked it word by word. His gaze stopped at the “Deliverables List” in Appendix 5. There was a new line in small print:

“Party B must provide a third-party security testing report for the core module of the desensitization engine within seven working days after contract signing.”

He frowned slightly. Third-party testing normally took ten working days. A report in seven days would be impossible unless expedited, and the contract said nothing about who would bear the rush fee.

He picked up his phone and sent Chen Hao a message:

“There’s a conflict in the testing timeline in Appendix 5. The report can’t be issued within seven working days. Either change it to fifteen days, or Party A bears the rush fee. If this clause isn’t confirmed, the contract cannot be signed.”

Sent.

He leaned back in his chair and closed his eyes. The wind outside scraped lightly across the window glass. Xiaoman’s breathing remained even. The monitor’s beeping moved forward one tick at a time, like the second hand of a clock.

Tomorrow was still a long road.

But tonight, all he needed was four hours of sleep.