Jump to content

Chicken dilemma: Difference between revisions

m
Replace dead-end link to ICT with a link to Smith//IRV as both are in the category in question
(Boldly remove CD2 per talk page)
m (Replace dead-end link to ICT with a link to Smith//IRV as both are in the category in question)
Line 42:
# Some voting systems, such as approval voting, ignore the problem. Perhaps the assumption here is that it will be impossible to organize a defection without prompting a retaliation, and thus that both sides will prefer to cooperate. ("Mutual assured destruction"?)
# Some voting systems, such as [[Majority Choice Approval]], try to exploit the fact that each faction is not a single coordinated entity, but a group of individual voters. The idea is that if a small number of voters defect, they should be ignored; hopefully, in that situation, majority cooperation will be a stable strategy.
# Other voting systems, such as [[ICTSmith//IRV]], try to exploit the fact that in a real-world election, A and B are never perfectly balanced; one subfaction is always larger. In this case, a voting system can encourage the smaller group to cooperate by threatening to elect C (punishing both groups) if the smaller group defects. The chicken dilemma criterion is usually passed by this kind of voting system.
# [[Reciprocal Score Voting]] addresses the problem by explicitly rewarding reciprocal cooperation and punishing the defecting sides. Whichever subfaction defects receives no support from the other faction, even if it's larger. The only way to maximize the odds of winning is by cooperating as much as possible with similar factions.
 
1,221

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.