> For the complete documentation index, see [llms.txt](https://zkcross-network-1.gitbook.io/learn.zkcross.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zkcross-network-1.gitbook.io/learn.zkcross.network/security-and-control/monitoring-reconciliation-and-verification.md).

# Monitoring, Reconciliation, and Verification

zkCross treats monitoring as part of security, not just operations.

Every execution run creates a structured trail that can be reviewed later. This includes:

* observations and state inputs
* the proposed intent
* validation results
* the execution path used
* transactions and receipts
* post-execution checks
* reconciliation outcomes

After execution, zkCross verifies that resulting balances, position changes and accounting states remain inside expected bounds.

Monitoring continues after settlement. The system tracks venue health, oracle drift, liquidity changes, anomaly signals and risk triggers over time.

This is what makes zkCross operationally reviewable and suitable for systems where capital cannot be treated casually.


---

# 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://zkcross-network-1.gitbook.io/learn.zkcross.network/security-and-control/monitoring-reconciliation-and-verification.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.