> 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/transparency.md).

# Transparency

## Token allocation

The current plan is:

* **0% team allocation**
* **0% private sale**
* **0% VC allocation**
* **No reserved team tokens**

The intention is for the token supply to be available through the public launch.

These are planned launch principles and will be confirmed with the final launch details.

## Community rewards

Community giveaways, rewards, and promotional campaigns are planned to be created or funded by the team without creating a reserved team token allocation.

Specific funding and distribution mechanics will be communicated for each campaign.

## Treasury

Treasury mechanics, addresses, assets, and spending rules will be communicated when the treasury becomes active.

## Development transparency

BROKE CEO is being developed progressively. Features that are not finalized will be clearly identified as planned or TBA.

## Risk

Crypto assets and NFTs can be highly volatile and may result in partial or total loss of funds. Nothing in this Whitepaper is financial, investment, legal, or tax advice.

Participants should make their own decisions and understand the risks before interacting with any token, NFT, wallet, or blockchain transaction.


---

# 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/transparency.md?ask=<question>&goal=<user_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.