> For the complete documentation index, see [llms.txt](https://zendius-jsc.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://zendius-jsc.gitbook.io/docs/welcome.md).

# Welcome!

{% hint style="info" %}
**Who are we:** We are a collective of visionary game developers and industry pioneers, united by a shared passion for redefining the gaming landscape. Our mission is to transform traditional games into engaging, immersive experiences that captivate players and spark creativity among developers. 
{% endhint %}

For N**ew Team Members**, This space is designed to help you settle in smoothly during your first days with the team. Here, you’ll discover who we are, how we work, and where to find all the key information you’ll need to get started confidently.

For **Long-Time Team Members and Partners**, this space serves as a handy reference to revisit how we operate, access administrative details, and stay up to date with policies and resources whenever you need a refresher.

<details>

<summary><strong>Getting Started</strong></summary>

Wondering where to begin? Start with our Vision, Mission & Focus to understand who we are and what drives us. From there, explore each section to get familiar with how we work and where to find the info you need.

</details>

<details>

<summary><strong>Need Help?</strong></summary>

If you want to contribute changes, start a new change request and submit it for review. The People team will review it soon after.

</details>


---

# 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://zendius-jsc.gitbook.io/docs/welcome.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.