> For the complete documentation index, see [llms.txt](https://docs.abachi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abachi.io/abachi-governance/overview.md).

# Overview

The Abachi team is working hard behind the scenes to start putting in place policy, ux, partnerships, marketing and dev teams. Our research team is already in place. All of these positions other than a few core team members from day 1 will be filled from the community.&#x20;

We are ***committed*** to move Abachi eventually into a legal DAO structure. Until a DAO is established, Abachi will be run under a for profit foundation and we will still utilise snapshot for governance decisions with transparency to the community.

**Want to be a part of the new teams? DM any of the core team, founders, mods.**

While the greatest weight of governance is given to those who lock staked ABI for 2 years in a governance contract.&#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://docs.abachi.io/abachi-governance/overview.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.
