Summary
A clear governance process is key for the DAO future. Clear guidelines help members to promote their ideas to become without the uncertainty created by unclear or scattered resources and guidelines. This proposal presents a life-cycle that upgrades our current processes and deliver a step-by-step guide that can be followed by any member.
Background
The PieDAO Governance process has been defined in several documents that are currently not linked to one another. This can create friction and uncertainty for users to submit ideas and for community members to visualize next steps. Below are the references used for this analysis
- Pie Template
- How to build Pies — Medium post
- Tiramisu — Pie Modeling
- Suggested Guidelines for Pie Proposals
- How to prioritize PIP guidelines
- Creating new Pies
While studying the current status, two discussions opened the door to rethink the current Idea→PIP→Vote flow to include a broather set of definitions to bootstrap the whole process
- Vote types and lenght: Forum post — by Shubiwubi
- Pie Signal Proposal (PSP): Vote — by Nico
The processes above do not cover all required aspects, and it is time for it to catch up with the level of maturity that the DAO has and apply the lessons learned.
Motivation
We expect to address the following points to allow proposals to be positioned for voting only after achieving an execution-ready status depending on their complexity.
- Segregate Complex from Simpler proposals
- Defining an approach that uses Gates and Stages
- Creation of a workbooks and templates
- Define Votes types and characteristics
- Quality assurance and community suppor through a moderator position
Specification
We propose to introduce the following changes
The information below is also available at Governing PieDAO in greater detail
1. Governance
1.1 Categories
Votes types are categorized in two main categories, and each one serve their own process flow
- Improvement proposals
- Generic Proposals
Improvement Proposals are called PIP (PieDAO Improvement Proposal). Their process requires two gates to be passed in order to be executed.
Generic Proposals are expected to be more light weight, requiering only one gate to be passed for execution.
1.2 Vote Types
All votes casted in Snapshot should be following one of these categories and consider the durations given below as the minimum required for their length. Types are categorized between Critical and Non Critical. Each type is described below into detail
Notarization How to Link: How to Notarize
1.3 Gate Baker
Moderation is a need to assure that:
- Members support and education over the proposal flow
- To assure submitted votes have met the gate-ready criterias
- Keep a DB for the submitted roles and segregate valid from invalid votes to support the Governance Mining eligibility criteria process
- Moderate the forum to lead conversations and keep conversations momentum and on topic.
** One role to bake them all! 
2. Introducing Gates!
Gates will act as check points designed to drive proposals efficiently and require a Snapshot vote. The amount of Gates will depend on the proposal type
- Improvement Proposals: Gate 1 >> Validation >> Gate 2 >> Execution
- Generic Proposals: Gate 1 >> Execution
2.1 Generic Proposals Gates
2.2 Improvement Proposals Gates
2.3 Considerations
PIP Acceptance Criteria
In order to pass a PIP: 5% or more of veDOUGH supply must participate (current_supply * 0.05 = result), and 60% or more of participating tokens must vote in favor (FOR)
Maintenance
Casted votes not following the gate steps won’t be considered for the Governance Mining Rewards eligibility process. The only exception will be Critical votes types.
Snapshot entries will not be removed from the system.
Naming Convention
Proposals can or can not have a PIP number. Either case it is expected that they follow the following naming structure to facilitate reading
- Without PIP # → [Gate #] Proposal title
- With a PIP # → [PIP-#] [Gate #] Proposal title
In any case, the title has to be meaningful and honor the proposal in discussion
3. Introducing Stages!
Stages are all the steps and activites that happen between gates, which do not require a Snapshot vote. They tick all the boxes for the conversation to move towards a gate vote in good shape, and determine the flow expected for the whole lyfe-cycle of each proposal type.
3.1 Generic proposal stages
- Forum Discussion: Proposed Idea to be discussed in the Forum
- Gate 1: Validate the community agreement through a vote
- Production Release: Execute the proposal
More level of details defined here: Generic Proposal Stages
3.2 PIP stages
- Forum Discussion: Proposed Idea to be discussed in the Forum
- PIP Gate 1: Gauge members support on the Idea
- PIP Refinement: Improvement Proposal refinement
- PIP Validation: Validation of Scope
- PIP Staging: Proposal pre-gate Staging
- PIP Gate 2: PIP Voting
- Production Release: Execute the proposal
More level of details defined here: Improvement Proposals Stages
4. Processes flows charts
Flows are visual aid images to understand what to do on each step, and they vary depending on the Proposal type. Below we will mention Generic and Improvement proposal’s into detail.
4.1 Generic Proposal Flow
4.2 PIP Flow
Improvement proposals have two flows to differentiate between Standard and New/Rebalancing Pie proposals.
4.2.1 Standard Proposal Flow
4.2.2 Pie Proposal Flow
Templates
- Generic Proposal Gate 1 — Template
- Notarization Vote — Template
- PIP Gate 1 — Template
- Standard PIP Gate 2 — Template
- PIE PIP Gate 2 — Template
- Pies Creation/ Rebalance — Template
Closing notes
Clarity during the process, good level of support, visibility on the next steps and MVP quality standards assurance are the key deliverables that will make us implement great products and changes and facilitate the decision making for the PieDAO community members.
Your suggestions, comments or simply support will be much appreciated!
- Yes
- No
- Needs Refinement
0 voters
- Yes
- No
- Needs Refinement
0 voters
- Yes
- No
- Needs Refinement
0 voters
- Yes
- No
- Needs Refinement
0 voters
