CONTROL PLANE
Keep the workspace and its boundaries under control.
Understand local versus account-backed state, settings areas, paper/live portfolio boundaries, connections and plan access.
WHERE TO GO
The account surfaces have distinct jobs
| Surface | Use it for | Access note |
|---|---|---|
| /profile | Identity and profile details. | Account surface. |
| /settings | Workspace, account sync, portfolios and billing. | Member surface. |
| /dashboard | Portfolio summary and bounded analytics. | Member surface. |
| /pricing | Plan summary, prices and billing readiness. | Public reading surface. |
| /pricing/details | The complete tier matrix, what consumes credits, and the quotas. | Public source of truth for plan promises. |
| /docs/faq | Answers before changing account state. | Public guide. |
SETTINGS
Settings is four control surfaces in one route
Settings groups the controls that change how Meridian feels and how it stores state. Use the category rail rather than treating every setting as part of the chart.
- WorkspaceTheme, density and visual comfort for the terminal.
- Account & syncIdentity and the state that is saved to the account.
- PortfoliosPaper and live accounting domains, connections and verification.
- BillingPlan and automation capacity when billing is configured for the environment.
SYNC
Know what a sync state means
Local only
The session is not signed in or is not using account-backed persistence. A local change is not proof of a cloud save.
Saving or merging
The workspace is reconciling local and account state. Wait for the state to settle before reloading.
Synced
The current state has reached the account sync boundary. Keep the browser session stable if you are making a batch of changes.
Conflict or error
Stop and inspect the two sides or retry state. Do not silently overwrite a side whose changes you have not reviewed.
CAPITAL BOUNDARIES
Paper and Live are separate domains
Paper portfolios are the safe place to rehearse accounting and automation behavior. Live portfolios are tied to a verified venue connection and can expose real funds to real orders.
Connections should be read as a capability contract: identity, permissions, provider account mode and venue capability all matter. A connection that exists is not automatically a connection that is ready to trade.
Pricing and settings always present the sellable catalog. If the selected provider credentials, variants or webhook contract are unavailable, checkout reports that dependency failure directly; no separate environment or rollout switch admits the product. Treat a visible plan card as product information, not as proof that its external provider is currently reachable.
ACCOUNT ROUTES