Monarch has plan and mandate surfaces, but Relay owns the execution-builder direction. The PWA should open the shared builder rather than maintaining a separate plans UX.
Entry points
The main PWA creation route is /monarch/plans/new. It can carry context such as an asset or template into the shared builder.
Examples:
/monarch/plans/new?asset=BTC
/monarch/plans/new?templateId=template-123Relay can also be opened directly from /relay when the user wants the standalone product surface.
Shared boundaries
Monarch and Relay should share:
- Intent parsing and clarification boundaries.
- Run readiness validation.
- Preview creation.
- Confirmation rules.
- Durable mandate runtime.
- Worker evaluation, receipts, and activity.
They should not fork strategy language or create incompatible template models.
Preview-only mode
Before execution capability exists, Monarch can create previews and explain setup. It should not show a final confirm action as if execution is available.
The preview can still be valuable: it explains trade shape, blockers, risk state, and missing setup.
Active mandates
Active mandates belong in activity and plans surfaces. They should show state, receipts, pause/resume controls, cancel or revoke actions, and current blockers.
Users should be able to reach mandate state from Monarch without needing to replay chat history.
Product copy
In Monarch, plans can describe the navigation area, but the user-facing execution object should still be the Relay run, preview ticket, or mandate.
Related pages
- Relay Overview: Understand the shared execution-builder model.
- Preview Tickets and Mandates: Review the preview and confirmation boundary.
- Wallets and Account State: Check account capability before confirmation.