The two versions of the contract agreed until the word acceptance.
In one column, the English clause said the pilot would be considered technically accepted after a witnessed demonstration under agreed conditions. The companion text used in the local review pack described completion of the contracted service more broadly, without repeating the conditions.
Arjun’s manager noticed the difference when a procurement officer asked whether payment would become due after the demonstration or after the system had operated reliably through a production cycle.
Yanchuan had read the English draft. He had not reviewed the other language and did not pretend to be qualified to do so.
“Which version controls?” he asked.
The lawyer pointed to a clause saying both versions were intended to have equal authority. That made the mismatch more important, not less.
They commissioned a professional legal and technical review with the people authorized to interpret the local language. The engineers supplied definitions of demonstrated function, permitted conditions, operational handover and service completion. The legal team made the obligations consistent across both columns.
It took three sessions.
Guo’s representative complained that the negotiation was holding up a small contract. Arjun replied that the contract could remain small only if everyone understood the same boundary.
The source of the discrepancy was ordinary. One translator had used a commercial term usually associated with delivering completed equipment. The English engineer had been describing a narrower trial. Neither had asked what would happen if the pilot demonstrated a warning but failed to support the factory’s daily maintenance process after installation.
The revised contract separated three milestones: demonstration under witnessed conditions, transfer of documentation and training, and acceptance of the limited ongoing service. Payment for each milestone followed the evidence needed to establish it.
Leela asked that the maintenance team be allowed to decline a handover until the procedures could be carried out by the people expected to use them. The contract added a named sign-off from the factory’s authorized technical representative. It did not make every employee a party to the agreement.
Yanchuan remembered the signature on his brother’s acceptance package. A mark confirming attendance had been made to look like approval of performance. Here the parties were constructing a document that would not ask a signature to perform two jobs at once.
He told Chen the parallel. Chen reminded him to keep the case and the commercial project separate even when one had taught him what to notice in the other.
A week later a minor disagreement arose over the location of data. The draft used a familiar phrase about secure storage. Arjun interpreted it as storage under the factory’s control. Guo’s analyst assumed it meant a cloud service accessible from Shenzhen.
“Secure isn’t a geography,” Arjun said.
They wrote the storage and access arrangements explicitly. The factory retained its production data locally; remote engineers could receive approved summaries or limited samples through agreed procedures. Any broader transfer required additional review.
Ning welcomed the change. It meant the model’s operating plan had to account for intermittent connectivity instead of assuming that every sensor could be streamed across borders.
At home An had a dispute with a supplier over a different kind of language. A delivery note described goods as received, while the warehouse had signed only for the number of boxes. When one item was missing, the supplier argued the signature closed the order.
She showed Yanchuan the form.
“What did the warehouse actually check?” he asked.
“Boxes.”
“Then say boxes.”
“I did. Three times.”
They drafted a short request for the packing list and the contents inspection record, without accusing anyone of theft. The supplier eventually located the error: one item had been left off the dispatch batch. The shipment was corrected.
“Your brother would have liked that,” An said.
Yanchuan looked at the screen. The sentence had arrived without ceremony, and he let it stay.
The bilingual pilot agreement was signed after both versions had been checked. Its acceptance definitions were aligned, its exclusions visible and its data rules capable of being followed by the actual people involved.
At the signing Arjun said he could now explain the contract to his maintenance team without translating its ambition into a different promise.
Guo said the revised version was longer than the term sheet.
“Yes,” Yanchuan replied. “The term sheet was cheaper to misunderstand.”
Nobody laughed immediately. Then Arjun did.
For the first time, Yanchuan felt that the project’s paperwork had become as much an engineering product as the classifier itself. The agreement told people what would be demonstrated, who could question the result and what completion would actually mean.
Arjun asked for two signed copies, one for the purchasing office and one for the maintenance team. Neither version would be filed away as merely a translation.