okay... sounds like this might be a way to implement user personas, then? like the caveat effectively can act as a marker of whether a particular user is actually a persona or not, and it would allow checks and lookups to be filtered on that? (in the context of a previous conversation about personas in the cloud IAMish model where you can't just have personas be a separate object type for implementation reasons)