# Cross-Domain Constraint Model

```sql
                 Execution Environments
        +----------------+----------------+----------------+
        |  Environment A |  Environment B |  Environment C |
        +----------------+----------------+----------------+
                 |             |               |
                 |     Raw Reports (Untrusted)  |
                 +-------------+---------------+
                               |
                     zkSync Oracle Layer
                         Validation
                               |
                 Valid?       |       Invalid?
                   |          |          |
                   v          |          v
           Enter NAV (Trusted) |   Excluded from NAV
                               |
                               v
                        zkSync Home Vault
              (ERC-4626 Accounting, Supply, NAV)

```

### Summary

Cross-domain invariants make Multistake’s multi-environment architecture safely composable. They ensure that:

* Accounting remains authoritative and deterministic.
* Execution-environment failures cannot propagate into vault state.
* No unvalidated external state is trusted.
* NAV cannot inflate or drift due to asynchronous execution or delayed settlement.
* Users experience predictable ERC-4626 semantics under all conditions.
* Solvency is preserved across all failure and recovery scenarios.

These invariants form the foundation that enables Multistake to unify heterogeneous execution environments into a single coherent, trust-minimized yield engine anchored by zkSync as the canonical settlement layer.


---

# 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/cross-domain-invariants/cross-domain-constraint-model.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.