> For the complete documentation index, see [llms.txt](https://docs.symm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symm.io/liquidity-provider-documentation/building-a-solver-on-symmio/solver-flow-summary-example.md).

# Solver Flow Summary Example

## Detect Intent

The Event Poller sees a user’s limit Intent for BTCUSDT at price X. This event is queued into the Position Manager.

## Decision & Lock

The Position Manager checks risk policy: “Is the price acceptable? Do we have enough allocated balance with the user? Are we whitelisted?” If yes, requests Web3 Agent to call `allocateAndLockQuote()`.

## Broker Hedge

Simultaneously, the Position Manager instructs the Broker-Order Maker: “Place a limit order on Binance at price X for the same quantity.” The Broker-Order Monitoring module watches for partial fills or a fill event from the exchange.

## Open Position On-Chain

Once the broker fill is confirmed (full or partial), the Position Manager calls `openPosition()`. 

## User Closing

At some point, PartyA requests a limit close. The Position Manager again places a corresponding close order on Binance. When the broker fill is confirmed, the Hedger calls fillCloseRequest() on-chain. The position is fully closed on both the broker and SYMMIO sides.

## Auditor (Optional)

A Position Validator confirms the final state matches: “Broker: no open position, Hedger DB: position closed, On-chain: position closed.” Monitoring & Developer Alerts remain watchful in case any mismatch arises (e.g., on-chain position open but broker order canceled, etc.).

<figure><img src="/files/YITk7gSfTnVTjy4DvJSf" alt=""><figcaption><p><strong>Recommended Architecture for the Hedger</strong><br><strong>Green objects</strong> codes will be open sourced and provided by the SYMMIO team (ETA Nov/Dec 2023)<br><strong>Red objects</strong> should be developed by the MarketMaker.<br><strong>Purple objects</strong> are optional.</p></figcaption></figure>


---

# 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.symm.io/liquidity-provider-documentation/building-a-solver-on-symmio/solver-flow-summary-example.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.