> For the complete documentation index, see [llms.txt](https://docs.epiora.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epiora.xyz/review-integrity.md).

# Review Integrity

A transaction review must represent the transaction that is eventually submitted.

Epiora therefore treats review integrity as part of the execution model.

A review can be associated with information such as:

```
wallet
network
market
action
payload
amount
price context
timestamp
```

Material changes invalidate the review.

This includes situations where:

* the wallet changes
* the market changes
* the amount changes
* required live state changes materially
* the reviewed action expires
* the execution payload no longer matches the reviewed payload

The system should request a new review rather than silently transforming the user's authorization into a different action.

## Live-State Revalidation

Markets change continuously.

Balances change.

Positions change.

Prices change.

An order that was correct at review time may no longer represent the same action immediately before signing.

For sensitive execution paths, Epiora therefore performs live-state revalidation before requesting the final signature.

A simple example:

```
User reviews SELL 5 HYPE

Balance at review:
10 HYPE

Before signature:
balance changes materially

Result:
review invalidated
```

Epiora does not silently resize the reviewed order and proceed.

The user is shown the updated state.


---

# 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.epiora.xyz/review-integrity.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.