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

# Long-Term Vision

BIG Indie Games is building for the long term.

Our focus is not only to launch a token, but to create an ecosystem where games, revenue, community, and Web3 value all work together.

We want to prove that a gaming project can build for regular players while still creating real utility and transparent support for its token ecosystem.

The goal is simple:

·    Build games people love.

·    Generate real revenue.

·    Use part of that revenue to strengthen $BIG.

·    Stay transparent with the community.

·    Grow step by step.

BIG Indie Games is not just a token project. It is a gaming company with a Web3 engine.


---

# 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://docs.bigindie.games/long-term-vision.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.