SODA voting (Simple Optionally-Delegated Approval): Difference between revisions

→‎Sample Ballot: clean up (AWB)
imported>Homunq
(→‎Sample Ballot: clean up (AWB))
 
(37 intermediate revisions by 3 users not shown)
Line 7:
<table border='1px' width='80%'><tr><td>
'''Vote for as many candidates as you approve, or vote for one candidate to delegate your vote:'''<br>
&#9634; Adams (Prefers Churchill, then Bachelet, then Deakin)<br>
&#9634; Bachelet (Prefers Deakin and Churchill)<br>
&#9634; Churchill (Prefers Adams)<br>
&#9634; Deakin (No preferences declared)<br>
&#9634; ____(write-in)____<br>
&#9634; ____(write-in)____
 
'''If you only vote for one candidate, your vote is delegated to that candidate, unless you check the box below.''' A delegated vote means that, if your favorite candidate shows preferences above, he or she may use your vote to approve of one or more of the most-preferred of them. For instance, if he or she can not win, he or she might approve of some other "compromise" candidate(s) who can.<br>
▢ Do not delegate. Do not let the candidate I voted for add approvals to my vote.
 
 
'''If you only vote for one candidate, your vote is delegated to that candidate, unless you check the box below.''' A delegated vote means that if your favorite cannot win, they may use your vote to approve of a compromise who can, according to their preferences above.<br>
&#9634; Do not delegate. Do not let the candidate I voted for add approvals to my vote.<br><br>
''Note: If you vote for more than one candidate, or if you vote for a write-in or other candidate with no declared preferences, your vote is not delegated. In that case, no-one can add approvals to your vote, and it does not matter whether you check the box above.''
</td></tr></table>
 
=== Full, step-by-step rules ===
RulesSteps marked "''(optional)''" are suggested, but only the four stepssubsteps in '''bold''' (1a, 2b, 3b, and 3b.i) are necessary for the system to function. ItemsExplanations in ''italics'' explaingive the justificationpurpose behind each step. Terms<u>Underlined</u> terms are defined on the right.
{|
|-
|<big>'''1. Candidates publicly declare their rankings of the other candidates'''</big>
|-
|valign=top|
:a) '''Before the election, all candidates must strictly rank theall other official candidates in order of preference. Equal rankings are not allowed.''' ''These pre-announced preferences allow voters to make informed decisions in step 2; and prevent corrupt vote-selling in step 3, where candidates may only approve others in a way that is consistent with their preferences.''
|-
|valign=top|
:b) ''(optional)'' Candidates may <u>enforce any prior agreements</u> of mutual preferences by changing their own preferences in response to those of others*. ''This enforcement mechanism is designed to deter betrayals, so that it should almost never actually need to be used. Candidates, realizing that changing preferences at this point will only make them look untrustworthy, will prefer agree on mutual approvals beforehand.''
<br>
<big>2. Voters vote delegated plurality-style votes or non-delegated approval-style votes</big>
| width = 33% |
<small><u>'''Enforcing mutual approval agreements'''</u>: If A ranked B higher than B ranked A, then A may respond by lowering B's ranking. B may respond by raising A, and A may then respond by restoring B to the original ranking. If B raised A above C, then C may lower A, but A may not respond. Three rounds of response are all that are allowed. </small>
|-
|valign=top|
:a) ''(optional)'' Ballots list all candidates in order from candidates who submit the <u>most complete</u> rankings of other candidates, to those who submit the least. Where this is a tie, ordering is random. ''This is a slight incentive for candidates to submit a complete ranking in order to appear high on the ballot.''
<big>'''2. Voters vote delegated plurality-style votes or non-delegated approval-style votes'''</big>
|-
|valign=top|
:a) ''(optional)'' Ballots list all candidates in order from candidates who submit the most complete* rankings of other candidates, to those who submit the least. Where this is a tie, ordering is random. ''This is a slight incentive for candidates to submit a complete ranking in order to appear high on the ballot.''
|valign=top|
<small><u>'''Most complete'''</u>: Completeness of ranking is scored by how many possible pairs of other candidates contain two candidates at different levels.</small>
|-
|valign=top|
:b) '''Voters may approve one or more candidates, and also have the option to mark "Do not delegate". <u>Delegated votes*</u> and initial <u>total approvals*</u> are tallied and announced for each candidate.''' ''Announcing full tallies makes step 3 predictable and fair.''
<br>
<big>3. Candidates take turns to publicly use their delegated votes, in descending order of delegated votes.</big>
<br>
:a) ''(optional)'' There is a one-week period for candidates to analyze and negotiate based on these preliminary results. ''Actually, the optimal strategies for all candidates and the resulting winner will already be obvious. Usually, all candidates except this winner would concede as soon as preliminary results are announced. However, for the occasional candidate inclined to act irrationally in a way that matters - say, by not delegating to an ally, even though the alternative is to see an enemy elected - this interim period would give them a chance to rethink things and come into reason.''
|valign=top|
<small><u>'''Delegated votes'''</u>:The delegated votes for candidate X is the number of ballots that approve only X and do not mark "Do not delegate". X will get a chance to effectively add additional approvals to these votes; or, if X has less than 5% approval, then additional approvals will be added automatically, in order to attain a better result by X's predeclared preferences.
 
<u>'''Total approvals'''</u>:The total approvals for candidate X is initially the number of ballots that approve X, including X's delegated ballots. This number increases through the process as other candidates use their delegated ballots to approve X.</small>
|-
|valign=top|
:b) '''Each candidate, in descending order of number of delegated votes, may <u>use some or all of their delegated ballots</u> to approve zero or more other candidates, consistent with their predeclared preferences. That is, they may add a number up to their delegated vote tally to the other candidates' approval tallies, as long as they do not give more to a less-preferred candidate.''' ''If, considering the votes, a candidate can win, they will probably prefer not to approve other candidates. If there are two allied candidates who need to cooperate to win, the one with more approvals has first chance not to approve the other. That way, when it's the weaker candidate's turn, they will no longer have the possibility of winning, so the weaker will approve the stronger.''
<big>'''3. Candidates, in descending order of current approval totals, publicly use their delegated votes'''</big>
|-
|valign=top|
<small><u>'''Use their delegated ballots'''</u>: The process by which a candidate effectively adds approvals to the votes delegated to him or her. When, for example, candidate A uses their delegated ballots to approve of B and C, then B and C's approval totals are each increased by A's delegated vote total. When it is a candidate's turn, they may choose to approve of nobody else, for instance if they believe they will win; but this counts as using their delegated votes, and they will not be given another chance to change that decision. When all candidates have used their votes, the election is over.</small>
:a) ''(optional)'' There is a one-week period for candidates to analyze and negotiate based on these preliminary results. ''Actually, the optimal strategies for all candidates and the resulting winner will already be obvious. Usually, all candidates except this winner would concede as soon as preliminary results are announced. However, for the occasional candidate inclined to act irrationally in a way that matters - say, by not delegating to an ally, even though the alternative is to see an enemy elected - this interim period would give them a chance to rethink things and come into reason.''
|-
|valign=top|
::i. If the candidate using their delegated votes has more than 5% approval, '''they may choose which candidates approve on their delegated ballots, <u>consistent with preferences</u>.'''
:b) '''As long as no candidate has approvals equal to over 50% of voters, each candidate in turn must use some or all of their delegated ballots* to approve zero or more other candidates. At each step, the candidate with the highest current approval total who has not yet used their ballots does so.''' ''If, considering the votes, a candidate can win, they will probably prefer not to approve other candidates. If there are two allied candidates who need to cooperate to win, the one with more approvals has first chance not to approve the other. That way, when it's the weaker candidate's turn, they will no longer have the possibility of winning, so the weaker will approve the stronger.''
|valign=top|
<small>'''<u>Consistent with preferences</u>'': For example, candidate A may not approve B and not C unless A predeclared a preference for B over C.</small>
<small>'''Use their delegated ballots''': The process by which a candidate effectively adds approvals to the votes delegated to him or her. When, for example, candidate A uses their delegated ballots to approve of B and C, then B and C's approval totals are each increased by A's delegated vote total. When it is a candidate's turn, they may choose to approve of nobody else, for instance if they believe they will win; but this counts as using their delegated votes, and they will not be given another chance to change that decision. When all candidates have used their votes, the election is over.</small>
|-
|valign=top|
::iii. ''(optional)'' If the candidate using their delegated votes has more than 5% approval,approvals '''theyor may choose which candidates approve onless, their delegated ballots, consistentare withused preferences,'''to with<u>automatically equallyapprove</u> preferredtheir tiespreference ''(optionally)''between brokenthe by current approval totals*frontrunners. ''ThisAutomatic tie-breakingapprovals byrespect approvalpredeclared totalspreferences resolvesbut theprevent "chickenminor dilemma",candidates from having asdiscretionary explainedkingmaker belowpower.''
::iii. ''(optional)'' If the candidate is a write-in or got less than 1% direct approvals from voters, they may not use their delegated votes. However, any candidate may approve a write-in, regardless of the predeclared preferences. ''Write-ins do not have a chance to declare or figure in the pre-declared preferences. Candidates with less than 1% are not allowed to use delegated votes to discourage a frivolous proliferation of candidates.''
|valign=top|
<small>'''<u>Automatic approvals</u>''': When approvals are assigned automatically for candidate X, they are set to approve as many of their pre-declared preferences as possible without approving both of the two candidates with the highest current approval totals that they prefer differently. (For example, say that X's preferences were for A>B>C>D>E, and the approval totals are 10, 30, 10, 20, and 15 alphabetically. B and D have the highest totals. So X's delegated ballots will be assigned to approve as many candidates as possible without approving both B and D; that is, they will approve A, B, and C.)</small>
<small>'''Consistent with preferences, with equally preferred ties broken by current approval totals''': For example, candidate A may not approve B and not C unless ''either'' A predeclared a preference for B over C, ''or'' A predeclared B and C equal and B currently has more approvals than C.</small>
|-
|valign=top|
<big>4. When step 3b ends, highest total wins</big>
::ii. ''(optional)'' If the candidate with the most approvals has 5% approvals or less, their delegated ballots are used automatically* to approve their preference between the frontrunners. ''Automatic approvals respect predeclared preferences but prevent minor candidates from having discretionary kingmaker power.''
|valign=top|
<small>'''Automatic approvals''': When approvals are assigned automatically for candidate X, they are set to approve as many of their pre-declared preferences as possible without approving both of the two candidates with the highest current approval totals that they prefer differently. (For example, say that X's preferences were for (A and B), then C, then (D and E), and the approval totals are 40, 30, 10, 20, and 15 alphabetically. A has the highest total; B has the next-highest, but does not count, because they are preferred equally to A; and D has the next-highest. So X's delegated ballots will be assigned to approve as many candidates as possible without approving both A and D; that is, they will approve A, B, and C.)</small>
|-
|valign=top|
<big>'''4. When step 3b ends, highest total wins'''</big>
|
<small>'''Write-ins''': If write-ins are allowed, write-in candidates can not declare preferences or use delegated votes, but can be approved at will by official candidates, regardless of the official candidate's declared preference order.</small>
|}
 
=== Notes on rules ===
(technical issues; moved to talk page)
==== Finish resolving the "Chicken Dilemma" ====
Rationale for breaking equal-ranked ties using approvals in step 3.b)i.: One of the toughest situations for any voting system is the "Chicken Dilemma" between two near-clones. Say there are 60% "Blue" voters and 40% "Orange" voters; but the Blue voters are split between two candidates, say 35% for Navy and 25% for Sky. Any good voting system will allow one of the Blue candidates to win, if all the Blue voters support both of their candidates. But under many systems, there is a temptation for the Sky voters not to support Navy, so as to make sure that Sky, rather than Navy, is the winner. But if the Navy voters respond in kind, then Orange could defeat them both.
 
http://chart.apis.google.com/chart?chs=300x225&cht=p&chco=103289,76A4FB,FF9900&chd=s:VPY&chp=4.71&chl=Navy|Sky|Orange
 
This is called the "Chicken Dilemma" because it resembles a [http://en.wikipedia.org/wiki/Chicken_(game) game of chicken], in that both blue factions benefit from being the only one to deny support, but both lose if both deny support. In fact, since no single blue voter can reliably know exactly how other voters in the two blue factions will behave, it resembles a blindfolded game of chicken.
 
This dilemma can be a problem for many voting systems. Approval voting, Range voting, Majority Judgment, and many Condorcet systems such as Schulze voting — all of them good systems — all can have some version of this problem. There are a few voting systems, such as IRV and some versions of Condorcet, which correctly elect Navy no matter what the Sky voters do. But these systems go too far in fixing the problem, and thus get bad results in some situations that superficially resemble the true "chicken" scenario in some way.
 
SODA already does better than most systems in resolving the chicken dilemma. The two blue candidates can each make sure that the other one includes them in the predeclared preference order. Then, if all votes are delegated, Navy, starting with more approvals, will add approvals to those delegated votes first (after Orange), and not approve Sky. Sky will be forced to approve Navy, or see the orange candidate win. Thus, Navy will win — the correct result.
 
But if the Sky voters are especially strategically-inclined, they could give Sky non-delegable approvals instead of delegable votes. If Sky did not have enough delegable votes to help Navy defeat Orange, then Navy would be forced to approve Sky, and Sky would win. Of course, the Navy voters could do the same thing; either "defensively" or "in retaliation", it doesn't matter. And so, while SODA resolved the game of chicken for the candidates, it is still a possibility if the voters are ruthless and engaged enough.
 
This rule would allow Orange to give the win to Navy (the correct winner) if Orange wished to; in the case where the Sky voters had attempted the strategy in the previous paragraph. Remember, if Orange had cared to, they could have declared a preference between Navy and Sky to start out with. This thus resolves the chicken dilemma completely, without causing other bad scenarios; something no other serious voting reform proposal can claim.
 
Unfortunately, while the rule itself is simple, it's taken 6 paragraphs to explain the rationale. This is probably too much complexity for most voters, and so this refinement is not recommended for an initial implementation of SODA. However, it is good to know that such a clear, simple fix exists, in case chicken-dilemma-style strategizing became a problem later on.
 
==== Prevent weak minor candidates from having kingmaker power ====
 
Step 3.b)ii.
This rule helps make this system more attractive to major-party politicians. But it's a principled rule, not just a sop to the major parties. Consider the "kingmaker" case: in a basically 50/50 split, some tiny party has the balance of votes, and manages to extract concessions far bigger than their base of support justifies, just in order to delegate those votes or not. That's unjust, and this rule would prevent it.
 
5% is a good cutoff here; for instance, nationally in the US, that's tens of millions of voters, and enough to deserve a voice. It shouldn't be too high, because this rule is effectively taking power away from voters; that's only justified if the faction is so small that the power is not legitimate, and so it's better to err a bit on the small side if anything. But under 5% - that is, under 10% of the winning coalition - doesn't deserve kingmaker power.
 
== Example ==
Line 104 ⟶ 80:
{{Tenn_voting_example}}
 
In this simplified example, all the residents of each city agree on the rankings of all the other cities, so there would be no reason for anybody to do anything but bullet vote. Memphis has the first option to choose approvals for its delegated votes, and, as the leader, decides to approve noone but itself. Nashville goes second; it is the pairwise champion (Condorcet winner), so it also declines to approve any others. ChatanoogaChattanooga and Knoxville would approve each other and Nashville, to prevent Memphis from winning. Nashville would then be the winner, with 58% approval after delegation.
 
ChatanoogaChattanooga could, before the election, not include Nashville in its preference list, hoping to force Nashville to approve it. But in that case Memphis would approve Nashville to prevent Nashville from being forced to hand the election to ChatanoogaChattanooga, and so Nashville would win with an even larger majority. Therefore, ChatanoogaChattanooga will not attempt this.
 
== Advantages ==
Line 134 ⟶ 110:
# SODA should be generally '''acceptable to honest officeholders''', who are winners in a Plurality two-party system. Most of their familiar ways of thinking about the campaign would still work - except that it would reduce negative campaigning. Plurality-style voting still works just fine, and if most votes are for major parties, this system will cleanly allow a major party to win, in many cases without going to the delegation round (especially if the major-party candidates do not pre-announce delegation preferences, thus preventing an extorting minor party from demanding their delegated votes).
# SODA would make a politician's job '''more fun'''. Less time spent on fundraising (see process advantage #3), fewer attack ads from opponents (see process advantage #2); what's not to like? Sure, nobody would be a politician today without a high tolerance for these problems, but even for politicians, negative ads and the fundraising treadmill have gotten out of hand.
# SODA '''reduces the threat from unserious candidates'''. Under plurality, an even an unqualified candidate can be a spoiler. Under Condorcet or Approval, they can prosper simply because of second-choice support from two polarized camps. In fact, in the latter case, candidates can do ''better'' the ''less'' voters know about them! If there's anything that annoys a serious politician, it's losing to an unqualified cipher. SODA has no such problem, unless one of the candidates with more first-choice votes puts their reputation on the line by explicitly choosing the centrist twice (in order to avoid something worse), not just once but two times. That's not going to happen for an unknown.
 
== Criticism and responses ==
=== "ThereToo arecomplex"? otherNo; systemssimplest whichfor are better in some waysvoters." ===
While the rules for counting SODA are indeed a bit complex, no other system is simpler for the voters, allowing them to simply vote their favorite and go home confident that their vote has full strategic power.
 
=== "Delegation is undemocratic"? No; it's a free choice by voters. ===
This is true. Condorcet, Range Voting, and Median systems (MJ, MCA, or Bucklin) each have some claim to be the "best voting system". But SODA is the best system which has no downsides versus plurality. All those other systems require more-complicated ballots. All of them require more-complicated, or even dishonest, strategic decisions from the voter, to get the most effective vote.
 
So in the end, while any of those other systems would be, in my opinion, a clear net benefit versus plurality, with SODA you don't need any qualifications like "'''net''' benefit" or "in my opinion". It is simply better, in every way.
 
=== "Delegation is undemocratic" ===
Simple response: if you don't want to delegate, don't delegate. You can still vote for whomever you want.
 
Line 152 ⟶ 125:
Simple response to a ''politician'' who makes this argument: "You just want the only smoke-filled room to be the one inside your skull." That is, minority factions '''should''' have a seat at the table, as long as everything is done transparently. The two-party system stifles some of the valid concerns of the members of the party coalitions. In SODA, all vote totals, preference orders, and final approvals added to delegated ballots are known; in the end, that's not a smoke-filled room, it's a transparent seat at the table, with a just degree of power which is derived from the people.
 
=== "There are other systems which are better in some ways"? Yes, but unlike them, SODA is better than plurality in ALL ways. ===
=== "Sounds too much like a parliamentary system, which has caused problems in [Italy / Israel / wherever]" ===
 
This is true. [[Condorcet]], [[Range Voting]], and Median systems like [[Majority Approval Voting]] (or others: [[Majority Judgment]], [[MCA]], or [[Bucklin]]) each have some claim to be the "best voting system". But SODA is the best system which has no downsides versus plurality. All those other systems require more-complicated ballots. All of them require more-complicated, or even dishonest, strategic decisions from the voter, to get the most effective vote.
SODA does involve some parliamentary-style negotiation for about a week after each election. But then it's done, and the winner is in power until the next election. Unstable parliamentary countries, or ones where minority parties have inordinate power, are that way because minority parties can leave the governing coalition at any time. SODA does not have that problem; in many ways, it's really the best of both worlds between a 3-branch system and a parliamentary system.
 
So in the end, while any of those other systems would be, in my opinion, a clear net benefit versus plurality, with SODA you don't need any qualifications like "'''net''' benefit" or "in my opinion". It is simply better, in every way.
=== "Why go to the trouble of pre-announced rankings and a second round? Why not just have candidates pre-announce the approvals they will add to their delegated votes?" ===
 
=== "Sounds too much like a parliamentary system, which has caused problems in [Italy / Israel / wherever]"? No, SODA still leaves "buck stops here" responsibility. ===
This sounds appealing, but would not work if two similar candidates were in a close race to see which had more first-choice votes, while an opponent stood ready to take advantage if they split the vote (that is, in the Chicken Dilemma, also discussed above). The system as it stands allows the similar candidates to see, after the votes are counted, which of them deserves to win: the one with the higher approval total. That one will go first and not delegate their votes, and then other one (of necessity) will.
 
SODA does involve some parliamentary-style negotiation for a short period after each election. But then it's done, and the winner is in power until the next election. Unstable parliamentary countries, or ones where minority parties have inordinate power, are that way because minority parties can leave the governing coalition at will, triggering new elections. SODA does not have that problem; in many ways, it's really the best of both worlds between a 3-branch system and a parliamentary system.
 
=== "Why go to the trouble of pre-announced rankings and a second round? Why not just have candidates pre-announce the approvals they will add to their delegated votes?" Because the best compromise is only clear after the votes are tallied. ===
 
This sounds appealing, but would not work if two similar candidates were in a close race to see which had more first-choice votes, while an opponent stood ready to take advantage if they split the vote (that is, in the Chicken Dilemma, also discussed on the talk page). The system as it stands allows the similar candidates to see, after the votes are counted, which of them deserves to win: the one with the higher approval total. That one will go first and not delegate their votes, and then other one (of necessity) will.
 
In general, this system, because it provides perfect information on voting totals at the time when delegation is happening, will make strategy obvious. This has the paradoxical result that, as long as most voters agree with their favored candidate's chosen ranking order, this system will in practice be '''more Condorcet compliant than a Condorcet method''' (because strategy could confound a true Condorcet method more often than SODA).
 
== Criteria Compliance ==
SODA itself does not satisfy [[monotonicity]] due to a complicated and implausible scenario involving 5 or more candidates. However, a slightly-modified version in which, before the delegated assignments, candidates can self-assign a penalty to be assessed at the end of the delegated assignment round, does. This modified version, MODA, is effectively identical to SODA for any plausible real-world election.
 
SODAMODA satisfies [[monotonicity]], the [[favorite betrayal criterion]], the [[majority criterion]], and the [[mutual majority criterion]]. Depending on assumptions and definitions, it can pass the [[Condorcet loser criterion]].
 
It does not satisfy the [[independence of irrelevant alternatives]] criterion in general, but it does if the "irrelevant alternative" is assumed to delegate votes in the same way as any candidate whose delegable votes they supplant. Similarly, it can only pass the [[participation]] and [[consistency]] criteria if it is assumed that candidate delegations do not change. These assumptions are ''not'' realistic, but they do show that the method is in some sense "close to" passing these criteria.
 
In any case where honest delegation could show a majority Condorcet winner, such delegation forms a strong Nash equilibrium. This shows that in general, strategic refusal to delegate is likely to fail.
 
=== Condorcet criterion (includes highly technical discussion) ===
Line 172 ⟶ 154:
*''Candidates are honest'' in their pre-election rankings. This could be because they are innately unwilling to be dishonest, because they are unable to calculate a useful dishonest strategy, or, most likely, because they fear dishonesty would lose them delegated votes. That is, voters who disagreed with the dishonest rankings might vote approval-style instead of delegating, and voters who perceived the rankings as dishonest might thereby value the candidate less.
*''Candidates are rationally strategic'' in sharing their delegated vote. Since this process is sequential, game theory states that there is always a subgame-perfect Nash equilibrium, which is always unique except in some cases of tied preferences.
*''Voters'' are rationally strategic or otherwise able to use the system to ''express all relevant preferences''. That is to say, all voters fall into one of two groups: those who agree with their favored candidate's declared preference order and thus can fully express that by delegating their vote; or those who disagree with their favored candidate's preferences, but are aware of who the Condorcet winner is, and are able to use the approval-style ballot to express their preference between the CW and all second-place candidates. "Second place" means the Smith set if the Condorcet winner were removed from the election; thus, for this assumption to hold, each voter must prefer the CW to all members of this second-place Smith set or vice versa. That's obviously always true if there is a single second-place CW.
*''Delegated votes are honest''. That is, voters do not delegate their vote to a candidate whom they disagree with. Though such a strategy might work in limited circumstances (when a candidate with exactly the right preferences was available to use to create a Condorcet cycle which didn't include themself), it would be both more trusting and risky than the average strategic betrayal, and also more cold-bloodedly dishonest. To exaggerate the case: how often are psychopaths good at trusting people?
The assumptions above would probably not strictly hold true in a real-life election, but they usually would be close enough to ensure that the system does elect the CW.
Line 183 ⟶ 165:
 
== SODA-PR (obsolete; see [[PAL representation]]) ==
(Section obsolete; seefor insteada proportional representation system based on SODA-like ideas, with several unique advantages, see [[PAL representation]].)
 
SODA-PR is the [[proportional representation]] version of the above.
 
First, to simplify the ballots, the population is separated into a "district" for each seat, and "districts" are grouped into sets of 2 or 3 "co-districts". The ballot for each district lists the candidates from that district in a larger font, and the candidates from its co-districts in a smaller font. Write-ins may be used to vote for candidates from other districts not listed on the ballot, so the districts only matter for ballot simplicity (Voters do not want to have a ballot with many dozens of candidates on it, but write-ins allow full freedom for those voters who want it). Larger parties will usually run one candidate per district; smaller parties may just run one candidate per co-district set.
 
As with SODA, voters can either vote an approval-style vote or delegate by bullet voting. Instead of a pre-announced ranking which allows them to choose a cutoff after the election, candidates have a pre-announced list of approvals that will be added to any votes delegated to them (beyond the votes they need to be elected). Candidates may make their approval of other candidates conditional on that approval being mutual, but they may not make it conditional on anything else about the other candidate's approvals. Thus, parties cannot protect corrupt members by forcing other candidates in the party to approve of them.
 
The counting process is as follows:
*While there are more uneliminated candidates than empty seats:
**Divide each ballot by the number of uneliminated candidates it approves
**If there are any candidates with more than a Droop quota:
***Elect the one with the highest score (previously "unique ballots")
***Reweight ballots for the elected candidate to reduce the total weight by a [[Droop quota]], starting with the ones delegated to that candidate
***Add the elected candidate's pre-declared approvals to any remaining delegated ballots for that candidate
**Otherwise:
***Eliminate the candidate with the lowest score
***Add the eliminated candidate's pre-declared approvals to any delegated ballots for that candidate
*Finally, elect all remaining candidates to fill the remaining seats.
 
Note: If all votes are for one of the two main-party candidates in the voter's district, and if all candidates approve everyone from their party, and if the districts are divided fairly so that plurality would give a proportional result, SODA-PR gives the same results as plurality. These assumptions will not generally be perfectly true, but they will generally be close to true, so SODA-PR will give results that are recognizably similar to those of single-member districts. It is hoped that this would make it a more acceptable system to politicians who have won under single-winner rules.
 
==Compatibility with the US electoral college==
Line 213 ⟶ 175:
 
Each "undelegated approval elector" would know the statewide non-delegated approval total, and the total of number of affiliated electors throughout the EC, for each candidate. Other "approval electors" would count as fractionally affiliated based on their known approval totals. These electors would be sworn to vote for whichever of the two candidates with the most nationwide electors had the highest statewide undelegated approval total. They would be chosen by the candidate for whom they were sworn to vote.
[[Category:Single-winner voting systemsmethods]]