Yoso separates account identity, wallet connection, read-only account context, and execution capability. Those states should not be treated as the same thing.
Identity
Identity is how a user signs in or recovers access. It can come from email, Google, X, an external wallet, or another supported Privy-linked method.
Identity does not automatically mean an account is funded, trade-ready, or allowed to execute.
Wallets
A wallet can prove ownership, hold assets, connect to Yoso, or provide account context. Wallet state should be shown separately from execution state.
External wallets and embedded wallets can both be valid entry paths. Users should not be forced to abandon an existing wallet if that wallet is the account they already use.
Read-only accounts
Read-only import can show public account context without granting execution authority. It is useful for portfolio review, market context, journal reconstruction, and prompts.
Read-only import cannot confirm execution.
Preview and execution capability
Preview-only means Yoso can prepare or evaluate a candidate action, but it cannot execute it.
Execution capability requires the right account, fresh state, supported runtime checks, and explicit confirmation. If those are missing, the UI should say why instead of pretending the account is ready.