Platform surface

The product is an app shell, not a landing page. A fixed sidebar holds the wallet, balance and the main destinations; a rolling confidence ticker runs across the top; and each screen is a page header, a row of stat cards, and a panel that scrolls its own rows while the page itself stays put.

What you can see

• Live alpha feed. Every bot decision as it happens, passed and rejected.
• Bot decisions. The score, the threshold, and the reasoning behind each one.
• Launch reasoning. Why a token was launched, in the bot's own blunt, numeric voice.
• Source tracking. The links that carried a signal, attached to the decision.
• Trending dashboard. What is moving across the watchlist right now.
• Launch history. Every token launched, sortable, each with its own page.
• Performance tracking. How launches have done since they went live.
• Watchlist. The set of stocks the bots scan, and what stakers have boosted.
• Alerts. Notifications on the events you care about.

The main screens

| Screen | What it shows | | --- | --- | | Home | Today's counters, the latest feed rows, and summary cards | | Feed | The full signal feed with stage filters | | Launches | A sortable table of every launched token | | Token page | Market stats, chart, swap, and the launch reasoning | | Portfolio | Open and closed positions with value and PNL |

Honest placeholders

Some of the designed surface needs data no backend returns yet: a live signal feed, live prices, holder counts, wallet positions. Where a real source exists, the screen uses it. Where one does not, the screen shows an honest placeholder rather than a fabricated number.

Today the home, feed, launches and token screens read real API data, and the ticker does too. A token page uses a live chart and swap once the token has a pool; before that it falls back to a plain chart and swap box. Portfolio stays on sample data until wallet trade indexing exists, and says so on the screen.