Okay, so I'm trying to figure out how this can fit into an event sourced system. I figured we could stick authz concerns into an inline projection (just a fancy phrase for "subscriptions that prevent persisting events if they fail"). That way, if we can't reach spicedb, we don't write the event(s), and if we do reach spicedb but the db commit fails, then we can forget about the dirty write to spicedb since no one will be checking for those abandoned IDs anyway. That much is clear. What is unclear is how we're supposed to handle zookies. If we're storing exactly one zookie for the entire app (keeping the freshest ofc) in a repository, that's easy. However, if we have to store a zookie for each relationship or so, it's not clear how I would go about that.