> 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-treasury.md). # BROKE Treasury ## The ecosystem treasury A BROKE Treasury is planned as part of the future ecosystem. The concept is to create a transparent structure that can hold assets acquired for ecosystem use. Potential treasury assets may include: * NFTs * Collaboration assets * Collectibles * Items intended for community rewards * Assets connected to future store releases * Other ecosystem-related assets ## Store connection Assets acquired by the treasury may later be used within the BROKE Store, collaborations, community rewards, or other planned ecosystem mechanics. The exact funding sources, custody structure, wallet addresses, reporting process, and spending rules will be announced before the treasury becomes active. ## Transparency Treasury activity should be communicated publicly where appropriate, including relevant purchases, holdings, and uses. No treasury-related return or profit is guaranteed. --- # 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-treasury.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.