> 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/core-infrastructure/execution-architecture.md).

# Execution Architecture

zkCross Network is an execution infrastructure layer designed to move value across chains safely, with deterministic control over what can happen at every step.

The architecture is built around one key principle: planning and execution must be separated.

A planner, strategy engine, or AI system can propose actions. That does not give it authority. Authority comes only from the execution system, which validates actions against rules, signing constraints and post-settlement checks.

### The execution lifecycle

<figure><img src="/files/spSr1m9bEVFAn1d7lgBk" alt=""><figcaption></figcaption></figure>

zkCross follows a structured execution lifecycle:

{% stepper %}
{% step %}

### Observe

The system reads balances, positions, venue state, price references and network conditions.
{% endstep %}

{% step %}

### Purpose

An action is represented as an intent with defined parameters, allowed destinations, bounds and expiry.
{% endstep %}

{% step %}

### Validate

The intent is checked against deterministic rules, policy boundaries, simulation expectations and permission constraints.
{% endstep %}

{% step %}

### Execute

If valid, the router builds the execution bundle, adapters normalise the action for the target chain or venue and the signing path authorises only the scoped action.
{% endstep %}

{% step %}

### Verify

After execution, zkCross collects receipts, compares expected and actual outcomes, reconciles accounting and re-evaluates invariants.
{% endstep %}

{% step %}

### Record and monitor

The run is logged in a structured trail that includes observations, intent, checks, transactions, receipts and post-execution verification. Monitoring continues after settlement.
{% endstep %}
{% endstepper %}

### Vault and custody model

<figure><img src="/files/AjI9u5kmgejLNSV4042W" alt=""><figcaption></figcaption></figure>

Funds remain inside user-owned vault contracts, which form the custody boundary and the execution endpoint.

This matters because zkCross is designed to be non-custodial at the infrastructure layer. The vault is the only approved origin and receiver of value movement. Execution can move funds through approved paths, but it cannot create arbitrary external transfer behaviour outside the defined model.

Core custody properties include:

* The vault is the source and destination of authorised value movement
* Actions must match approved action types and approved destination sets
* Slippage and exposure bounds are enforced at execution time
* Execution paths cannot bypass policy enforcement

This model gives zkCross a clean separation between infrastructure control and user asset ownership.

***


---

# 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/core-infrastructure/execution-architecture.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.