Dashboard workflows and data labels
This page describes the proposed dashboard update. Availability depends on the application/API release and its completed validation; a merged pull request alone does not establish that every feature is live.
Ticker and market charts
The ticker is designed to scroll continuously and pause while you hover over or drag it. Keyboard interaction and the device's reduced-motion preference also pause automatic movement for accessibility. Moving the pointer away resumes the loop. Price refresh and ticker movement are separate behaviors.
Active stock and commodity cards show the configured Hyperliquid venue mark when a valid quote is available. An unavailable quote is shown as a dash, not zero. A listing marked Active does not mean the agent has placed a trade. Market charts retain the distinction between venue prices and underlying reference prices. Historical candles are not current mark prices.
Asking the agent
The proposed agent question flow requires login, a wallet whose ownership the API verifies, and a positive wallet-held 7N7D balance. Failed entitlement checks do not unlock chat. Command Center keeps its separate staking requirement; chat access is not a substitute for that requirement. Existing chat quotas and premium pricing are separate from the basic entitlement check.
Vault and staking confirmations
A submitted transaction is not yet a successful deposit, stake or withdrawal. The proposed modal flow waits for successful chain receipts, including approval before a subsequent transaction. While confirmation is pending, check the existing transaction rather than submit a duplicate. A missing hash, changed wallet context or unresolved replacement is not shown as completion.
A confirmed withdrawal request is still only a request. Follow the contract's withdrawal window and completion step before expecting funds in your wallet. For a status that remains uncertain after closing/reloading, inspect the wallet and chain before starting a new transaction. Live validation is still required for the proposed transaction flow; this guide is not a transaction guarantee.
Reports
Daily report dates are UTC calendar keys. Stored reported P&L is displayed with cents and explicit evidence labels. Missing days, failed requests and missing expense information are not converted to zero activity or zero costs.
A legacy verification flag is not proof of a reconciled account statement. Account-return Sharpe and marked drawdown require the corresponding normalized and scoped evidence. Daily summaries and observations describe what the producer reported; they are not independent trading-performance certification. Exports contain the loaded report sample, not an unlimited account history.
Development updates
The public development page displays deliberately published release summaries and bounded delivery counts. It does not display repository source, diffs, private PR bodies or internal implementation records. Some merged changes may have no public summary. Merged changes and deployed features are different states.
Trading-token proposals and navigation
Token proposals use an exact market from the catalog. Builder-DEX identifiers
such as xyz:TSLA preserve their namespace and case. Existing voting-power and
server checks apply. Creating a listing proposal does not itself place a trade.
No live proposal is created by the dashboard QA process.
The proposed update removes the standalone Alerts page from navigation. Internal operational safety monitoring is not removed.