# User-Centric Design

{% hint style="success" %}
One key design principle is:

**Time windows are defined relative to each user’s payment action, not relative to the content itself.**
{% endhint %}

* Each time a user tips content, that action receives a maximum 365-day earning lifecycle.
* During these 365 days, the user appears in future supporters’ "senior lists” with different weights over time.

For each junior tip, the 80% prediction pool is split into four layers:

| Senior Layer | Time Range (relative to junior’s tip time)  | Share of 80% | Amount (of X) |
| ------------ | ------------------------------------------- | ------------ | ------------- |
| L1           | Seniors who tipped within the last 24 hours | 40%          | 0.4X          |
| L2           | Seniors who tipped 1–7 days ago             | 30%          | 0.3X          |
| L3           | Seniors who tipped 8–30 days ago            | 20%          | 0.2X          |
| L4           | Seniors who tipped 31–365 days ago          | 10%          | 0.1X          |

Meaning:

* Seniors who tipped during the last 24 hours are considered the most influential to the current spread;
* Seniors who tipped 2–7 days ago represent **short-term** spread;
* Seniors who tipped 8–30 days ago represent **mid-term** spread;
* Seniors who tipped 31–365 days ago enjoy **long-tail** returns.

For any single tip:

* From the moment of tip, the user can receive rewards from future supporters for up to 365 days.
* Over time, their tier naturally shifts from L1 → L2 → L3 → L4 as time passes.
* After 365 days, it no longer participates in new distributions, but the content can still be tipped.

In other words:

* The **work itself** can exist long-term and continue to receive tips;
* What has a lifecycle is **each tipping action**, not the content.


---

# Agent Instructions: 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:

```
GET https://docs.talex.world/talex-as-a-new-content-app/user-centric-design.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.