> 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/introduction/project-overview.md). # Project Overview The JAN-Navi platform continues to evolve and expand, enhancing both the traditional and digital Mahjong experience across the globe. This section outlines the key components of JAN-Navi's strategic development: the JAN-Navi Platform, JN Token, and DePIN Mahjong Big Data. * **JAN-Navi Platform**\ JAN-Navi, known for its solid operational track record, acts as a gateway to the global Mahjong community. The platform is expanding its reach by establishing online storefronts for physical Mahjong parlors and extending its influence globally. In addition to these expansions, JAN-Navi is also offered as a white-label solution, allowing it to be integrated into various games, enhancing its capabilities as a matching platform and communication tool. * **JN Token**\ The JN Token plays a crucial role in the development of Mahjong e-sports and the reinforcement of the JAN-Navi ecosystem. It provides token holders with decentralized sponsorship opportunities for e-sports events, along with other utilities including game revenue sharing, participation in the Jan-Navi DAO, and tipping features. These utilities enhance engagement within the platform and promote active user involvement. * **DePIN Mahjong Big Data**\ The DePIN initiative integrates online and offline Mahjong player data on the blockchain to create a true global Mahjong community. By merging online behaviors with offline match data, it facilitates the development of new marketing strategies and revenue models. --- # 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://wp.jannavi.net/introduction/project-overview.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.