> For the complete documentation index, see [llms.txt](https://reflection-or-injection.gitbook.io/rein-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reflection-or-injection.gitbook.io/rein-docs/why-the-empty-side-pays-more.md).

# Why the empty side pays more

This is the mechanic that makes REIN a game rather than a savings account.

The pot is split among everyone on Injection. Ten people share it ten ways. A hundred people share it a hundred ways. So the fewer people are there, the more each one gets.

Which sets up the real decision, three times a day:

* Stay on the crowded side, where you are likely to win but the win is small
* Move to the thin side, where you might get nothing for a while and then take a pot that has been filling the whole time

Nobody controls this. It is the sum of what everyone else decides, and it shifts every round. The standing you see on the dashboard is everyone's answer to that question, right now.

{% hint style="warning" icon="circle-info" %}
The winning move is not always the obvious one. Sometimes the obvious move is exactly why the other side is about to pay.
{% endhint %}


---

# 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://reflection-or-injection.gitbook.io/rein-docs/why-the-empty-side-pays-more.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.