Asha’s map had three colors of pencil marks and no legend.
Red lines traced equipment that failed to deliver its rated capacity under certain conditions. Blue circles marked places where spare parts could be stored. Green arrows showed routes that maintenance crews could use when the road near the river was flooded.
Yanchuan had asked for a system diagram. She handed him a map of the people who kept the system running.
“Where’s the legend?” he asked.
“In my notebook,” she said. “I didn’t think you’d be building software from a photograph.”
He apologized. She was right to keep the meaning with the people who had made the marks.
They were meeting at the workshop’s follow-up session, arranged by Amina. Asha described a district network with conventional lines, some local generation and customers whose dependence on reliable power was not proportional to the size of their bills. The official diagram contained electrical connections. Her map contained time, distance and the fact that a road could become impassable at the same moment a storm increased the chance of an equipment fault.
“Your model would call those separate uncertainties,” she said.
“Unless we tell it they’re connected.”
“Exactly. We don’t need an algorithm to learn that rain affects roads. We need the planning team to remember it when choosing a spare.”
Mutiso joined them with maintenance records from a permitted demonstration network. No confidential customer data would be exported. The engineers selected a hypothetical repair scenario and asked Yanchuan to calculate service restoration under three constraints: a replacement part at the central warehouse, one at a local depot and one that had not yet been procured.
The electrical calculation was the easy part. The repair time depended on access, people, tools and permission to work. His first estimate assumed the crew would reach the site by road in forty minutes. Asha crossed the route out during a flood scenario.
“Try again.”
He did. The result was worse, and more credible.
The workshop’s local team proposed a shared model they could maintain themselves. It would be small, with documented inputs, an offline view of the map and no automatic control of equipment. Its first purpose would be to make logistical constraints visible before a promise was made to a customer.
Guo heard about the idea when Yanchuan returned to Shenzhen. He wanted to know whether it could be commercialized.
“Only if the local team wants that,” Yanchuan said. “They own their operating knowledge and must decide what can be shared.”
“I’m not asking to take their map.”
“You are asking what revenue it can produce.”
“That’s what I do.”
They spoke longer about possible funding without reaching an agreement. Chen said any collaboration would require a separate contract with local engineering leadership and a clear rule about data ownership. Guo asked for a proposal under those conditions.
Yanchuan sent Asha an email describing the interest and asking whether she wanted to consider it. He did not send her annotated map to Guo.
Her reply came two days later. She would discuss a small paid study, but the first result had to help maintenance staff make a decision they currently struggled with. She did not want a demonstration built to impress visitors.
Ning read the message and smiled.
“I like her.”
“You haven’t met.”
“I like the requirement.”
Meanwhile the official inquiry into Yansheng remained open. Wanjiru had arranged a scheduled meeting while Yanchuan was in Kenya. It produced an update about the records reviewed and the leads still being checked, not a new confirmed location. Yanchuan listened, asked the two questions An had agreed on in advance, and returned to his workshop obligations without visiting the annex.
When he told An afterward, she said she was glad the meeting had been orderly. She did not pretend the absence of a breakthrough was a success.
Back in Shenzhen he printed Asha’s map request, not the map itself, and placed it beside the factory pilot’s data-governance agreement. The two projects would need different rules. One had a long history of controlled industrial measurements; the other began with practical notes held by local workers who had never promised to license them.
Yanchuan remembered the first time he had treated his brother’s spreadsheets as if they contained everything relevant. Mei had made him say extract rather than raw data. Asha was making him say map rather than model.
At the next engineering meeting, Ning suggested that the local team lead the definition of a successful pilot. It could be fewer unplanned trips for missing parts, more realistic restoration estimates, or a clear warning when a schedule could not be promised. Savings might follow. They should not be invented in advance.
Chen approved the approach.
That evening Yanchuan called his father. Jianming asked whether the new project meant more travel. Yanchuan said perhaps, but only with a defined purpose and a budget the family could understand.
“Good,” his father said. “Do the work in front of you.”
Then, after a pause, he asked whether there had been news of Yansheng.
“No.”
They spoke for a while without trying to change the answer.
Asha’s map remained in Kenya, where it could be corrected by someone who knew when a road washed out or a spare was moved. Yanchuan held only the part she had chosen to share.
When the next planning meeting began, he asked Asha to walk the team through her own version of the map. His copy remained closed.