Fable
Cloud canals are no longer opened only by craftsmen
The mountain city moved its canals to a reservoir in the cloud. Craftsmen opened as many gates as they needed water, finance received only one bill at month-end, and the city lord cared only about whether the fields were watered.
In the spring plowing peak season, the canal ran all day. The engineering team said this was growth, finance said the budget had exploded, and farmers said some fields were still dry. All three sides argued their own case.
The city lord first ordered all gates halved. The bill did get smaller, but the high-value medicinal fields lacked water, while ordinary grassland was still being irrigated, and the money saved was quickly swallowed by reduced output.
The engineering team also promised to save on its own. But with each canal's ownership unclear, no one wanted to close a gate that might be useful, and the old experimental fields kept consuming water.
Later they set up a water council: engineering marked clearly whom each canal served, finance gave budgets and forecasts, and business explained which field had the highest output. Once a week they reviewed water use, output and waste.
The water affairs meeting did not pursue only the lowest cost. The medicinal fields could receive water when dry, but they had to know why; if abandoned fields were still consuming water, an alert would trigger automatically; shared canals were allocated according to actual use. Finance also began participating in design rather than settling accounts at the end of the month. Before the new canal broke ground, cost attribution and expansion limits were estimated, while the business side explained whether revenue could cover it. Water flow changed from an expense item into an operating variable.
The craftsmen received self-service meters and no longer had to wait until the end of the month to learn they had overspent. Finance was no longer only able to call for a stop, but could point out which types of work needed optimization or repricing. The water affairs association also changed rewards and penalties. The engineering team no longer won awards for using less water, but for using water more steadily for the same output, closing gates promptly on abandoned fields, and giving warnings before medicinal fields lacked water.
A quarter later, the water in the mountain city had not decreased, but a lot less was wasted. The most expensive water flowed to the fields most worth it, and ordinary fields also had stable quotas. The city lord understood that cost governance is not finance blocking engineering, but engineering, finance, and the business jointly managing the value of every drop of resources. Later, the steward wrote this experience into the daily rules: first look at the scenario, then look at the boundaries, and finally look at who can take over when it fails. Only when all of these are clear will a beautiful demo become deliverable work.