A conversation
Designing a city’s participatory budget.
Frame: Plurality, Weyl/Tang/⿻ Community (2024).
You
A city budgeting platform serves 50,000 residents. City staff select eligible projects. Residents discuss them in one public forum, then vote yes or no on each project. Projects are ranked by total yes votes. What should we examine before launch?
→ plurality.assess_plural_design(…)
Claude
The tool’s six-layer rubric surfaces three unresolved design questions. Association: Can affected publics form around shared consequences, rather than only through a citywide resident roll? Augmented deliberation: Can the forum surface agreement across groups, and can its findings change the outcome? Plural voting: Does a yes/no tally capture intensity, delegation, or overlapping affiliations? These are questions to investigate—not evidence that any one voting mechanism is automatically right.
Plurality, Ch. 4-2, Ch. 5-4, Ch. 5-6
Other books read this differently
Think Like a Commoner, Bollier
Ostrom’s rubric starts with the commons itself: eligibility, admission, rule changes, and which decisions remain local. The proposal names residents but does not answer those questions. Ch. 2.
Governable Spaces, Schneider
Residents can vote, but staff control which projects qualify. Schneider’s lens asks whether the vote is binding, who controls the agenda, and whether residents can change those rules. Ch. 1 and Ch. 5.
