> For the complete documentation index, see [llms.txt](https://whitepaper.opz.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.opz.io/opz-dex-beta/status-and-priority-rules.md).

# Status & Priority Rules

### Status:

At any given time, an order is currently in one of the following states:

* Filled
* Cancelled
* Expired
* Partially Filled
* New
* Rejected
* Suspended (not currently on the order book, for example, parked Stop/Stop Limit)

### Amendments:

After entering an order into the system, you can change the following properties:

* Quantity
* Disclosed Quantity
* Price
* Stop Price
* Expiration Time (GTTs)
* Expiration Date (GTDs)

### Priority Rules:

When matching, the priority order (from highest to lowest) for any given price level is:

* All displayed orders
* Non-displayed parts of Icebergs (via replenishment)
* Fully Hidden Orders
* Pegged Orders

The order is then prioritized according to when it was added to the book or changed. If an order is changed, it loses priority.


---

# 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://whitepaper.opz.io/opz-dex-beta/status-and-priority-rules.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.