Fable
A pharmacy that cannot find its old formula cannot cure new illnesses
The herbal medicine shop on Qingshi Street had a formula book. The shopkeeper changed a few ingredients every day based on patient feedback, and the apprentice would also add a few reminders in the margins. In the small shop, everyone remembered what had been changed yesterday.
After the pharmacy connected the automatic herb-picking puppet, the formula book became prompts, that set of machines, tool descriptions, the contraindication table and customer tags. There were more changes, and it was faster too.
One day the puppet suddenly began prescribing different doses for similar patients. The proprietor asked who had changed the formula, but the apprentices only remembered that someone had optimized the summary, someone had swapped the herb table, and someone else had adjusted the order of contraindications.
Naive patching means copying the current recipe and naming it "latest final version." Two days later, "latest final version 2," "temporary usable version," and "do not delete version" appear. No one knows which one is actually live.
The new medical case specialist put everything that could affect dispensing behavior into the version cabinet: formula text, herb tables, puppet models, tool permissions, test cases and release notes. Every change had an author, time, reason and diff.
They also put version numbers on the production medicine cabinets. If a patient has an abnormal reaction, they can review the formula combination used at the time; if a new version has problems, they can roll back to the previous verified version.
The version cabinet serves not only rollback but also learning. Which change reduced misdiagnosis, which change increased side effects, and which type of customer was affected can all be traced along the version history.
The pharmacy later dared to try new formulas more frequently, because each attempt no longer erased the past. Changes had a trajectory, and mistakes had a way back. The shopkeeper understood that version control is not about naming files, but about making every change in system behavior traceable, comparable, and recoverable. Later, an even more troublesome task arrived. On the surface it looked like an old problem magnified, but in fact it forced out all the gaps hidden in the process: who takes over first, who can make changes, and how to return to the previous step after an error. Places that used to get by on familiarity and tacit understanding now all had to be made clear. The person in charge did not urge everyone to be more careful again, but walked the site once more. He had people record every handover, every failure, and every remedy, which places were merely slow, which places would harm the results, and which places would be hard to recover once wrong.