What users need immediately
- Identity established through wallet sign-in.
- A default Metavault available or clearly in progress.
- Fast access to spells, markets, and WorldMonitor.
- A visible path to add funds if action requires them.
Journey Model
Every path should move cleanly from interest to controlled action.
The PRD defines ten user flows, but they collapse into one narrative: reach a usable account state quickly, discover a relevant signal, act through a guided flow, and keep enough visibility afterward to trust both manual and automated behavior.
Primary Flows
10
Onboarding, discovery, triggers, casting, positions, funds, automation, and profile views.
Critical Handoffs
4
Signal selection, review, authorization, and post-action visibility.
Hard Rule
No ambiguity
Fees, permissions, account scope, and result state must always be visible.
Outcome
Trust
Users understand what happened and what can happen next.
Entry should feel light
The first-use experience should not block browsing. A default Metavault and account context need to appear quickly enough that the rest of the product is reachable.
Trigger creation must stay bounded
The user chooses a signal, defines a threshold, attaches an optional action, and reviews the implication before saving.
Casting is the irreversible moment
That is why fees, account selection, and likely outcome must all be visible on the review step rather than after the fact.
Autonomy is a user-controlled state, not backend magic
Users must understand what ARM allows, what DISARM revokes, and how automation costs will be deducted from the selected Metavault.
User entry
Onboarding should produce a usable state, not a setup maze.
Both wallet-based and embedded-wallet onboarding are supported. The first-use flow should let users browse before everything is perfectly configured, while still making account ownership and balance context explicit.
Discovery handoff requirements
- Browse by topic, category, or risk-relevant grouping.
- Search, filter, and sort prediction markets quickly.
- Jump directly from market context into trigger setup.
- Keep the transition from browsing to action obvious.
Trigger flow
Trigger creation is a guided “if this, then that” path.
The user chooses either a market threshold or a WorldMonitor factor threshold, configures the direction, threshold, and optional action, and then reviews the full implication before saving.
Step 1: Choose the signal
Signal origin should remain obvious throughout the flow so the user never loses track of what is being monitored.
Step 2: Define the condition
Threshold, direction, cooldown, max fires, and optional expiry form the bounded rule set.
Step 3: Attach an action
The user can select a target strategy or trade, vault, size, and optional risk controls such as TP or SL.
Step 4: Review before save
Recommendations may assist, but the user must still see the exact condition and resulting action before committing it.
Casting + positions
Casting should end in a visible position, not a dead-end confirmation.
The cast flow asks the user to choose a spell, account, and amount, review the outcome, and confirm. After success, the user should land in a position state with clear PnL, risk, actions, and event history.
Review step non-negotiables
- Selected spell and expected outcome.
- Selected Metavault.
- Amount and context.
- Estimated operation fee before confirmation.
Position detail non-negotiables
- Current value, PnL, and key risk metric.
- Attention state if intervention is required.
- Available management actions.
- Human-readable timeline and cumulative fees.
ARM semantics
ARM and DISARM are their own user journey, not just buttons.
The system can only earn trust if the user understands what autonomous access allows and can revoke it quickly. The current armed state must remain visible across the product, especially on positions and triggers that depend on it.
ARM review
Show allowed actions, account scope, limits, fee implications, and the fact that automation is bounded rather than open-ended.
Active automation
The product must signal clearly when a Metavault is armed and which positions or triggers depend on that state.
DISARM
Revocation must be easy to find and hard to misunderstand. It is a trust control, not an edge-case admin function.
Ongoing use
The later flows extend the same logic: clarity over novelty.
Moving funds, creating additional Metavaults, exploring more strategies, or looking at profile and leaderboard views should all reinforce the core account and position model rather than distract from it.
Move funds
Transfers must show source, destination, and balances before confirmation.
Create additional Metavaults
The user should understand why multiple vaults help isolate different goals or risk postures.
Explore strategies and view profile
These surfaces support decision-making and continuity, but they should never eclipse the core product loop.