> For the complete documentation index, see [llms.txt](https://docs.visiongame.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visiongame.io/visionnexus-depin/visionnexus-introduction/core-philosophy.md).

# Core Philosophy

VisionGame’s philosophy is rooted in community empowerment and shared success, principles that shape every aspect of VisionNexus. VisionNexus was built to embody these values, offering a platform where individual contributions become part of a larger purpose. By allowing license node holders to join forces through guilds and contribute resources like storage and computational power, VisionNexus enables members to actively participate in a decentralized network that benefits everyone involved.

Our commitment to a “win-win-win” approach means that VisionNexus isn’t just about technology—it’s about creating meaningful, community-driven opportunities. Every node holder plays a role in powering VisionGame’s ecosystem, and in return, they share in its rewards and growth. VisionNexus stands as a testament to VisionGame’s belief that GameFi thrives when its participants feel ownership, purpose, and connection.


---

# 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:

```
GET https://docs.visiongame.io/visionnexus-depin/visionnexus-introduction/core-philosophy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.