Recommended to post all proposals to the forum for discussion 7 days before being submitted to vote.
Proposal Types and Sub-types
<aside> đź’ˇ The following template should be followed any time a proposal is made that involves withdrawing funds from the Budget Vault of the Aragon DAO. This may include funding a full-time time team, a time-bound project with fixed deliverables, other project investments, token swaps, etc.
</aside>
Title: Clear and precise, indicating that it is a funding request. E.g. “Ecosystem Guild Funding Request”.
Transaction: Please describe in 1-2 sentences the exact nature of the on-chain transaction that will execute if this proposal were to pass, including the destination address of the withdraw. Any mismatch between what is stated here and the payload submitted to the DAO will result in a Guardian veto.
Financial Compliance: Fill out the following form and specify here: **“**I have completed a Financial Compliance Form for this Withdraw Request.” Your withdraw request will otherwise be vetoed.
Description: 1-2 short paragraphs explaining how much funding is being requested, by whom, and the high level value that is planned to be created for Aragon. Focus on the strategic relevance.
Objectives [only applicable for teams and deliverables]: The goals the individual or team has set. It is recommended to use the OKR framework. 3-5 objectives with 3-5 key results each is common. The objectives here should support the organization objectives included in the Aragon Annual Plan.
Details: This is the bulk of the proposal and the most open-ended section. It should contain a longer, more detailed description, as well as content that is relevant to the nature of the work being done by the team (e.g. technical specifications for an engineering team). This should be considered the “expert deep dive.” The granularity of detail will depend on the work being done and the amount of funds being requested (e.g. large funding requests will require more detail than a small funding request).
Team [only applicable for teams and deliverables]: A description of all of the people intended to be compensated with the requested funds. Describe each person and their relevant experience. Include a job description for any new positions that need to be filled and indicate who is responsible for the hiring decision.
Funding Breakdown [only applicable for teams and deliverables]: Funding breakdown by expense category. If streamed funds are being requested, it should be specified how the payments are to be structured. Please see Finance Operating Model for more information.
Risks and Dependencies: Highlight the risks that could prevent the objectives from being fulfilled. Consider any dependencies on work from another workstream (not an external event like a pandemic or recession). For example, specify the risk of one team blocking another (a product team blocking growth’s launch plans), risk team members leaving, or risk of not meeting hiring goals.
Title: Clear and precise, including versioning or an indicator to make a distinction between potentially competing AAPs. E.g. “2023 Annual Strategy v1”.
Sponsors: A list of token holders or delegates who are endorsing this proposal.