# Routing Logic Routing logic determines where new capital is deployed. It accounts for: * target weights per strategy * plane-level exposure caps * risk-class weighting * constraints on minimum idle liquidity in the zkSync vault * per-plane execution suitability (latency vs. throughput vs. stability) Routing uses a deterministic planner that computes the intended allocation state, then issues execution messages that cause strategies on the respective planes to deploy capital. The routing does **not** assume that execution is instantaneous. It expects asynchronous delivery, and only updates accounting once finality and validation occur. --- # 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/rebalancing-and-routing/routing-logic.md?ask= ``` 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.