> 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/1.-intent-life-cycle.md).

# 1. Intent Life Cycle

An intent's lifecycle begins with **PartyA** (the trader) initiating a trade request on Symmio by specifying the trade's key parameters. This request, the "intent", is broadcast on-chain through the core contracts. Once posted, it's visible to [**PartyB**](/trader-documentation/glossary-of-terms.md), the hedgers or market makers, who can review and respond.

Hedgers and solvers monitor these on-chain requests with tools like event listeners or subgraphs. They evaluate each intent against their strategy, risk profile, and market conditions. If a hedger decides to proceed, they claim the intent and respond with a transaction on-chain. That transaction signals agreement to the terms, or any modifications they want, such as an adjusted price or collateral requirement.

### PartyA sendQuote flow

* **Create a sub-account** through the [AccountLayer](/contract-documentation/symmio-perps-v0.8.5/account-layer-diamond.md).
* **Deposit and allocate collateral** to the sub-account.
* **Call `sendQuote()`** with the desired parameters. This requires two things:
  * A Muon signature verifying PartyA's ability to open a position and the price of the asset (usually handled by the frontend builder).
  * The transaction encoded via the `_call()` function on the Account Layer contract, which forwards to `sendQuote()` on the Diamond contract.

After being whitelisted as a PartyB by the SYMMIO developers, hedgers can use the Cloverfield interface to send quotes with the `sendQuote` functionality. This lets hedgers verify their service and test their strategies and workflows in real time.

More documentation on sendQuote is available here.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.symm.io/liquidity-provider-documentation/building-a-solver-on-symmio/1.-intent-life-cycle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.