Fable
The same kind of latch was installed at the entrance of every warehouse
The dispatch building in the port city wanted to connect to the city's warehouses, accounting office, calendar, work orders, and email. Each place had its own door, its own lock, and its own code word.
At first, engineers hand-made one key for each system. Connecting one warehouse was quick; after connecting ten systems, the keychain was so heavy no one dared touch it.
The trouble started with maintenance. The accounting office changed the door bolt, email changed the secret code, and the warehouse added a permission stamp. The dispatch hall could get in yesterday, but today it was locked out.
Someone proposed moving all systems into the same building. It sounds tidy, but every department has legacy processes, audit requirements, and vendor constraints, so it cannot be moved.
A bridge builder switched to building connectors. Each connector handles only one thing: understanding the gateway of an external system, exposing a stable entry point to the dispatch tower, and translating identity, permissions, parameters and errors clearly.
The dispatch tower does not need to know how each warehouse arranges its goods internally; it only needs to know what the connector can retrieve, what it can modify, who must authorize it, and what it returns on failure.
Connectors are not universal channels either. High-risk actions require approval, sensitive fields must be masked, and rate limits and access traces must follow every access.
Later, when new systems were added, engineers no longer built keys from scratch but connected them through the same connection pattern. Changes to old systems could also be absorbed within the connector boundary. The city lord understood that the value of connectors is not to make all systems the same, but to give the office assistant a reliable, governable interface. Later, an even trickier job arrived. On the surface it looked like just an amplified old problem, but in fact it forced out all the gaps hidden in the process: who takes over first, who can make changes, how to return to the previous step when something goes wrong. Places that used to get by on acquaintances' tacit understanding now all had to be made clear. The person in charge did not urge everyone to be more careful again; instead, he 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. After the new rules were rolled out, the first few days were not smooth. Some complained about an extra check; some felt their old experience was being insulted. But when the next anomaly appeared, for the first time everyone could follow the traces to find where the problem occurred, instead of gathering around the result and guessing at one another.