So, I've been trying to model some use cases that we want to solve with SpiceDB and there is one thing I came across. Considering the following schema:

definition user {}

definition blob {
    relation owner: user_archive | shared_document // | ... and so on

}

definition user_archive {
    relation owner: user
}

definition shared_document {
    relation editors: user
}

Is there a useful way to invert the definition of relationships in

blob

? I.e. the service handing out blobs does not really care if it is part of a user_archive or a shared_document and ideally the definition would not have to be changed.