> For the complete documentation index, see [llms.txt](https://docs.yodl.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yodl.fi/capital-access-and-protection/reputation-framework/operator-reputation.md).

# Operator Reputation

#### **Overview**

Every Operator begins with a Reputation Multiplier (RM) of **1.00** upon whitelisting. This value is stored on-chain and updated automatically after each epoch based on verifiable performance metrics.\
The RM acts as a dynamic trust coefficient, scaling the Operator’s **execution-credit ceiling.** 

Governance defines a global RM range of **0.50 ≤ RM ≤ 1.50**, ensuring no Operator can gain or lose influence excessively within a single epoch.

#### **Epoch Update Logic**

Positive behavior increases RM toward the upper bound; failures or restoration events decrease it proportionally.

#### Positive Reputation Factors

| **No Liquidation or Slashing Events** | Maintains solvency throughout epoch                   | +0.1  |
| ------------------------------------- | ----------------------------------------------------- | ----- |
| **Exceptional Execution Efficiency**  | Generated surplus ≥ 5 bps on YODL Delegated USD Value | +0.01 |

Maximum positive adjustment per epoch: +0.11.

#### Negative Reputation Factors

| **Bounded Liquidation Event**     | Triggered when HF ≤ 1.0                                  | −0.05                          |
| --------------------------------- | -------------------------------------------------------- | ------------------------------ |
| **Non-Repayment of Vault Assets** | Fails to restore by epoch end                            | −0.10 and temporary suspension |
| Restoration Reserve Usage         | Slashing sourced from the protocol’s restoration reserve | −0.20                          |

Maximum negative adjustment per epoch: −0.35.

#### **Blacklisting & Recovery**

* **Auto-Blacklist:**
  * `RM = 0.50` 
* **Re-Whitelisting:**
  * Requires governance approval and audit of prior epoch data (off-chain).
  * Upon reinstatement, RM resets to 0.90 (probationary).

#### On-Chain Enforcement  

• Update Frequency: Each time a relevant event occurs (liquidation, repayment, surplus).\
• Data Sources: Aggregated Orchestrator data.\
• Transparency: All RM adjustments and reasons are emitted on-chain for verifiability.

#### Governance Controls  

Governance may:\
• Define minimum and maximum RM bounds\
• Tune per-event reputation adjustments\
• Pause RM updates during system-wide incidents


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yodl.fi/capital-access-and-protection/reputation-framework/operator-reputation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.