> For the complete documentation index, see [llms.txt](https://docs.upshift.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.upshift.finance/upshift-vault-curation/risk-framework-and-emergency.md).

# Risk Framework & Emergency

## Risk Framework and Guardrails

Risk controls are layered; curators should know which constraints are contract-enforced and which are process-enforced.

<table data-header-hidden><thead><tr><th width="141.1015625"></th><th width="432.47265625"></th><th></th></tr></thead><tbody><tr><td><strong>Guardrail</strong></td><td><strong>What it does</strong></td><td><strong>Enforced by</strong></td></tr><tr><td>Non-custodial perimeter</td><td>Neither Upshift nor the curator can move funds to an external EOA; transfers limited to vault ↔ subaccount ↔ whitelisted strategy contracts.</td><td>Smart contract</td></tr><tr><td>Policy engine</td><td>Whitelists the exact protocols, contracts, and functions a curator may call.</td><td>Subaccount layer</td></tr><tr><td>Liquidity buffer</td><td>Configurable % of assets held in-vault for instant redemptions; no forced unwinds.</td><td>Contract + ops</td></tr><tr><td>NAV volatility protection</td><td>Max percentage change per update cycle; mitigates bad oracles, erroneous NAV, and MEV/latency arbitrage.</td><td>Smart contract</td></tr><tr><td>Timelocks</td><td>24h delay on fee changes and withdrawal-period changes; users can exit before changes take effect.</td><td>Smart contract</td></tr><tr><td>Hypernative monitoring</td><td>Automated unwinds on critical alerts.</td><td>Integration</td></tr><tr><td>Emergency functions</td><td>Multisig can instantly pause deposits/withdrawals and pull all strategy funds back into the vault.</td><td>Owner multisig</td></tr></tbody></table>

## Emergency & Unwind

On critical alerts, exploit on a whitelisted venue, oracle failure, depeg the response sequence is:

1. **Automated unwind.** Hypernative may auto-unwind affected DeFi positions on critical alerts.
2. **Curator unwind**. The curator unwinds remaining exposure and returns capital to the subaccount.
3. **Recall**. The operator pulls funds back into the vault with withdrawFromSubaccount.
4. **Lockdown**. The owner multisig can pause deposits/withdrawals (pauseDepositsAndWithdrawals) and, if needed, sweep with emergencyWithdraw to a safe destination.

### Events to monitor

* OnEmergencyWithdraw events
* DepositWithdrawalStatusChanged events (Pause/Resume)
* Hypernative critical alerts on any whitelisted venue


---

# 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.upshift.finance/upshift-vault-curation/risk-framework-and-emergency.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.