> For the complete documentation index, see [llms.txt](https://docs.rakelaunch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rakelaunch.xyz/rake/introduction/why-rake.md). # Why RAKE The protocol scope that RAKE adds around launch exposure, execution, and fee handling. A conventional launchpad can concentrate on deployment. Much of the activity after launch can then remain disconnected from the launch itself. RAKE frames this gap as the difference between the small part of a token lifecycle that is deployment and the larger part that follows. The `10% / 90%` framing is RAKE's way of describing that distinction, not a measured market statistic. ### Launch is the beginning A token launch does not end the process. It begins the activity that follows. That activity can involve accumulated fees, holder visibility, token status, trading, tipping, prediction, and permissionless, trustless operation. When these functions are disconnected, launch becomes an isolated event rather than the entry point to an ongoing system. RAKE connects launch exposure with its ecosystem actions: * Harvesting and fee distribution * Burns, leaderboard visibility, and token activity * Trading actions, tipping, prediction, and other supported actions The later mechanisms have distinct roles. RAKE does not treat them as a replacement for deployment. It connects them to the lifecycle that deployment begins. RAKE is intended to function as an ecosystem, not simply as a launchpad. --- # 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.rakelaunch.xyz/rake/introduction/why-rake.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.