Ark MVP 1.0 stabilizes the presentation boundary without owning application state
The core and Flutter packages fix contracts for ModelBinding, Presenter, ViewState, ViewEffect, sessions, MvpView, and lifecycle-safe hosting.
Presentation does not need to own business state
ark_mvp and ark_mvp_flutter reached 1.0.0. The core package defines a framework-independent ModelBinding, Presenter lifecycle, ViewState adaptation, local invalidation, and non-replay ViewEffect delivery. The Flutter adapter hosts these contracts through MvpView, typed model providers, context access limited to the active build, and explicit runtime error routing.
The stable line deliberately stops before application state management. A model can read from one UseCase, several managers, or another typed source owned by the application. UseCase Forge is one possible composition, not a runtime dependency of either MVP package. This keeps presentation state, operation results, and one-time effects from collapsing into one replayed stream.
Both packages are available on pub.dev, with lifecycle guidance and examples in GitLab.