# Plane Overview

Multistake operates across distinct execution planes. Each plane provides execution guarantees that materially impact the performance, responsiveness, and safety of different strategy classes. The execution layer is deliberately decoupled from the vault’s accounting so that strategies can benefit from heterogeneous execution environments without compromising determinism or solvency.

The purpose of this section is to define the role, properties, and operational constraints of each execution plane. These are not interchangeable environments; each is optimized for specific strategy types, latency requirements, and state-access patterns. Multistake assigns strategies to planes based on their computational needs and market-interaction profile.

The execution planes differ along four axes:

1. **Latency model**: block speed or micro-block responsiveness.
2. **Throughput model**: single-threaded vs. parallelized state transitions.
3. **Pricing and gas characteristics**: fee structure and composability cost.
4. **Failure and recovery behavior**: how the plane behaves during congestion, stalls, or external protocol failures.

The zkSync vault treats each plane as an external module. Strategies running on different planes cannot influence one another directly; their only interaction occurs through validated reporting that feeds into NAV.


---

# Agent Instructions: 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:

```
GET https://multistake-1.gitbook.io/multistake-docs/documentation/execution-planes-zksync-monad-megaeth/plane-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.