One tool contract, every harness, intent in and typed action out

• trading_resolve_market — resolve canonical symbol, asset index, szDecimals, maximum exchange leverage, and market availability. Never hard-code the ETH asset index.
• trading_get_market_snapshot — mark, mid, oracle, funding, open interest, day volume, and BBO with freshness metadata.
• trading_get_market_history — bounded candle history for 1m, 3m, 5m, 15m, and 1h; one response is capped at 500 bars.
• trading_get_order_book — current book and BBO with attached freshness for execution-critical reads.

Freshness thresholds govern execution: stale BBO or account state blocks submission rather than silently degrading.

• trading_get_account_state — account value, margin used, withdrawable, and positions for the master-wallet address.
• trading_get_position — the canonical net ETH position, entry, size, PnL, funding, and margin.
• trading_get_open_orders — currently open orders keyed by canonical identity.

Account state is queried with the user-owned master-wallet address. The Privy-managed execution-wallet address signs actions; it is never used as account identity.

• trading_get_mission — current mission, authority, strategy, watches, and control flags.
• trading_publish_momentum_strategy — publish the structured momentum strategy the harness will operate under.

// Every MomentumStrategyState field the harness authors.
// version and updatedAt are excluded: the server assigns both on
// acceptance, and the accepted version is always expectedVersion + 1.
type PublishMomentumStrategyBody =
  Omit<MomentumStrategyState, "version" | "updatedAt">;

type TradingPublishMomentumStrategyInput = {
  missionId: string;
  expectedVersion: number; // 0 before any publish
  strategy: PublishMomentumStrategyBody;
};

type TradingPublishMomentumStrategyResult =
  | {
      outcome: "accepted";
      strategy: MomentumStrategyState;
      strategyVersion: number;
      supersededWatchIds: string[];
    }
  | {
      outcome: "rejected";
      reason: "stale_strategy_version" | "mission_not_active";
      currentVersion: number; // so the harness can retry
    };

• trading_register_watch — register a simple typed predicate: price_cross, candle_close, order_update, position_update, or scheduled_reassessment.
• trading_schedule_reassessment — schedule a future harness wake-up at a specific time.
• trading_list_watches — list active, triggered, consumed, cancelled, expired, and superseded watches.
• trading_cancel_watch — cancel an active watch before it fires.

Watches are bound to a strategy version and remain simple, deterministic, typed, and inspectable. Complex interpretation stays a harness responsibility.

• trading_preview_order — produce a normalized, authority-checked preview with precision, fees, and risk reservation before signing.
• trading_open_or_increase_position — open or scale into the canonical ETH position with mandatory stop information.
• trading_place_entry_order — place a resting or marketable entry order.
• trading_modify_order — modify a mission-owned order.
• trading_cancel_order — cancel a mission-owned order.
• trading_replace_protection — place or replace reduce-only stop and take-profit protection for the canonical position.
• trading_reduce_position — reduce the canonical position via a reduce-only marketable IOC order.
• trading_close_position — close the canonical position and reconcile the result.

Every execution tool runs through the same authority checks, nonce lane, cloid derivation, signing, and reconciliation path. Submission is never treated as execution; canonical Hyperliquid state is the only completion signal.

• trading_pause_mission — block new entries, scale-ins, reversals, and re-entry while preserving valid protection.
• trading_resume_mission — re-enable a mission the harness itself paused, after revalidating account, protection, authority, and provider availability. Rejected when the mission is blocked (for example cumulative_loss_limit): a blocked mission can only be resumed by an explicit user action, per the Risk page's no-auto-resume rule.
• trading_revoke_mission — permanently end autonomous authority; preserve valid protection if a position remains.

These controls let the harness wind a mission down within a turn. They follow the same path as the deterministic user controls below.

These typed RPC commands are invoked directly by workspace buttons and do not require a harness turn:

• trading_control_pause
• trading_control_resume
• trading_control_cancel_entries
• trading_control_reduce_position
• trading_control_close_position
• trading_control_revoke
• trading_control_close_and_revoke

Button behavior and loss-budget consequences are detailed on the Risk page; the bounded emergency-close procedure is §17.5 on the Hyperliquid page. Interactive control placement is shown on the UI concepts prototype.