> For the complete documentation index, see [llms.txt](https://support.axiondao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.axiondao.com/axion-dao-legacy-club/founders-membership-nfts/pioneers.md).

# Pioneers

Strategists helping forge the DAO’s legal and structural framework, lighting the way for others to follow.

![](https://lh7-rt.googleusercontent.com/slidesz/AGV_vUe3khxepJxKjgmG09TLpWNclkhMCS37pMt538U0zBeD7syo06keG9T4iKg6osw8yWmMWBoCLtnGGk_qPaLcwF2-kfFhAvp41oPlsaKdeyUEvwsKseF-hXonO559nvBNZ48Ulzs2=s2048?key=GaGsSv4lf6CaeYnY5woKpBDc)

 Pioneers are the bold strategists and builders who rolled up their sleeves and helped shape the DAO’s earliest structure. They laid the groundwork that others will stand upon. These are the community leaders, developers, and advocates who dared to move Axion from idea to action, helping us forge a legal and scalable future as a Utah DAO, Social Enterprise, and Corporate Cooperative. Strategic builders are helping forge the legal and operational framework that defines Axion DAO. The Pioneers don’t just dream—they plan. They were among the first to envision a compliant DAO model capable of sustaining partnerships, revenue generation, and governance. These are the hands that shaped the soil and paved the road forward for others to follow.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.axiondao.com/axion-dao-legacy-club/founders-membership-nfts/pioneers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.