Fable
The city gate is not the castle, but it determines who can enter the workshop
In the mountain city there were several precision workshops that could engrave seals, refine medicine, and repair clocks. In earlier years, acquaintances would push the door open directly, give their name, and the master would take the job.
After the workshop became famous, out-of-town caravans, city shops, and temporary laborers all came to request processing. Before the master even started work, the doorway was crowded with questions: who has permission, which master should take it, and which version of the craft should be used.
The city lord first posted instructions on the door of each workshop. The instructions were written very clearly, yet guests still went to the wrong doors, and old customers still misused processes that had already been abandoned. One urgent order was sent to the old workshop and ruined by the old method. During the retrospective, everyone found that the workshop itself was not broken; the problem was that the entrance had no unified management of requests, identities, versions, and rate limiting.
So the city lord built a main gate. All requests first arrived at the gate, where tokens were verified, quotas checked, workshops selected, versions marked, and then the work was handed to the right master.
The city gate also recorded every entry and exit. Which caravan made the most requests, which craft had a high failure rate, which version broke right after release—all could be traced. When a new workshop went live, clients were no longer required to change a pile of routes. The gate could first let a small number of requests try it out, then gradually scale up once stable.
Later the city had multiple machines and multiple suppliers, but the city gate remained the fixed entry point for application calls. Workshops could be swapped, but the entry contract could not be shaken at will. So the city lord built a main gate pavilion. Visitors no longer barged directly into workshops; instead they declared their identity, purpose, urgency and desired craft at the pavilion, and the pavilion passed the work to the right master.
The gatehouse also did three things: it blocked people without credentials, recorded every entry and exit, and reminded people to take a different route when old techniques were involved. The master could finally focus on his work instead of arguing at the gate all day. This small incident made everyone stop and review. They didn't rush to adopt a louder slogan; instead, they wrote down one by one the entry points that had gone wrong, the rules that had been misunderstood, and the boundaries that needed to be preserved.
Some caravans resented the extra gate. But after one wrong process nearly ruined an entire batch of medicine, everyone admitted: the gatehouse itself makes nothing, yet it determines whether a request can be delivered safely inside. The city lord understood that machine services need a clear endpoint. It is not the machine itself, but it carries the boundary responsibility of letting applications reliably call the machine.