@ctweney It was used mainly as an implementation stub. In the event that a new proxy was added to the merged model, you can start off with a very basic class and not worry about crashing the merged model feed since it's missing the implementation of `append!` I was initially seeing more as an interface than an abstract class, so that when other add proxy endpoints, they'll know which public methods to expose. I can go ahead and remove this if we feel that this is not necessary.