The good news is that the Data Vault is flexible and you have many ways to approach this. But - you have to choose.
John Giles discusses such a use case in his book, The Elephant in the Fridge.
What you have are two concepts: a super type and a sub type. The super type makes modelling sense in some business circumstances, the subtype makes sense in other circumstances.
So it depends on if they share the same business key? Same business key implies they are the same HUB. You can hold super or subtype data in separate satellites, assuming your source system refers to both concepts in separate tables.
If the concepts have different keys, you could model as two separate Hubs, with a same as link between them.
In a data vault model you have to balance between an abstract representation (as would happen with an enterprise architect who would use party, party role, etc.), and a more physical representation of concepts (supplier, customer, employee, etc.). In general, you should tend towards the more physical end for model readability and ease of extracting data.
2 Likes