Apothecary

Monarch should make account trust levels explicit. A user can browse, import, connect, or create an account without granting execution authority.

Entry paths

Create account

Use this path for a new user who wants a simple account and wallet identity. The first useful state is wallet identity plus funding and setup guidance.

Say wallet ready or account created when that is all the product can prove. Do not say ready to trade until funding, trading checks, and execution capability are present.

Log in with wallet

Use this path for existing Hyperliquid users. External wallets remain first-class and should not be forced into an embedded wallet model.

After login, Monarch can load real portfolio, position, risk, and journal context when account data exists.

Import address

Use this path for read-only proof. Address import uses public data and does not require signing.

Imported addresses can show portfolio, positions, risk notes, journal reconstruction, and prompts. They cannot confirm execution.

Account states

The home surface should handle:

No wallet.
Syncing.
Sync failed.
No Hyperliquid deposit.
Spot USDC transfer needed.
Deposit needed.
Optional subaccounts.
Perps ready.

Empty accounts should still be useful. Show address, freshness, and the next safe action instead of sample balances.

Execution capability

Execution capability is separate from login. Monarch should label capability states such as:

Preview-only
No master key
Confirm to execute
Capability active

Do not show a confirm control that appears executable when the account is only read-only or preview-only.

Freshness

Account and market data must carry freshness. Stale or disconnected states can show existing data, but preview refresh and confirmation should be blocked until the state is current again.

Account and Wallet Model: See the docs-wide identity and wallet boundary.
Plans and Relay: Understand preview-only and execution-capable flows.
Security and Trust: Review wallet prompts, signatures, and trust boundaries.