> For the complete documentation index, see [llms.txt](https://gmgm-market.gitbook.io/gmgm-market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gmgm-market.gitbook.io/gmgm-market/a-demand-order-with-combinable-intents.md).

# A demand order with combinable intents

Users often have complex operational processes that require many transactions to achieve the desired outcome. The definition of these results can be broken down into conditions Orders. These orders define the user's desired outcome and motivate the solver to find the best way to achieve that requirement order. Support for demand combination orders, such as:

Swap: "What I want is to have asset A, and I'm willing to pay with asset B"

Transfer: "The result I want is to transfer assets from one address to another"

Cross-chain: "The result I want is to transfer assets from the same address on one chain to another"

Combine demand orders: These orders are used to determine what conditions the user is currently having. All conditions can be expressed as requirements. Surrounding the question "Is my order demand fulfilled?" Is the A/B price lower than the market price? The logic of problems can be expressed in terms of demand orders, which can be combined into signatures that delegate the user workflow to the solver. Consider a simple workflow where a user wants to swap from A to B at a lower market price and then back to A from B at a slightly higher market price. The user can combine this intent with two limit exchange demand orders to check if the first limit exchange result has been resolved. Solvers who understand how these composable orders work can monitor and solve them independently. The user only needs to sign once, and the solver must use two transactions to "solve" this workflow.