> 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/vision-and-ecosystem.md). # Vision & Ecosystem BROKE CEO is designed as a connected ecosystem that grows in stages. The intended progression is: **BROKE POINTS → BROKE STORE → $CBROKE → BROKE CEO NFT → BROKE → RICH → BOX → COMPANY NFT → BROKE CEO ECOSYSTEM** The community journey begins before the token launch, with BROKE Points, the BROKE Board, leaderboard, missions, and the BROKE Store planned to become active first. ## The Ecosystem Layers ### 01 — BROKE POINTS The community participation layer. BROKE Points are planned for supporters who complete activities such as X and Discord participation, daily check-ins, likes, reposts, comments, missions, events, and collaborations. The BROKE Board and leaderboard are planned to be active before the $CBROKE launch. **BROKE Points are for brokes. 😂** ### 02 — BROKE STORE The first ecosystem destination. The BROKE Store is planned to become active before the $CBROKE launch. Supporters may use BROKE Points for selected rewards, items, access, and opportunities. After launch, $CBROKE may become an additional payment and participation route. The BROKE CEO NFT is planned to have utility inside the Store, while future Box assets or items may also become usable or tradable through the Store. **Too broke to buy it? Earn it. 😂** ### 03 — $CBROKE The planned ecosystem token. $CBROKE is intended to become a core participation and utility layer as the ecosystem develops. Specific token mechanics, utilities, burns, treasury interactions, and other requirements will be announced when finalized. ### 04 — BROKE CEO NFT The first collectible stage. The BROKE CEO NFT collection is planned after the $CBROKE launch and BROKE Store stage. The NFT is intended to have utility inside the BROKE Store and may later participate in the evolution system. ### 05 — BROKE → RICH The evolution stage. Eligible BROKE NFTs may be designed to evolve into RICH through future mechanics. Potential mechanics may include NFT upgrades, $CBROKE use, burns, treasury interactions, or other requirements. Exact eligibility and mechanics will be announced before implementation. ### 06 — BOX The bridge stage. The Box Collection is planned to connect the NFT evolution system with the broader Company ecosystem. Boxes may contain assets, items, components, access elements, or other collectibles. Some future Box assets or items may become usable or tradable through the BROKE Store. Exact contents and mechanics remain TBA. ### 07 — COMPANY NFT The Company stage. The Company NFT Collection is planned as a major ecosystem milestone. Eligible Box assets may connect or integrate with the Company stage, creating a more connected BROKE CEO universe. ### 08 — BROKE CEO ECOSYSTEM The connected universe. The long-term goal is to connect BROKE Points, the BROKE Store, $CBROKE, NFTs, evolution mechanics, Boxes, Company NFTs, treasury systems, collaborations, and future community-driven mechanics into one evolving BROKE CEO ecosystem. **BROKE POINTS → STORE → $CBROKE → NFT → RICH → BOX → COMPANY → ECOSYSTEM** The roadmap represents the current development direction. Dates, mechanics, and features may evolve as development continues. --- # 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/vision-and-ecosystem.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.