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

# Bio

The team is doxxed and professional, absolutely the best of the best, and have gained their experience working on some of the most successful token launches this year. They’ve got the dev & marketing experience to send Floki Millions straight to outer space.

#### Executive Team

Jack - Co-founder / CEO

Sean - Co-founder / Dev

#### Marketing

Moonman - Head of Marketing

#### IT & Web Dev

Noctis - Web/Dapp Developer

Smith - Bot master and community leader

Sir Tris - Smart Contract Developer

#### Graphics and Design

Yathir - Head of Graphics

Rob - Videographer / design

#### Community Engagement

BP - VC host and community leader

J Foster - publicist / dev advisor

1000x Boss - Shill / Raid leader

Hannah - Social media and community leader

Bear - VC/AMA and community leader

Camilla - socials


---

# 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://floki-millions.gitbook.io/floki-millions/team/bio.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.