The ward had a free bed on the computer and no free bed in the room.
Qiao was standing beside the nurses’ station when the transport coordinator called to ask why the transfer had not been completed. The scheduling system showed that a patient had been moved at 14:10, freeing a place for someone arriving from the emergency department.
The patient’s belongings were still in the cupboard. The patient herself was sitting in a chair beside the window, waiting for the receiving ward to confirm that its lift and transfer equipment were available.
“She hasn’t moved,” Qiao said.
“But she’s marked transferred.”
“Then the mark is wrong.”
The coordinator asked whether the patient could wait in the corridor while the new arrival came upstairs. Qiao looked at the patient, who was trying to make a phone call with a battery that had nearly run out.
“No,” she said. “Not as a way to make the computer true.”
The coordinator began to describe the waiting queue. Qiao interrupted only to give the patient’s actual location and the name of the nurse staying with her. She had no empty bed to offer; she could offer a verifiable state of the ward.
The charge nurse joined the conversation and arranged a different safe placement for the new arrival. It took calls, a person walking to another ward, and twenty minutes that the schedule had not allowed. Nobody had invented a bed. They had found a way to care for two people while the original transfer remained unfinished.
By evening Qiao was exhausted. She sent Yanchuan a photograph of the empty schedule grid, without names or hospital details.
“What’s wrong with this picture?” she asked.
He studied the row of cells marked available and unavailable.
“There’s no state for a transfer that started but hasn’t finished.”
“That’s one thing.”
He thought again.
“There’s no person responsible for deciding whether a bed is actually ready.”
“That’s two.”
“And the status changed when someone filled the form, not when the patient arrived.”
“Three. You can buy your sister dinner next time you’re here.”
He wanted to propose a state machine that would separate requested, accepted, in transit and physically completed. Then he remembered she had been on her feet all day.
“Did you eat?” he asked.
She had. Barely. The conversation returned to their father’s wrist, a neighbour’s repair request and whether Jianming was trying to conceal another appointment. Only after they had discussed those things did Qiao ask him to send the state names in ordinary language for a meeting with the ward administrator.
He did, with a warning that the staff would need to define the actual checkpoints and decide what information could safely be recorded. It was not his hospital to redesign from a family call.
At the factory a nearly identical error appeared in a maintenance schedule. A replacement component had been ordered and marked provided when the warehouse generated a dispatch label. The technician still had no part in hand. The pilot model had assumed that the repair would be complete before the evening shift and suggested a schedule that depended on it.
Gao declined the recommendation.
“Tell the warehouse a label is not a bearing,” he said.
Ning separated order accepted, dispatched, received and installed in the data feed. She warned the commercial manager that this would make the percentage of completed maintenance work look worse until old records were reviewed.
“It will look worse because it has been wrong,” he said.
Yanchuan could scarcely believe a manager had said the sentence before he did.
At the next family review, the missing-person case had no confirmed development. An was frustrated by a delayed response from the contractor about a document inventory. She asked the coordinator whether the requested record had been located, rather than whether the matter was being handled.
The reply came the following morning: the packet had been transferred to storage, but the specific attachment had not yet been identified in the permitted inventory. The distinction did not solve the case. It prevented someone from treating a successful handoff between offices as a successful search.
On a train to Guangzhou Yanchuan wrote three examples in his notebook: patient transfer, spare-part delivery, document request. Each had produced a completed field before the thing the field seemed to describe had happened.
He was tempted to call this one great fault of modern systems. He stopped. It was an old human error made faster and easier to copy by software.
Qiao met him at the station after her shift. He had brought dinner in containers that remained warm despite the journey. She ate while explaining that the ward manager had agreed to change the transfer form. They would not mark a bed available until the receiving team confirmed the physical move, except under a documented emergency process that named who took responsibility.
“Will it slow everything down?” he asked.
“Some things,” she said. “Maybe it will keep us from having to undo them.”
She looked at his notebook and asked whether he was collecting her mistakes for a new business idea.
“No.”
“Good. You can start by washing the containers.”
At An’s apartment their nephew had laid out his bridge in the living room. One side was marked open; the other, closed. He told Yanchuan he had made a signal so the cars would not drive onto a section that was still under repair.
“Who changes it to open?” Yanchuan asked.
“Me, when I finish.”
“Does the signal know when you finish?”
“No. That’s why I have to look.”
Yanchuan watched the boy lift a cardboard barrier after placing the final support. There was no shortcut between writing ready and making something ready.
The ward would not gain a spare bed merely because the software said one existed. Qiao kept the bed marked occupied until the receiving team confirmed that everything the patient needed was actually in the room. The software’s free-bed count changed only afterward.
That night, before sleep, Yanchuan sent Qiao a thank-you for the dinner. She replied that he had paid for it. He answered that he meant the lesson, and she sent back a single word: Good.