Elsewhere 2027 · Asociado vote
Eight dates.
97 voices.
One shared direction.
The vote, opened up. Explore the preferences behind the result, compare every date, and follow the count from ballot to outcome.
These results are calculated from the 18 September 2026 vote export. The winning week remains subject to the relevant authorities’ approval; the vote does not itself confirm the event dates.
01 / The result
A clear head-to-head winner
Explore a scenario: what if a date is unavailable?
Untick dates to recalculate with the same 97 ballots. This is an exploratory scenario, not a change to the vote. At least two dates must remain. Ranked dates come first, then omitted dates tied together, then explicitly rejected dates tied last.
Head-to-head wins are not the ranking rule: cycles can leave dates with the same number of wins in different places. The order above follows the locked Ranked Pairs graph.
02 / Every date against every other
Where the consensus sits
Read across a row: 53–39 means 53 ballots prefer the row date and 39 prefer the column date. The rest express no preference between the two. Select a cell to inspect that comparison.
03 / Beyond the winner
Enthusiasm, compromise, and rejection
A high first-choice count and broad support are different things. These views describe the same ballots; they do not replace the selected counting method.
04 / Show the working
No black box
Each head-to-head victory is considered in order of strength. Lock it in unless it would create a loop. The date with no incoming locked defeats wins.
See every lock, in counting order
Counting rules and interpretation
- Equal ranks: dates in the same rank group contribute no vote against each other. Ranked dates beat omitted dates; omitted dates beat explicitly rejected dates. Omitted dates are tied with each other, and rejected dates are tied with each other at the bottom.
- Victory strength: descending winning margin, then descending winning votes. Exact ties use the original option order, first the winner then the loser. This matches Humans’
RankedChoiceCounter. - Finishing order: repeatedly take a date with no incoming locked edge among the remaining dates. If multiple dates qualify, use original option order. The page reports when this fallback is needed.
- Rejection is not a veto: it places a date at the bottom of that ballot. It does not remove the date from the election.
- Percentages: general charts use all 97 ballots. Matrix percentage mode uses only ballots that distinguish the two dates. First-choice shares split one vote equally among tied first choices.
- Scope: this export is the Asociado vote, not the earlier 948-response attendee survey. It does not contain the eligible electorate size, so no turnout percentage is inferred. The export alone does not establish whether voting was formally closed.
A distinction from the earlier explainer: the voting-method page describes omitted and rejected dates as tied. Humans’ implemented count distinguishes them as described above. This page follows that implementation and matches the supplied results matrix. The distinction changes 6–12 September vs 5–11 July from 64–25 to 64–26; it does not change the winner or finishing order.
Context: attendee survey results · candidate-week evidence · voting method
05 / Look at the ballots
Different paths to a preference
Each row is one ballot. “=” means equally ranked; “→” means preferred to. Numbers are local references assigned after sorting by ballot content, not response IDs or submission order. This view always shows the original eight-date ballots, even in scenario mode.
06 / Take a closer look
Your own analysis starts here
Download all 97 ballots. These public copies retain the vote contents while removing response IDs, timestamps, submission order, language, input method, and confirmation answers. Ballot numbers match the explorer above.
Both source exports were cross-checked ballot by ballot before generating these files. No names or user IDs were populated in the source CSV. Distinctive voting patterns can still be recognisable; metadata removal is not a guarantee of anonymity. Downloads always contain the full vote, not the current scenario or filtered view.