> For the complete documentation index, see [llms.txt](https://crowdcontrol-network.gitbook.io/crowdcontrol-learn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crowdcontrol-network.gitbook.io/crowdcontrol-learn/how-to-play/the-game.md).

# The game

CrowdControl is the first online collectible card game, in which YOU (the player) can not only play the game but also create and sell cards, and shape the development direction of the game. 

This sounds very awesome, but how does it work? Somebody must be in charge and someone has to say what is overpowered? The answer is blockchain. We are building a blockchain with Cosmos technology that incentivizes productive contributions and positive interactions with the game. How this all works can be read in detail in our [Whitepaper](https://github.com/DecentralCardGame/whitepaper/blob/master/whitepaper.pdf).

CrowdControl is also a decentralized autonomous organization (**DAO**). This means that this whole thing is not owned by a huge company squeezing the maximum profit out of the player base. CrowdControl is owned by everyone who has contributed to the project. This means you can also contribute and become not only a player but an owner of the game.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://crowdcontrol-network.gitbook.io/crowdcontrol-learn/how-to-play/the-game.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.