> For the complete documentation index, see [llms.txt](https://safaricrush.gitbook.io/safaricrush-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://safaricrush.gitbook.io/safaricrush-whitepaper/future.md).
# Future
Safaricrush is currently in the alpha stage and is just the first step of a long journey ahead.\
We will deploy various marketing strategies to make this simple yet amazing game available to more people, and we will continue to release new stages and contents for the game.
In the future, we plan to expand the reach of our simple and exciting game so that more people can enjoy it by deploying various marketing strategies. We will continue to release new stages and content for the game. We also plan to establish licensing partnerships with various companies to sell Safaricrush Friends character licenses or recruit other companies' characters as new Safaricrush Friends and sell them as NFTs. Furthermore, as the game volume grows, advertising revenue will undoubtedly continue to increase. All of these revenues are designed to be distributed to $SFRC holders as part of our economic structure. Stay tuned, as amazing things will continue to unfold over time
---
# 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://safaricrush.gitbook.io/safaricrush-whitepaper/future.md?ask=&goal=
```
`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.