> For the complete documentation index, see [llms.txt](https://docs.kampeni.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kampeni.com/gameplay/overview.md).

# Overview

Kampeni is ecosystem for telling stories through digital games. Kampeni's "meta-game has nine layers:

1. **Meta Game -** This is the broader ecosystem or the "base layer" of Kampeni. The meta game are the base rules for how the other 8 layers of the game ecosystem work together. 
2. **Character Layer -** This is the where players can purchase, trade, organize, and develop collectable game characters - which are NFTs. 
3. **Organizations Layer -** This is where players leverage their characters to build, manage, and monetize in game organizations ("Orders") to build influence in and out of the game. 
4. **Political Economy Layer -** This is where players leverage their collection of characters and participation in Orders to build wealth and power by leveraging and manipulating the game's political economy.
5. **Playable Games Layer -** This is where the players use their characters to engage in traditional video games. To ensure the game lore can rapidly advance  the first games will be shorter, distinct, lightweight games that can quickly advance the storyline and allow us to offer unique experiences that take advantage of the different traits 
6. **Lore Layer -** This is where players engage in storytelling 
7. **DeFi Layer -**
8. **Publishing Layer -**
9. **Governance Layer -**

Players may "play" or participate by engaging in one or all of these layers. These layers are the ones built by design, however others may be developed organically by the community.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.kampeni.com/gameplay/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.