> For the complete documentation index, see [llms.txt](https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/introduction/want-to-contribute.md).

# Want to contribute?

What qualifies as a successful pattern?

* [ ] An overall positive impact in helping your organization achieve its purpose (feel free to share what benefits you gained in your entry).
* [ ] Adheres to the regenerative standards, ethics, and protocols detailed in the [SEEDS Constitution](https://joinseeds.earth/pdf/Official_SEEDS_Constitution_V_1_July_10_2021.pdf) where the pattern is consciously designed to positively impact the wellbeing of all people, our planet, and our shared prosperity.   &#x20;

Follow these steps:

1. Duplicate and use the template.
2. Submit a change request.
3. Hop over to the [SEEDS Discord](https://discord.gg/dSFeSW4) and share your accomplishment!&#x20;


---

# 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://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/introduction/want-to-contribute.md?ask=<question>&goal=<endgoal>
```

`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.
