> For the complete documentation index, see [llms.txt](https://cellular-automata.gitbook.io/cellular-automata-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cellular-automata.gitbook.io/cellular-automata-documentation/readme-1/core-mechanics.md).

# Core Mechanics

<figure><img src="/files/zmUi0xQCw1EgofrhQfAM" alt=""><figcaption></figcaption></figure>

#### Pattern Creation

* Users access the platform and design patterns using a grid-based interface.
* Patterns evolve according to Cellular Automata rules, which simulate life-like behaviors over discrete time steps.

#### 2. Token Spending

* To generate patterns, users spend **$CA tokens**:
  * **90%** of the spent tokens are **burned**, reducing the overall supply and increasing token value.
  * **10%** of the spent tokens are added to a **rewards pool**.

#### 3. Leaderboard System

* Patterns are evaluated based on:
  * **Efficiency**: How well they evolve over time.
  * **Longevity**: Survival across numerous cycles.
  * **Innovation**: Unique or novel designs.
* Top-ranked patterns appear on global leaderboards, showcasing user creativity and skill.

#### 4. Rewards

* Patterns that survive **1 million cycles** are rewarded with **10,000,000 $CA tokens**.
* Additional rewards are distributed periodically to top performers on the leaderboard.


---

# 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://cellular-automata.gitbook.io/cellular-automata-documentation/readme-1/core-mechanics.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.