> For the complete documentation index, see [llms.txt](https://tonify-1.gitbook.io/tonify-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tonify-1.gitbook.io/tonify-docs/ru/simulyacii/sim1.md).

# sim1 — сколько стоит слушатель

Сколько стоит слушатель — цена механизмов выплат против контракта с лейблом.

**Вопрос.** Сколько приносит артисту слушатель при каждом механизме выплат и как это соотносится с тем, что забирает контракт?

**Ворота.** Синтетический мир обязан воспроизвести три независимо измеренных якоря до того, как напечатан хоть один вывод: доля артистов ниже 1000 стримов в год, доля выше верхнего порога и доля всех стримов у верхушки. Прогон, промахнувшийся мимо, завершается ненулевым кодом.

**Главное число.** Ось правила двигает жизнеспособность артиста ×1.34 при базовом кошельке. Ось контракта — ×14.8. Индустрия спорит про первое число.

**Запуск.** `python3 sim1/tonify_cash_sim.py`, затем `v04_full.py`, `v05_matrix.py`, `v06_uc_crossover.py`.

***

Спецификация, ворота и красная команда: [sim1/SPEC.md](https://github.com/ProximaCA/tonify-sims/blob/main/sim1/SPEC.md), [paper/PAPER.md](https://github.com/ProximaCA/tonify-sims/blob/main/paper/PAPER.md), [paper/CRITIC.ru.md](https://github.com/ProximaCA/tonify-sims/blob/main/paper/CRITIC.ru.md).

![MVA](https://raw.githubusercontent.com/ProximaCA/tonify-sims/main/figures/fig1_mva.png)


---

# 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://tonify-1.gitbook.io/tonify-docs/ru/simulyacii/sim1.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.
