Many democracies vote for parties, not representatives, and many have no geographical subdivisions that are represented at the national level.
But I agree with your point about groupings on other dimensions. I call that demotmimata. The USA used it wisely during the land reform the military forced on Japan 1946-1949. I’m working on an essay about that.
If we want cultural representation, we can create a new branch of government, that allows people to identify as a particular culture, and then vote for members of that culture.
If we want religious representation, we can create a new branch of government, that allows people to identify as a particular religion, and then vote for members of that religion.
If we want racial representation, we can create a new branch of government, that allows people to identify as a particular race, and then vote for members of that race.
If we want language representation, we can create a new branch of government, that allows people to identify as speaking a particular language, and then vote for members who also claim to speak that language.
Again, the same rule we apply to software architecture should apply here. Whatever kind of representation we regard as important, we should approach the matter directly, and not try to achieve the effect accidentally, as the side effect of some other architectural decision.
Indeed, many of the problems we see in our political system are exactly because too many goals are being overloaded on too few institutions. If this was a legacy software app, and I was brought in as a consultant to clean it up, I would immediately suggest that a dramatic increase in both encapsulation and polymorphism was needed, and could only be achieved by introducing new branches of government.
But I agree with your point about groupings on other dimensions. I call that demotmimata. The USA used it wisely during the land reform the military forced on Japan 1946-1949. I’m working on an essay about that.
If we want cultural representation, we can create a new branch of government, that allows people to identify as a particular culture, and then vote for members of that culture.
If we want religious representation, we can create a new branch of government, that allows people to identify as a particular religion, and then vote for members of that religion.
If we want racial representation, we can create a new branch of government, that allows people to identify as a particular race, and then vote for members of that race.
If we want language representation, we can create a new branch of government, that allows people to identify as speaking a particular language, and then vote for members who also claim to speak that language.
Again, the same rule we apply to software architecture should apply here. Whatever kind of representation we regard as important, we should approach the matter directly, and not try to achieve the effect accidentally, as the side effect of some other architectural decision.
Indeed, many of the problems we see in our political system are exactly because too many goals are being overloaded on too few institutions. If this was a legacy software app, and I was brought in as a consultant to clean it up, I would immediately suggest that a dramatic increase in both encapsulation and polymorphism was needed, and could only be achieved by introducing new branches of government.