📖
MetaPoll | Docs
  • Introducing MetaPoll
  • Getting Started
    • Take the MetaPoll tour!
    • FAQs
    • Quickstart Mission
  • MetaPoll User Guide
    • Signing In
    • Adding and Removing DAOs
    • Browsing MetaPolls
      • Filtering MetaPolls by DAO
      • Search and Other Filters
      • Main card
    • Viewing MetaPoll Results
      • Snapshots
      • Options
      • Child Options, Layers, and Navigation
    • Voting
      • Ranked and Unranked Options
      • Ranking and Unranking Methods
      • Casting Your Vote
      • Viewing Vote History
    • Eligible Tokens and Vote Calculation
    • Vote Decay
    • Graduation
  • Authoring MetaPolls
    • Basics of Creating MetaPolls
      • Creating a new MetaPoll
      • Setting up the MetaPoll
      • Creating Options
      • Publishing a MetaPoll
      • Managing your MetaPolls
    • Working with MPTS format
    • Option space design
      • Option Naming Styles: The Abstraction-Precision Trade-off
      • State Change Loop
      • Utility Formats
    • Example MetaPoll types
      • 1. Control Surfaces for Automated Systems
      • 2. Information Sources for Decision-Making
      • 3. Proposal Temperature Checks
      • 4. Proposal Election and Expectation Management
      • 5. Representative Guidance Systems
  • Hypothetical MetaPolls
  • Advanced Topics
    • Decision Spaces
    • Snapshot Data Structure
    • VCIP - Voter Compute Integrity Proof
    • VDIP - Voter Data Integrity Proof
    • Arweave Perma Storage
    • Verkle Trees
    • ZKsnarks
  • Appendix
    • Links
    • Glossary
Powered by GitBook
On this page
  1. Authoring MetaPolls
  2. Example MetaPoll types

4. Proposal Election and Expectation Management

MetaPolls can create dynamic, ongoing prioritization systems for proposals or products that combine automatic selection with preference specification.

How It Works

The community ranks a set of potential options (projects, products, proposals), with automatic selection of the top N items for active status. Each option contains nested preferences that specify implementation details once selected.

For example, a community cafe might use a MetaPoll to determine which drinks to include on the menu:

title [Starbonks Drink menu]

options [

=Latte

==Milk Type

===Whole

===2%

...

=Americano

...

]

(Full example abbreviated but includes extensive customization options)

In this system, only the top 10 drinks might be offered, with automatic rotation based on changing community preferences. Within each selected drink, the most preferred customization options become the default offering.

This creates a hybrid system where:

  1. Top-level selections are automatically implemented (only top-ranked drinks appear on the menu)

  2. Nested preferences provide implementation guidance (default milk types, sweeteners, etc.)

Previous3. Proposal Temperature ChecksNext5. Representative Guidance Systems

Last updated 10 days ago