cqrs-es

I would like to review the docs and explain also de concepts behind some decisions.
Things needed to explain:

• DDD objectives and reasons why.
• Core concepts like
  • bounded context
  • anti corruption layer
  • domain
  • value objects VS entities
  • aggregates
  • aggregate root
  • layered architecture and each one responsibility
  • reasons for the command and query bus
  • the even

Improve the documentation of entities and read models so the reader can better understand what can be done with each one. For example, you can’t search on entities, you have to project them to the read models to perform a search.
We need to make clear the read model concept and how the joinkeys work. In Booster, you need to know which are the keys related to the entity that was updated to trigger

I hate manual tagging because, as everything tasked to a human being, the human factor brings inherent error.

Since we're all ✨ software engineers here ✨ we can automate the tagging process when merging on main -- maybe after the tests have passed?

NOTE: for each feature, a minor release should be used, and fix or minor branch, a patch release should be used instead.