Monarch is Yoso's Hyperliquid companion PWA. It is portfolio and journal first, with AI as an operating layer and execution as an advanced, explicit capability.
The public route is /monarch. The internal application route group still uses /companion, and middleware maps the product URL into that surface.
Product thesis
Monarch should be useful before a user grants execution capability. The app starts from real account state, portfolio context, positions, risk, market awareness, trade history, journaling, and activity.
The assistant can explain PnL, summarize trades, tag journal entries, answer risk questions, and build previews. Confirmation remains gated by explicit capability, fresh snapshots, risk checks, and user action.
Trust levels
Monarch supports separate entry paths:
| Entry path | First value | Execution status |
|---|---|---|
| Create account | Account shell, wallet identity, funding and setup guidance | Preview-only until funding and capability checks pass |
| Log in with wallet | Existing Hyperliquid account context when available | Preview-only until trading capability exists |
| Import address | Public read-only portfolio and risk context | Never executable from import alone |
Do not treat a created wallet as a funded or trade-ready Hyperliquid account. The UI should distinguish wallet identity, Hyperliquid account funding, trading enablement, and Yoso execution capability.
Relationship to Relay
Relay is the execution builder and mandate model. Monarch can open the same builder from /monarch/plans/new, often with an asset or template already selected.
Monarch should not maintain a second execution-builder model. It should consume Relay previews, mandates, receipts, and activity objects through product-appropriate screens.
Core surfaces
/monarch: portfolio and account home./monarch/markets: public markets and market detail context./monarch/plans: previews, mandates, and Relay entry points./monarch/journal: reconstructed trading journal and review surface.