An ADP idea is created as a post in our forums and must be approved by one of our moderators with a confirmation that it complies with the DAO-approved guidelines before it appears to the community. The party submitting the ADP idea will be referred to as the Initiator or Initiators (multiple members can work together on an ADP intention). The ADP idea informally gathers comments in the forum thread for 14 days. The initiator cannot edit the original post - if the initiator wants to propose changes to the original intention, he must do this via the comments.
After the 14 days feedback window has passed and the moderator closes the topic, one of our moderators will send the initiator the proposal template and the next steps for submission and voting. They can also create a proposal category if necessary.
The initiator will fill out the template and can add additional information if necessary to better communicate the scope of the ADP draft. The moderator may also inform the author of incorrect or missing information that needs to be changed. If the initiator does not respond to those requests within 14 days, the ADP draft will be automatically rejected.
When the admin confirms that an ADP Draft complies with the DAO-approved guidelines, they assign a number to the ADP for identification purposes.
The ADP is reviewed by a project manager from our team that is engaged with the Alpha Dune DAO who will provide a report that will breakdown and review the costs, implementation steps, legal considerations, potential conflicts of interests and any further implications that have been identified.
Given that ADP initiators can create drafts with little to no resources, this layer ensures that the DAO community has enough information about the proposals in order to make the best decisions when voting.
The ADP Draft is reviewed by a team of moderators and either approved or not approved based on wether it adheres to the guidelines. If not approved, it is eligible for resubmission after 60 days have passed since the initial submission, except in cases of violation of the law or reasonable suspicion of fraud or other misleading information.
Pending ADPs that have passed ADP Review are tagged as “Ready for Vote”.
The “Ready to Vote” tag is given to a pending ADP whose costs, content, and implications are considered straightforward and of no risk to the well-being of the DAO.
Pending ADPs that have passed their respective approval processes will become Live ADPs on Snapshot during the next Weekly ADP Release, which is when new ADPs are released in batched. Once live on Snapshot, live ADPs are open to voting until the vote closes. Moderators are the only ones that can post ADPs to snapshot because they must confirm that each one has gone through the correct approval process.
At this step, the ADP will be available in Snapshot for community voting. All Alpha Dune token holders will be able to participate in the voting process.
If a Live ADP has not gotten the necessary votes, it will be tagged as "Rejected" and be eligible for resubmission in 90 days after the vote has passed. Rejected ADPs can be resubmitted via the standard process if the author contacts a moderator.
Accepted ADPs that have passed the vote will move into implementation.
For accepted ADPs that passed the voting phase, implementation will begin based on the steps outlined in the ADP template. The project management team engaged by the Alpha Dune DAO is responsible for making sure this happens, but is not responsible for doing it themselves.
If a suggested proposal directly conflicts with a proposal that is currently up for vote, the second proposal should not go for a vote until a decision is made on the first proposal to avoid approval of opposing requirements.
A suggested proposal that directly conflicts with another approved proposal cannot go to vote for 90 days after the original proposal has been implemented to avoid wasting community assets.