Fable
The bell tower's echo line lets a command find its origin
The bell tower in the mountain city was responsible for telling time for the whole city. In early years there was only one bell, and the bell keeper struck it a few times upon hearing the lord's command. As long as people heard the bell, they knew whether to open the market or close the gates.
After the city grew larger, the bell began to drive the water gates, granaries, horse teams, pharmacies, and tax offices. A wrong bell time would make an entire street close early, and could also make the medicine cart miss the city gate.
The bell keeper first hung a board beside the bell and wrote down how many times it was struck today. The board could prove the bell had rung, but could not explain who ordered it, where the order came from, or why it became this rhythm.
One stormy night, the water gate closed early and the low street flooded. The water gate said it acted by the bell, the bell tower said it rang by the note, the messenger said the note came from the granary, and the granary said it was only asking about the weather. Every step was reasonable, yet strung together it was absurd.
The new secretary tied an echo line to every command. Who issued the command, who relayed it, which rule interpreted it, which actions it triggered, and where the action results returned—all were marked on the same line.
The next time the bell sounded abnormally, the secretary looked back along the line and found that it was not the bell tower ringing by mistake, but that a weather inquiry had been recognized by an old template as an emergency closure instruction. The problem was hidden in the interpretation step, not the execution step.
The mountain city thus changed how it fixed errors. In the past, when something went wrong, the last bell-ringer was punished; now the path was rebuilt first, to see at which station the signal had deformed, so responsibility and repair had a place to land. The clerk also required every line to be traceable both forward and backward. When something went wrong, one could trace from the consequence back to the source, and changing a rule would show which water gates, granaries, and horse teams would be affected. The lines did not exist only for assigning blame, but also for seeing the ripple effects before making changes. The mountain city also used the echo lines to train newcomers. The clerk gave them an old accident and had them work backward from the result to the original order, then forward from the order to the consequences. Being able to walk it both ways showed the records were complete enough; where it couldn't be walked was where the next loss of control might hide. The city lord later found that the more complete the records, the fewer the arguments. People could repair things along the line instead of arguing around the last executor.
The clock keeper said that being able to see a result does not mean being able to understand it. Traceability connects an event from input, judgment, and action through to consequence into a single line, and only then does the system deserve to be trusted.