Hey Harry! Thanks for reading! Here are a few thoughts. first, on large domains. Sometimes you'll need a system of systems. Sometimes objects will need types and/or inheritance. You have a PLACE object, but also recognizable variations of library, historic landmark, park, gov building, etc. Object Bases work for this. It all comes down to making the system as simple as possible but not too simple. A true art! And in my opinion, the larger and more complex the domain the MORE you need to get clear on objects and relationships. You don't want any fuzziness there — for your team or your users (and if it's fuzzy for you, it WILL be fuzzy for the team).

As far as "good services are verbs" — I disagree. this is a reaction to poorly labeled nouns. Nouns labeled properly from a user centered perspective will win over verbs every time. I wonder if "Building Permits" would do better than "get permission to build our renovate"... What can you draw a simple picture of? That the thing that can be more easily conceptualized. Also, we can strip away assumptions. What if someone doesn't want to get permission just yet? They just want to see a Building Permit to understand the level of effort? Or what if they want to check to see if the work a neighbor is doing has a permit?