Fable
A waterwheel without blueprints will break again every time it is repaired
In the valley there was a waterwheel, first built by an old craftsman with his own hands. It could drive the mill, irrigate the fields, and send water to the dyehouse. The old craftsman knew the temperament of every wooden axle, but rarely wrote it down.
The water wheel took on more and more work, and beside it were added hidden channels, diversion gates, and night alarm bells. The new apprentice could only follow the old craftsman's gestures; no one fully understood where the water came from, where it passed, or when it would stop.
After the first failure, the workshop owner had the apprentice write a repair note. The note was full of small tricks, but had no overall diagram, interfaces, limits, change records, or emergency steps. The next time something broke elsewhere, the note was almost useless.
A cold snap froze and cracked the hidden channel, and the old craftsman was not in the city. The apprentices argued around the waterwheel for half the night, and in the end closed the wrong gate; the mill was not saved, and the dye works also stopped.
When the old craftsman returned, he did not blame the apprentice. He drew the waterwheel in several layers: overall structure, the responsibility of each gate, normal waterways, abnormal waterways, maintenance cycles, and parts that must not be modified.
He also required every change to clearly state the reason, scope of impact, test results, and rollback method. Blueprints were no longer completion commemorations but part of keeping the waterwheel running. Documents were also assigned to different readers. Apprentices read daily maintenance, inspectors read safety boundaries, workshop owners read impact scope, and outside craftsmen read interfaces and restricted areas. Writing these clearly meant the waterwheel no longer lived only on one person's memory.
A few months later, the new apprentice could handle minor faults independently, and the outside inspector could understand how the waterwheel protected the downstream fields. The old craftsman's experience had finally left his head. Later the steward 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 it fails. Only when all of these are clear does a beautiful demo become deliverable work.
The master said that technical documentation is not written for the past; it is written for the next person who will maintain, review, take over and trust this system. Later the master also decreed that drawings must be updated together with the waterwheel. Changing a gate without changing the drawing is more dangerous than having no drawing at all; a new apprentice will operate according to the old drawing and turn a small change into a major accident.