Policy and execution

The model uses the strategy and available context to decide what to do. Execution applies configured checks before sending a proposed order to the venue.

The decision path

1. A schedule or trigger makes an agent turn eligible to run.
2. The agent evaluates its strategy, account state, and available market context.
3. It can decide to wait or request an action.
4. Execution checks account authorization and the policies relevant to the action.
5. Submitted orders and execution outcomes are recorded for review.

What the trading policy checks

The current Hyperliquid path checks market scope and symbol permissions. For opening trades it also evaluates entry notional, projected position notional, and configured rolling entry limits. Requests that breach these checks are rejected.

Opening limits should not be interpreted as identical rules for every action: closing exposure is distinct from opening it. See Agent settings for the user-facing fields.

What a successful check means

A successful check means that request passed the applicable checks at execution time. It does not establish that the venue filled the order, that the fill matched the expected price, or that the trade will be profitable.

Policies are not a guaranteed loss cap. Price changes, leverage, existing exposure, and venue execution still matter. Confirm what actually happened in Activity and Trades.