# Trust rating algorithm

The creation of a trustworthy service is not only related to the ability of users to create content aimed at evaluating places but also to the ability to interact with each other's content.

<figure><img src="/files/RDSno5iIwrJYoMZjLC7i" alt=""><figcaption></figcaption></figure>

The subsystem of evaluation affects the motivation of users to create exclusively honest and high-quality material. To implement this functionality, such user characteristics as activity level, trust rating, and weight in the system are introduced. The user's content directly affects their rating, depending on the reaction of other application participants.

<figure><img src="/files/Q46kI47EraEX6SHHIFRf" alt=""><figcaption></figcaption></figure>

Users, by evaluating content, change its weight in the system and, accordingly, its rating indicator. In turn, the updated post indicators affect the weight and rating of the content creator user.

Moreover, users, by performing targeted actions such as evaluation, creation, etc., change their own level of activity, as shown in the figure. The user's activity level is involved in the formula for calculating the personal trust rating and is an important user characteristic that reflects their involvement in the system.

The structure of interactions, implementing a closed system for calculating weighted coefficients, allows for more accurate rating indicators of the place and thus ensures the necessary level of trust in the system as a whole.


---

# 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://wp.dagama.world/architecture/trust-rating-algorithm.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.