Thanks Anne, that's very interesting and really great to hear about how other orgs are tackling these issues.
I wonder though if your solution actually solves the problem - the problem being that a role is not a person, and can't be held accountable for "people" things. But I might also not be understanding the role/soul distinction so well.
Also, as per Chris' point above ("the main issue...is that they impact the people, yet "a person" isn't a role and therefore can't object to any of this."), does that mean that everyone at Springest can come into the GCC meetings to propose changes to the Springeteer role?