> 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-ceo.md).

# BROKE CEO

## The CEO of Absolutely Nothing

> Billion-dollar dreams. Zero-dollar balance. Infinite confidence.

<figure><img src="https://3912587727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaCkwEOotyUZP6FOZ4a0Y%2Fuploads%2FpiDRBYRZXXj46nIOnEp2%2Fceo%20withepaper%201.png?alt=media&amp;token=fc1c320c-4428-403a-9761-f7c38dbb9f81" alt=""><figcaption></figcaption></figure>

BROKE CEO is a community-driven meme project built around a simple idea: **being broke doesn't mean you stop building.**

What begins with **$CBROKE** is designed to evolve into a larger ecosystem connecting community participation, BROKE Points, a future BROKE Store, NFTs, collaborations, and an evolving digital universe.

The long-term journey is built around:

**BROKE → RICH → BOX → COMPANY**

The project is being developed step by step, with the community playing a role throughout the journey.

> **You don't have to be rich to join the board.**

## A living document

This Whitepaper describes the current direction of BROKE CEO. Some features, dates, mechanics, products, and utilities are planned and may evolve as development continues.

Where something has not been finalized, it is marked as **planned**, **potential**, or **TBA** rather than presented as a confirmed feature.


---

# 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-ceo.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.