> 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/vault-curator-reputation.md).

# Vault Curator Reputation

Curator reputation reflects consistency, scale, and commitment of capital participation.\
It rewards predictable behavior (pre-commitment, steady capital allocation) and penalizes early withdrawals or inactive epochs.

Every Curator begins with **RMC = 1.00** upon registration.\
This value evolves automatically after each epoch based on off-chain computation of on-chain actions recorded through the Approver, VaultRouter, and FeeManager contracts.

Governance defines a global range of **0.50 ≤ RMC ≤ 1.50**, ensuring stability and avoiding volatility in capital-routing logic.

#### Reputation Drivers

| Parameter                    | Description                                                                       | Measurement Basis                              | Weight / Impact                      |
| ---------------------------- | --------------------------------------------------------------------------------- | ---------------------------------------------- | ------------------------------------ |
| Pre-Commitment Ratio         | Share of total capital the Curator locks in advance via the Pre-Commitment Vault. | (Pre-Committed Value ÷ Total Curator Deposits) | ↑ increases RMC up to +0.10          |
| Allocation Depth             | Amount of allocated capital across active Operators relative to vault balance.    | (Allocated Value ÷ Vault Balance)              | ↑ increases RMC up to +0.08          |
| Allocation Persistence       | Continuous capital participation across epochs without withdrawal interruptions.  | Active Epochs ÷ Total Epochs                   | ↑ increases RMC up to +0.05          |
| Early Unallocation (Penalty) | Removing allocated capital before epoch end or cool-off completion.               | Count per epoch                                | ↓ decreases RMC −0.20 per event      |
| Zero-Participation Epochs    | Epochs with no active capital allocation.                                         | Epoch count                                    | ↓ decreases RMC −0.05 per idle epoch |

### Governance Controls  

#### Governance may:

* Adjust global RMC bounds and per-event weights.
* Approve or replace the off-chain Reputation Engine.
* Pause or override RMC updates during system-wide incidents.
* Integrate cross-protocol metrics (e.g., Symbiotic vault metadata).


---

# 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/vault-curator-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.