> For the complete documentation index, see [llms.txt](https://rico-matrix.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rico-matrix.gitbook.io/whitepaper/token-utility-flywheel.md).

# 🔄 Token Utility Flywheel

### <mark style="color:$primary;">The Loop</mark>

1. ✍️ More authors join
2. 📚 More books are listed
3. 🔥 More RICO is burned through publishing
4. 👥 More users buy content
5. 🔥 More RICO is burned through purchases
6. 🌐 More community engagement leads to more curation activity
7. 🔥 More voting can burn more RICO
8. 💰 More holders stake RICO
9. 🔒 Liquid supply can tighten
10. ⚠️ Early exits trigger burn + redistribution
11. 💎 Long-term holders become more aligned with ecosystem growth

### <mark style="color:$primary;">Why this matters</mark>

This flywheel means RICO is not relying on only one source of value reinforcement.

Instead, multiple ecosystem actions can work together:

* usage
* curation
* scarcity
* retention
* and staking

### <mark style="color:$primary;">Strategic Takeaway</mark>

> 🚀 Growth feeds utility.\
> 🔥 Utility feeds burn pressure and demand relevance.\
> 🔒 Staking supports retention and supply lock.\
> 💎 Long-term alignment becomes stronger over time.

<mark style="color:$success;">Next: 🔥 Deflation Model</mark>


---

# 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://rico-matrix.gitbook.io/whitepaper/token-utility-flywheel.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.