I interessted in the "usecases" and "how they interacts with the "context" at "clean architecture".
If I understand right, there will be two contexts.
First is the context of the domain-model with instances of the intelligent domain-entity-classes, which are includes all the buisness/domain-logic (e.g."Client")
Second is the context of the data-model (db,files,..) with instances of the stupid data-class without any logic (e.g. "ClientDto").
An example usecase: create a new client at a bank-software
The presenter/controller of the presentation-layer will call this "usecase", which is in the application-layer. But what will the usecase do or on which "context" will the usecase anything do. Writes the usecase the "new client" two both contextes, or only to the domain-model and these convert the "Client" to "ClientDto" and transfer it to the data-model? (Intuitively I would say the latter, but I also know that the domain model should not know the data interface.)
Editing after answer of @Michael Borgwardt:
Correct, the usecase itself do not active work at these context. The presenter creates a instance of a usecase and transfer it to somebody, who will do something because of this usecase. (so it's more a passive work, because the usecase-instance exist).
For my example.
- User push Button "New Client"
- View informed Presenter that "New Client" needed
- Presenter creates instance of usecase and will send this instance to somebody
The question is: how is "somebody"? "He" have to updated the two context, which I described. Or?