> 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/how-a-round-works.md).
# How a round works
A round is 8 hours long. Rounds run back to back with no gaps, so there are exactly 3 rounds every day.
During a round, nothing is decided. Both sides are simply accumulating weight. You can see the live status on the dashboard at any moment, and it moves as people stake and leave.
When a round ends, the referee checks one thing: which side holds more than half the weight?
* If Reflection has the majority: Reflection is paid and Injection gets nothing
* If Injection has the majority: Injection is paid and Reflection gets nothing
* If it is exactly even: nobody is paid and everything carries over to the next round
Then the next round starts immediately. There is no waiting, no pause, no cooldown between rounds.
{% hint style="warning" %}
There is no partial payout. 51% takes everything, 49% takes nothing. That is the whole point.
{% 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/how-a-round-works.md?ask=&goal=
```
`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.
