Fable
The mill's waterway map found the upstream source of the bad flour
The river valley mill used to grind only one kind of wheat. Farmers brought sacks of grain, the mill produced flour, and the ledger recorded weight and price. No one needed to ask anything more.
Later, the mill took orders from the city's pastry shops, military camps, and medicinal food kitchens. The wheat came from different villages, and cleaning, blending, drying, grinding, and packaging were also assigned to different workshops.
The mill owner first had every bag of flour labeled with its production date. The date could tell customers when the flour was milled, but not which wheat it used, which water channels it passed through, or which batches it was mixed with.
After a batch of pastries turned bitter, three villages fell under suspicion, and all flour shipped the same day was recalled. The losses were heavy, yet still no one knew which waterway the problem had entered through.
The new steward drew a waterway map. The source, washing tank, mixing barrel, drying oven, millstone, packaging bag and customer order of every sack of wheat were all linked. Each mixing or splitting generated a new batch relationship.
When the strange smell appeared a second time, the manager traced it along the graph and found that only batches that had passed through Dryer No. 3 and been mixed with wheat from the west slope were affected. The recall scope shrank, and the real equipment problem was found. When the pastry shop later wanted to trace the source of a bag of flour, the mill could follow the graph from the customer order back to the wheat field, and from the faulty dryer down to all affected batches. Responsibility no longer relied on guesswork, and repairs were no longer one-size-fits-all.
The mill later posted the waterway map in the dispatch room. It wasn't for looks, but so that any sack of flour could explain where it came from, how it was handled, and where it finally went. The new manager also required that any temporary change leave a trace on the map. The night shift bypassing water trough No. 2, switching dryers on rainy days, a customer requesting small-bag packaging—none of it could rely on the master just remembering it.
The workshop owner finally understood that data flows, mixes, gets processed and gets distributed like wheat. Without a lineage graph, any conclusion used by an enterprise's automated agents may have no traceable upstream accountability. Later the manager wrote this lesson into the daily rules: first look at the scenario, then look at the boundaries, and finally look at who can take over when things fail. Only when all of these are clear does a beautiful demo become deliverable work.