Create the first usable terminal screen: a professional dashboard that opens directly to portfolio allocation, ranked subnet opportunities, key performance and risk signals, recent changes, and clear allocation action paths. Use realistic seeded Bittensor subnet data for now so allocators can evaluate the core workflow before live integrations are added.
Acceptance (definition of done)
Opening the product shows a polished default allocator dashboard without configuration. It includes a portfolio allocation summary, a ranked subnet opportunities table, signal cards for performance/emissions/stake/risk, recent subnet change feed, watchlist area, and visible actions to inspect a subnet or start an allocation preview. The layout is dense, scannable, responsive on desktop, and contains no maintainer or repository-facing language.
This is the current active step for this product. The maintainer will only merge a pull request that completes THIS step and demonstrably works. Open a PR that closes this issue.
Why this step now: With only documentation in the repo, the most valuable next move is to establish the product’s core experience: the default workspace allocators see first. This creates the foundation for later subnet inspection, allocation execution, monitoring, data integrations, and customization without jumping ahead to backend or chain-specific work before the cockpit exists.
Create the first usable terminal screen: a professional dashboard that opens directly to portfolio allocation, ranked subnet opportunities, key performance and risk signals, recent changes, and clear allocation action paths. Use realistic seeded Bittensor subnet data for now so allocators can evaluate the core workflow before live integrations are added.
Acceptance (definition of done)
Opening the product shows a polished default allocator dashboard without configuration. It includes a portfolio allocation summary, a ranked subnet opportunities table, signal cards for performance/emissions/stake/risk, recent subnet change feed, watchlist area, and visible actions to inspect a subnet or start an allocation preview. The layout is dense, scannable, responsive on desktop, and contains no maintainer or repository-facing language.
This is the current active step for this product. The maintainer will only merge a pull request that completes THIS step and demonstrably works. Open a PR that closes this issue.
Why this step now: With only documentation in the repo, the most valuable next move is to establish the product’s core experience: the default workspace allocators see first. This creates the foundation for later subnet inspection, allocation execution, monitoring, data integrations, and customization without jumping ahead to backend or chain-specific work before the cockpit exists.