The proxy architecture is an abstraction for instantiating various vtk.js pipelines. Think of them as high-level wrappers. For example, the ViewProxy instantiates the Renderer, RenderWindow, and the Interactor, while the SliceRepresentationProxy instantiates the ImageSlice + ImageMapper + ColorTransferFunction pipeline for viewing slices.
The central portion of the proxy architecture is the vtkProxyManager, along with the proxy config object. The config object defines the available Sources (producers of data objects), Representations (how to display input data), and Views (e.g. 2D or 3D views). The vtkProxyManager uses this config to construct these proxy objects whenever you request them.
There really should be some better documentation on the proxies. I can see if I have time to add some. In the meantime, check out the VtkThreeView.vue file in the VolView project. I’d suggest to start with following the usage of the viewProxy variable.