> For the complete documentation index, see [llms.txt](https://clarity-7.gitbook.io/clarity-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clarity-7.gitbook.io/clarity-docs/clarity-moniversive-invariant-static-mis/architecture-static-ml/cross-shard-state-bounds-746-760.md).

# Cross-shard bounds 746–760

> Generated 2026-07-29T03:15:30Z · module `languages/mis-ml/surfaces/CrossShardStateBounds.clrty`

Protocol invariants for multi-shard execution on **clrty-1 / 1202** — aggregated roots, divergence guards, cross-shard receipts, fee routing, and global solvency.

| n   | id      | Name                         | Definition                                                                                   |
| --- | ------- | ---------------------------- | -------------------------------------------------------------------------------------------- |
| 746 | sml-746 | `CrossShardStateRoot`        | Aggregated 256-bit Merkle root committing multi-shard execution state into primary consensus |
| 747 | sml-747 | `ShardStateDivergenceGuard`  | Halt cross-shard transfers if state roots diverge across shard sub-committees                |
| 748 | sml-748 | `AtomicCrossShardReceipt`    | Proof verifying asset burn on source shard before mint on target shard                       |
| 749 | sml-749 | `CrossShardLatencyCap`       | Max 10ms latency budget for resolving cross-shard state messages                             |
| 750 | sml-750 | `ShardCapacityBalancer`      | Dynamic routing shifting active accounts across shards to equalize compute load              |
| 751 | sml-751 | `CrossShardGossipTopic`      | P2P topic dedicated to high-speed inter-shard state synchronization                          |
| 752 | sml-752 | `ShardValidatorQuorum`       | >=66.7% of sub-committee validators must sign cross-shard state receipts                     |
| 753 | sml-753 | `CrossShardInferenceRelay`   | Relay pipeline for static ML inference spanning split feature data across shards             |
| 754 | sml-754 | `GlobalStateTreeAccumulator` | Rolling Merkle tree binding all shard states into one unified root digest                    |
| 755 | sml-755 | `CrossShardFeeRouting`       | Split cross-shard gas revenues across processing committees in real time                     |
| 756 | sml-756 | `ShardStateRollbackTrap`     | Unwind cross-shard transfers if finality fails on destination shards                         |
| 757 | sml-757 | `CrossShardGasPriceFloor`    | Baseline execution price threshold across all cross-shard messaging channels                 |
| 758 | sml-758 | `ShardSyncTimeout`           | Max 1 slot for shard committee to broadcast state attestations                               |
| 759 | sml-759 | `CrossShardCollateralEscrow` | Vault locking collateral on source shard during pending cross-shard token swaps              |
| 760 | sml-760 | `GlobalSolvencyCrossCheck`   | Multi-shard check: total global supply equals sum of shard balances                          |

```bash
bin/misc languages/mis-ml/surfaces/CrossShardStateBounds.clrty --check --compact-letters
```


---

# 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://clarity-7.gitbook.io/clarity-docs/clarity-moniversive-invariant-static-mis/architecture-static-ml/cross-shard-state-bounds-746-760.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.