> For the complete documentation index, see [llms.txt](https://wp.jannavi.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.jannavi.net/appendices.md).

# Appendices

{% content-ref url="/pages/2V6Yf09tacoPCIrYRMmV" %}
[JAN-Navi e-Sports Guidelines](/appendices/jan-navi-e-sports-guidelines.md)
{% endcontent-ref %}

{% content-ref url="/pages/ryglUV1uEAFrvhkUwBk6" %}
[JAN-Navi Demographics](/appendices/jan-navi-demographics.md)
{% endcontent-ref %}

{% content-ref url="/pages/4gICJH27hetCU97INnLg" %}
[Forecast for the Growth of the e-Sports Market](/appendices/forecast-for-the-growth-of-the-e-sports-market.md)
{% endcontent-ref %}

{% content-ref url="/pages/VvG0BN2ajf8B46aAiCNt" %}
[Team and Partners](/appendices/team-and-partners.md)
{% endcontent-ref %}


---

# 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://wp.jannavi.net/appendices.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.