Repository class for all projects. todo-mvvm-live-kotlin

I find "repository" thing very confusing. I mean most of the architecture patterns have an abbreviation of Model in the names, but its very hard to find an example with actual model layer. It appears to me everyone has his or her own understanding of model... even in google samples. What is model and what is repository?

Why the architecture components are not named RVVM, RVP, RVC? Why can't we rename repository to model?

How do we achieve separation of concerns for business logic and view presentation?
For example, todo-mvvm-live-kotlin has TasksViewModel which deals with the list of tasks. However, it also handles filtering and add task view(new task). I mean it is hard to grasp where business logic ends and view presentation logic starts. What is business logic in android development?

Begin with the todo-mvvm-live-kotlin sample and its TasksViewModel, which the issue identifies as handling task lists, filtering, and adding tasks. The issue needs a concrete documentation scope and an agreed definition of done before work can start, such as explaining the model, repository, business logic, and view-presentation boundaries.

Written by the indexing model from the issue text.