Rico, I enjoyed this article very much (and applaud your courage in posting a serious article on April Fools Day).

I fully agree with the use of the domain-bounded context to describe software components. The most common reason for failure in application development is the failure of communication between the application domain experts and the developers who must translate the requirements and behaviors into working software.

However, I cannot agree with a shift of emphasis from nouns to verbs. It is the relationship between nouns and verbs that makes a bounded context useful. A bounded context defines the state of a "thing", the rules that govern that state, and the actions or events that can change that state.

The team I work on makes bounded contexts first class services that respond to messages from GUIs, other application components, and event queues. Some contexts represent only persistent entities and read from and write to databases. They are used by the other contexts.

https://dick-dowdell.medium.com/some-advice-for-developers-eb16e5f076a0

https://medium.com/nerd-for-tech/composable-services-ec1ced75a8dc#5858