> For the complete documentation index, see [llms.txt](https://docs.charterfnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charterfnd.com/charter-basics/participation-requirements.md). # Participation Requirements Charter is designed for a select number of serious token launches per year. Projects are admitted to Charter based on readiness, quality, and alignment with the Charter framework. To protect the quality of each launch, Charter facilitates no more than two token launches per calendar month. This ensures that Chartered launches do not compete for the same market attention, liquidity, or partner bandwidth. This selectivity is intentional. It allows Charter to dedicate meaningful attention to each project at the moments that matter most, from preparation through launch and release. It also ensures that builders are not launching into a crowded window where their project is one of several competing for the same audience and capital. #### Who Is Charter for? Charter is designed for: * Founders launching digital asset projects, * Teams introducing tokens into existing products, * Builders seeking a structured and compliant launch pathway, * Projects that value long-term credibility and institutional alignment. Charter is not intended for: * Hobbyists, * Memecoins, * Anonymous launches, * Experimental or unstructured token deployments. --- # 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.charterfnd.com/charter-basics/participation-requirements.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.