> 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/the-charter-launch-schedule.md). # The Charter Launch Schedule Token launches do not happen in isolation. When multiple high-quality projects launch within the same window, they compete for the same liquidity, market attention, and partner bandwidth. This is one of the most common and avoidable reasons that otherwise well-structured launches underperform. Charter addresses this through the Charter Launch Schedule. Each builder accepted into Charter is allocated a specific launch date within the schedule. Charter will endeavour to facilitate no more than two launches per calendar month, ensuring that top-tier projects are not crowding around each other and that each launch receives the market conditions and partner focus it deserves. However, it is worth noting that the Launch Schedule is strictly non-binding. Market conditions shift. Dynamics change. A builder may choose to delay their launch to wait for better conditions, or choose to strike while the iron is hot. There is no penalty for launching outside of the scheduled window. The purpose of the schedule is visibility, not enforcement. It gives builders a clear picture of what other high-calibre projects are building and when they plan to launch. This allows teams to make informed decisions about their own timing. This is as much a matter of practicality as it is etiquette: crowded launch windows do not help anyone. If a builder needs to move their launch earlier or later, the Charter Foundation will work with them to find a new slot. If a builder ultimately launches outside the schedule entirely, there is no punishment and no consequence. The schedule exists to serve builders, not to constrain them. --- # 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/the-charter-launch-schedule.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.