> For the complete documentation index, see [llms.txt](https://broke-ceo.gitbook.io/broke-ceo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broke-ceo.gitbook.io/broke-ceo-docs/broke-points-lifecycle.md). # BROKE Points Lifecycle ## A limited chapter of the ecosystem BROKE Points are planned as a temporary system tied to the development journey of BROKE CEO. The intended lifecycle is: **BROKE Points Begin** → **BROKE Store** → **$CBROKE Launch** → **BROKE CEO NFT** → **BROKE → RICH** → **BOX** → **COMPANY NFT** → **BROKE Points End** ## Why end the points system? BROKE Points are intended to represent the **BROKE era** of the project. The concept is not to create an endless loyalty-points system. The points system is planned to have a defined endpoint when the Company NFT stage is reached. The final rules, closing date, treatment of unused points, and final leaderboard mechanics will be announced before the system ends. ## Final leaderboard The final BROKE Points leaderboard may become part of the project's history and may be used for selected final rewards or recognition, subject to the rules announced for the relevant event. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://broke-ceo.gitbook.io/broke-ceo-docs/broke-points-lifecycle.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.