Choose Flutter ownership deliberately

The widget that can reach a UseCase is not necessarily the widget that owns its lifecycle. Choose the constructor from the ownership boundary, not from convenience.

Let the provider own a new instance

UseCaseProvider<ProfileUseCase>(
  create: (context) => ProfileUseCase(repository),
  child: const ProfileScreen(),
)

The provider creates the instance once and calls close() when it leaves the tree. Use onCloseError when the application needs explicit handling of asynchronous close failures.

Expose an externally owned instance

UseCaseProvider<ProfileUseCase>.value(
  value: profileUseCase,
  child: const ProfileScreen(),
)

The .value provider never closes the instance. The service, parent scope, or other lifecycle boundary that created it remains responsible.

Dispatch without subscribing to provider identity:

context.readUseCase<ProfileUseCase>().add(const RefreshProfile());

Lookup uses the exact UseCase type. Providing a concrete ProfileUseCase does not register unrelated base types.