We'll probably need more use-cases to get a feel for the right way to separate it. At the moment I would say if the model is fundamentally different, it probably has a completely different type name. Whereas if it's kinda-the-same-but-has-a-couple-more-properties, we can likely just have one model object and phrase it / make fields optional appropriately.