Monarch is not only a trading-confirmation surface. It should help a Hyperliquid user understand account state, market context, and trading history before any execution setup.
Markets
The markets surface helps users choose context before asking or previewing. It should handle public markets, loading and stale states, unavailable markets, search, and selected market detail.
Market detail can lead into Relay-backed run creation, for example by opening /monarch/plans/new?asset=ETH.
Watchlists
Watchlists keep markets and wallet addresses close to the user. They should remain useful in read-only mode and should not imply execution authority.
Journal
The journal reconstructs trade history and supports review. It can show fills, performance notes, tags, reviews, and assistant-written summaries when the source data supports them.
Journal content should stay tied to real account state. Avoid sample balances or sample trade history as default app state.
Activity
Activity should bring previews, mandates, orders, fills, alerts, and journal events into one traceable history.
For execution-related activity, show whether an item is a preview, draft mandate, active mandate, submitted order, fill, cancellation, or failure. That distinction matters for trust and recovery.
Assistant context
The assistant can answer questions about portfolio state, market context, and journal history. Trade-changing intent should become a preview object instead of staying as chat text.
Related pages
- Monarch/PWA Overview: Review the companion app's role.
- Plans and Relay: See how market or journal context becomes a Relay-backed preview.
- Where AI Fits: Understand the assistant boundary.