📖
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

1. Control Surfaces for Automated Systems

Perhaps the most transformative application of MetaPolls is as parametric control systems for automated infrastructure. This creates a direct interface between collective preferences and executable code.

How It Works

The MetaPoll becomes a user interface that N people collectively operate to control various aspects of their shared systems. The ranked preferences generate variables that are passed directly to functions, smart contracts, or agent systems.

Consider what makes an effective control surface:

  • Explicit optionality - Include the full range of possible values, even when some seem obvious

  • Variable mapping - Design option titles that can be interpreted as function parameters

  • Automated execution - Connect poll results to code execution through APIs or smart contracts

  • Continuous adjustment - Focus on parameters that need ongoing community alignment

For example, in treasury management, we might define asset allocation parameters:

title [Treasury asset allocation]

options [

=Asset Allocation

==ETH

===100%

===100% to 70%

===69% to 30%

===29% to 10%

===0%

==USDT

===100%

===100% to 70%

===69% to 30%

===29% to 10%

===0%

==DAO token

===100%

===100% to 70%

===69% to 30%

===29% to 10%

===0%

]

This creates a direct mechanism for treasury rebalancing based on collective risk preferences. The community isn't voting on one-off allocation decisions but creating an ongoing sentiment stream that drives treasury composition.

The critical insight here is that explicit agreement, even on seemingly obvious choices, creates legitimacy and accountability. If ETH allocation is ranked highest with "100%" as the top sub-option, this creates a clear record of community intent that can be referenced when actions are taken.

Other examples of control surface applications include:

  • Community-controlled funding allocation

  • Automated market maker parameter adjustment

  • DAO governance rule calibration

  • Protocol parameter optimization

  • Community-driven AI agent direction

PreviousExample MetaPoll typesNext2. Information Sources for Decision-Making

Last updated 10 days ago