> For the complete documentation index, see [llms.txt](https://avania.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://avania.gitbook.io/whitepaper/vision-and-mission.md).

# 👓 Vision & Mission

### Vision

" Supporting people to earn happiness by playing games "

We believe that happiness can be described in many ways such as fun moments, warm relationships, self-esteem, money, ETC.&#x20;

We also believe that happiness is a purpose of living. It is a goal of life, people are searching for it.

As a result, we would like to support people in every way we can to make sure people can earn happiness happily. <br>

### Mission

* Focus on player centric.
* Create and maintain a sustainable ecosystem.
* Add interesting content and feature frequently.
* Build a supportive community
* Offer a reasonable reward to everyone in ecosystem.

![](/files/yTbHQ629AbgtJsoIHpyL)


---

# 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://avania.gitbook.io/whitepaper/vision-and-mission.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.
