Small input from user perspective. In my experience I had quite a lot of cases where I needed to merge accounts (of course I've done it manually).
One of things that often pop-ups and I don't see it covered in current proposal document is handling different permissions for the same object that user has relationship with.
Real-life example: Joe the User with account A is simple member (student) of group/community XYZ, same Joe the User with account B is administrator (professor) of the same group/community XYZ.
How system would handle such case? I guess, it should stick to relationship wich has higher permission lever (in exampe case that would be administrator). Would that fit to all situations?
