# Unwind Semantics

Unwinds occur under three conditions:

1. **Withdrawal-driven liquidity needs**\
   The withdrawal queue requires liquidity that must be retrieved from strategies.
2. **Rebalancing operations**\
   Capital must shift between strategies or execution planes.
3. **Emergency or pause triggers**\
   Strategies enter forced wind-down due to risk event or oracle inconsistency.

Unwinds follow deterministic rules:

* A strategy cannot return more than its validated value.
* Bridge delay does not affect safety—only availability.
* Shares are not burned until liquidity reaches zkSync.

This protects the vault from mismatches between expected and delivered liquidity.


---

# 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://multistake-1.gitbook.io/multistake-docs/documentation/strategy-layer/unwind-semantics.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.