01
Model
An immutable snapshot of everything the feature currently needs: business state and allowed operations without raw infrastructure objects.
ARKTELOS / PRODUCTS / ARK MVP
Model becomes ViewState while View stays a view.
Ark MVP establishes an explicit boundary between business state and UI: Model captures a complete feature snapshot, Presenter adapts it for the screen, and View renders ready values while forwarding user intent.
01 / MODEL
One directional flow keeps every role distinct.
Application composition builds a ModelBinding over business objects it already owns. Presenter receives Model, derives ViewState, and publishes one-time ViewEffects. View never sees Model, a UseCase, a Repository, or a service.
02 / BOUNDARIES
The pattern defines boundaries without prescribing infrastructure.
02
Presenter
The adapter between Model and View: combines states, formats values, derives presentation policy, and exposes feature actions.
03
View
Receives only ViewState and public Presenter methods, renders prepared values, and handles ViewEffects in the current UI context.
03 / DOCUMENTATION
Follow the path from Model to a complete screen.
Begin with the full architecture, continue into the Flutter lifecycle, or study working examples for one UseCase, several UseCases, and an independent state manager.