> For the complete documentation index, see [llms.txt](https://www.size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.size.club/docs/tutorials/read-your-game.md).

# How to read your game

Follow the five key parts of the Size terminal: P\&L, score, rank, stage objective, and countdown.

The terminal shows several numbers that serve different purposes. Use them together to understand what is happening in the game.

| Watch           | What it tells you                          | What to remember                                 |
| --------------- | ------------------------------------------ | ------------------------------------------------ |
| Position P\&L   | How an open virtual trade is performing    | It can change while the position is open         |
| Score           | Your points under the accepted game rules  | It is separate from cash and XP                  |
| Rank            | Where you stand against active competitors | A rising score can still leave you below the cut |
| Boost card      | The active stage objective and progress    | Read its qualification conditions                |
| Stage countdown | How long remains before the next boundary  | Check your rank before the cut                   |

![Terminal showing P\&L, score, rank, boost and the stage countdown](https://922876858-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdAGEvfYCv46sFERq1DWJ%2Fuploads%2FzmXhQ4bX9waP4t4h8jSL%2F02-gameplay-and-boost.jpg?alt=media)

*Illustrative local demonstration. P\&L, score, rank, boost and the countdown describe different parts of the game.*

## Before the next cut

Check the countdown and leaderboard together. In the documented standard format, the lowest-ranked active competitor is eliminated at each stage end. If you are eliminated, the run ends.

## At the finish

Read the final report rather than using the size of a single profitable trade to judge the outcome. Surviving alone does not guarantee a prize. [Game rules](https://www.size.club/docs/gameplay/game-rules) explains the result conditions.

## Want the exact scoring calculation?

Use [Score](https://www.size.club/docs/gameplay/score) and [Boosts and rewards](https://www.size.club/docs/gameplay/boosts-and-rewards) as the detailed reference. This walkthrough does not replace the accepted rules for your game.

[Start your first free game](https://www.size.club/docs/start/first-game).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.size.club/docs/tutorials/read-your-game.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.