# Reporting Structure

Each strategy periodically generates a *valuation packet* containing:

* Underlying asset balances.
* Liquidity positions, derivative exposures, or auxiliary assets.
* Accumulated rewards and unharvested yield.
* Realized and unrealized profit and loss since the previous report.
* Strategy health indicators and operational status flags.
* Timestamp or execution identifier for ordering and reconciliation.

Valuation packets are forwarded through execution-environment-specific relays into the zkSync oracle module for validation and reconciliation.

Reporting frequency may vary across execution environments based on their operational characteristics, including:

* Deterministic or block-aligned reporting.
* Event-driven or execution-cycle-based reporting.
* Time-based batching or aggregation.

Despite differences in reporting cadence and execution timing, all valuation packets undergo a uniform validation and reconciliation process prior to any impact on vault accounting or 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/oracle-architecture/reporting-structure.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.