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

# About GOW39 Team

<figure><img src="/files/PEIcTVLIewZn8CzZCD3I" alt=""><figcaption></figcaption></figure>

Join us to get to know Gow39 team!

Currently, GOW39 has a total of 17 people, divided into 4 teams according to different areas. In particular, the four leaders have all implemented many million-dollar projects and are highly experienced. All members work based on creativity and a systematic system for each work item.

GOW39 is a long-term project and will build a product system to provide many utilities for owners, we are implementing many products for GOW39 such as: NFT, Staking, Lucky spin,... We believe that we can meet the launch schedule. and development of the project in the long term. Team personnel will be added after launch to be able to develop more products in the near future.<br>


---

# 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://gow39.gitbook.io/whitepaper/about-gow39-team.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.