> For the complete documentation index, see [llms.txt](https://docs.alphadune.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphadune.com/alpha-dune-governance/formal-adp-template.md). # Formal ADP Template ### A proposal typically includes: * **Abstract** - Two or three sentences that summarize the proposal. * **Motivation** - A statement on why the Alpha Dune community should implement the proposal. * **Rationale** - An explanation of how the proposal aligns with the Alpha Dune Community's mission and guiding values. * **Specifications** - A detailed breakdown of the technologies that will be used. * **Steps to Implement** - A breakdown for each step necessary for implementation and information regarding resources for each step where applicable. * **Timeline** - Relevant timing details, including but not limited to start date, milestones, and completion dates. * **Budget** - The total cost to implement the proposal. The author can add additional information if necessary to fully communicate the intentions, specifics, and implications of the ADP draft. **Proposals that did not make it through the respective approval process and are being resubmitted should also include:** * Link to original proposal. * Reason it was not approved. * Changes that have been made and why it should now be approved. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.alphadune.com/alpha-dune-governance/formal-adp-template.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.