> For the complete documentation index, see [llms.txt](https://docs.kampeni.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kampeni.com/introduction/roadmap.md). # Roadmap **Q4 2022** * Public Announcement of Kampeni * Initiate Community Development * Complete Artwork for NFT * Complete White Paper * Complete and Externalize Political Economy Design Document **Q1 2023** * Release of Game Token * Completion of DAOs * Gameplay Video **Q2 2023** * NFT Chapter 1 Launch **Q3 2023** * Release Beta of the TTRPG Rulebook * Release the Political Economy Rulebook * Launch NFT Staking **Q4 2023** * Introduce Storytelling Rewards and Content Bounties * Beta Test Governance Meta Game **2024 and Beyond** Items listed here are on our product roadmap but have too many dependencies for is to reliably predict when we will ship. We are listing these deliverables to communicate our vision. We will ship them as soon as possible. * Release of Lore Book Enabling TTRPG Play * Incentivize Distributed Storytelling * Introduce In-Game Taxation Model * Release of Legendary Characters * Integrate TTRPG Progress into Meta Game * Decentralization Roadmap * Native "House Ads" - We Will Always Source the Ads and Never Rely on Personal Information for Ad Serving * Integration of other CC0 Solana Projects * Kampeni Integrated Dashboard --- # 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://docs.kampeni.com/introduction/roadmap.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.