It doesn’t seem to be a widely recognized pattern, so it's probably a custom blend of MVVM and MVP. Think of it like using MVVM’s ViewModel for state and data-binding, while also having a Presenter (like in MVP) to handle user interactions, navigation, or coordination logic. The View connects with the ViewModel for state, and the Presenter takes care of the flow and event handling. This kind of setup helps keep your ViewModels clean and easier to test. I’d suggest checking how the View, ViewModel, and Presenter are wired up in your codebase, it’ll help clarify things. Also, maybe ask your teammates if there’s any internal architecture diagram, they might already have one shared.