> For the complete documentation index, see [llms.txt](https://steakhouse.financial/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://steakhouse.financial/docs/risk-management/monitoring/portfolio-monitoring.md).
# Portfolio Monitoring
Steakhouse Financial has made significant investments into developing a proprietary offchain reallocation engine. This engine monitors all underlying markets and automates efficient rebalancing - the process of depositing and withdrawing liquidity from all underlying markets within a Steakhouse vault - leading to higher yields and more consistent depositor access to liquidity.
As a reminder, Morpho markets target 90% utilization, meaning that generally 10% of deposited assets are available to meet immediate withdrawals requests. The standard interest rate model seeks to trigger borrower repayments when utilization is >90% by increasing the interest rate charged; the inverse is true when utilization is <90%.
Early on, Steakhouse realized that each underlying market became a latency competition to extract liquidity during periods of market distress. Our current infrastructure is able to predict when liquidity crunches may occur, monitor when liquidity in an underlying market returns, and outcompete competitors relying on slower (or manual) processes to actually extract that liquidity into our idle markets and meet withdrawal requests from our vault.
In addition, our systems employ a series of automated and manual “killswitches” to avoid deploying into markets where the deposited collateral and/or market is potentially compromised. The triggers include a number of proprietary criteria - such as a deviation between an asset’s “real” price and the price reported by a particular market oracle - and lead to the cessation of deployment into and/or withdrawal from a compromised market.
---
# 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://steakhouse.financial/docs/risk-management/monitoring/portfolio-monitoring.md?ask=&goal=
```
`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.
