> 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/measurement/cadence.md).

# Payment cadence

The payment-cadence slot — a Telegram pilot of ≥200 rows, or the range stays open.

**The question.** How often does a devoted fan actually pay, on Telegram, in music — not on Twitch, not on Patreon, not in Tencent gifting.

**The rule.** Without ≥200 rows in `data/pilot_payments.csv` the status is UNMEASURED and the 0.38–1.25–6.31 range stays open. Adjacent-industry k=12 is colour, not a closer. The script will not invent payments.

**Run it.** `python3 emp2/cadence_measure.py`

***

Replaces Twitch/Patreon/Tencent as a closer of the sim1 breakeven range 0.38–1.25–6.31. Fail-closed: without ≥200 rows the status is UNMEASURED and the range stays open. The script will not invent payments and will not substitute k=12.

```
python3 emp2/cadence_measure.py
```

CSV: `data/pilot_payments.csv` (not in git). Header in `data/pilot_payments.example.csv`:

```
ts,user_id,artist_id,amount_usd,is_recurring
```

Spec: [SPEC.md](https://github.com/ProximaCA/tonify-sims/blob/main/emp2/SPEC.md). Status written to `emp2/STATUS.json` on every run. `sim5/glue.py` reads the same loader: measured k/check in, otherwise the open range — never Twitch.


---

# 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/measurement/cadence.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.
