The certificate said the guard had been installed. The guard was lying against the workshop wall.
Arjun found the discrepancy during a planned inspection of the robot handling aid. The supplier’s completion packet contained photographs of a safety enclosure and a signed installation checklist. On the floor, the final section of the guard had not been fitted because it conflicted with a pipe support.
The supplier’s engineer explained that the certificate described the standard cell configuration. The local adaptation was still being completed.
“Then the certificate doesn’t describe this cell,” Ning said.
The engineer pointed out that most of the system had passed its checks. He was not lying about the missing steel. He had signed a standard document before recognizing that its claim reached beyond what had been installed.
Arjun stopped the demonstration. Nobody argued that the guard was only a small part. The point of the guard was to stand between people and a moving mechanism under conditions where the system might behave unexpectedly.
They measured the interference and asked the responsible engineer to design an approved modification. The new part would need its own inspection and documented acceptance. The supplier could not solve the mismatch by deleting the guard from the photograph.
Yanchuan read the certificate again. It had been generated from a template with the product model and delivery date filled in. The words physical installation complete remained unchanged.
“What does the signatory verify?” he asked.
The engineer said the document normally confirmed installation to specification. In this case he had intended to confirm that the components were delivered and assembled except for the remaining adaptation.
“Then write a delivery acknowledgment,” Arjun said. “Don’t call it full acceptance.”
The correction delayed payment of the installation milestone. It did not cancel the legitimate work already completed.
The supplier’s engineer called his manager before signing the revised document. He returned looking tired and asked that the completed assembly work be listed separately from the missing guard. Arjun agreed. The engineer had made an error, but a truthful record did not require pretending he had done nothing useful. The parties agreed to record delivered components, incomplete installation and the remaining conditions separately.
Guo heard about the delay on a call. His first question was whether the supplier had misrepresented the work intentionally.
“We haven’t established that,” Yanchuan said. “We have a document whose scope doesn’t match what we saw.”
“And the missing guard?”
“Was there. Not installed.”
Guo asked for a revised schedule and the cost of the approved adaptation. He did not instruct them to proceed without it.
After the meeting Leela brought Yanchuan to a shelf of parts waiting for inspection. Each had a label describing its current status: received, checked, awaiting fit, rejected or approved. The labels were plain. The process was not perfect, but a worker could tell what each item was allowed to be used for.
“Certificates are helpful,” she said. “Steel still has to be where the drawing says.”
Yanchuan remembered the first discussion with Mei about Yansheng’s signature. An attendance acknowledgment had become a performance approval when an image was attached to a different document. The signature had been real. The claim beneath it had changed.
He did not tell Arjun the whole family story. He told the engineering team why he insisted on a written boundary for every sign-off.
Mei asked whether the robot supplier had corrected its internal template. The local engineer said it had begun a review. The factory requested a copy of the revised procedure before accepting future installations.
A week later the approved guard modification arrived. The technicians fitted it during a scheduled stop, inspected the clearances and demonstrated the safety functions under the specified conditions. Only then did Arjun sign the physical acceptance record.
The report identified what had changed, who checked it, and what remained outside the trial’s scope. It did not certify the robot as suitable for every possible part or production condition.
On the train to the airport Yanchuan received a photograph from An. Their son had repaired the toy bus with its correct pin. The wheel turned freely, and the boy had drawn a certificate of his own: BUS WORKS, with a picture of a happy passenger.
“Did you test it?” Yanchuan asked by message.
The reply was a short video. The bus crossed the paper bridge, rolled down a ramp and stopped against a cushion.
“Now I have,” the boy wrote.
Yanchuan laughed aloud. A passenger across the aisle glanced at him, then returned to her book.
Back in Shenzhen he put the corrected installation record in the project’s archive. The certificate now matched the steel. It said what had been done and no more.
At the next review Guo praised the team’s ability to recover from a difficult acceptance. Yanchuan declined to call it a victory. The guard should have been fitted before the first certificate was issued.
“But you found the problem,” Guo said.
“Yes.”
“And you corrected the process.”
“We’ve started.”
He thought of his brother, still missing, and the technical record whose misuse had finally been acknowledged through formal review. A corrected document could not restore everything lost in the time it had been wrong.
Arjun asked the supplier to photograph the guard after installation and inspection, with the pipe support visible in the same frame. The record would have to describe this cell, not the standard one.
Outside the meeting room the factory’s ordinary work continued. Machines moved, operators watched, and maintenance staff kept checking the parts that had not yet earned the word complete.