> For the complete documentation index, see [llms.txt](https://mevcapital.gitbook.io/vaults-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mevcapital.gitbook.io/vaults-protocol/methodology-and-curation-2.md).

# Methodology & Curation

MEV Capital’s curation process for Strategy Vaults is grounded in rigorous thesis validation, operational feasibility testing, and risk stress-testing.

**1. Market Thesis Validation** Each vault is launched only after:

* Backtested simulations on historical data
* Projected APY analysis under multiple scenarios
* Evaluation of sustainability of underlying incentives

**2. Protocol Stack Review** Protocols involved in the vault are assessed for:

* Audit coverage and exploit history
* Oracle models and price feed integrity
* Governance friction and upgradeability

**3. Execution Risk Modeling** MEV Capital reviews all executable legs of a strategy to model potential slippage, failed execution costs, and dependency on MEV-sensitive flows.

**4. Position Monitoring & Intervention Framework** Live telemetry tracks:

* PnL on a per-leg and per-strategy basis
* Collateral health ratios (where relevant)
* Strategy drift from original design assumptions

Vaults are rebalanced or unwound automatically or manually depending on deviation thresholds.


---

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

```
GET https://mevcapital.gitbook.io/vaults-protocol/methodology-and-curation-2.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.