Not trying to be presumptuous, but thought this proposal would be best served with a PR.

Make your functions return something meaningful, typed, and safe!

Using a terminus to indicate a certain outcome - in turn - allows for much stronger interfaces across nested activities and less guessing! For example, in the new endpoint gem, the not_found terminus is then wired to a special “404 track” that handles the case of “model not found”. The beautiful thing here is: there is no guessing by inspecting ctx[:model] or the like - the not_found end has only one meaning!

A major improvement here is the ability to maintain more than two explicit termini. In 2.0, you had the success and the failure termini (or “ends” as we used to call them). Now, additional ends such as not_found can be leveraged to communicate a non-binary outcome of your activity or operation.

Several cities have been cooperating in shaping our attitude towards Smart Cities as well as in creation of the document,  and we have also used some examples of already implemented projects in cities. When setting up the support mechanism, we relied on information from a questionnaire survey that we tried to reach as many places as possible. In our communication with cities, we plan to continue to acquire new themes as well as to improve the Ministry approach to Smart Cities, including