> For the complete documentation index, see [llms.txt](https://stradall.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stradall.gitbook.io/docs/project/our-mission.md).
# Our Mission
We are here to create an ecosystem of amazing STRADALL gaming experiences with community and player-owned economies as foundational pillars. By doing this we will deliver property rights to all users of the internet, starting with gamers.
Stradall is a digital nation where people globally come together to play, work, and make lifelong connections by creating Team together or play in versus .
When we started this journey 2 years we weren't sure where we'd end up but we believed that if we asked the right questions we could build something with you that had never been seen before in Web3. We asked:
What if we built a game that could onboard the world to Automotive and Web3?
What if we could make crypto nostalgic,educational, and immersive?
What if a game could be built by pilots, financials, developers and players working together through aligned incentives?
Welcome to the Stradall game to reality.
---
# 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://stradall.gitbook.io/docs/project/our-mission.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.