Pokémon TCG — Dashboard and Local Tournament

The dashboard is the operating surface for local research. It manages models, decks, submissions, experiments, tournaments, ratings, configuration and local replay launch.

Local tournament

The first implementation is synchronous. Sweep-decks and vs-self remain active concepts, alongside local X1 matches. A tournament uses persistent dashboard-editable configuration rather than CLI parameters as its source of truth. The schema is intentionally compatible with a future continuously running CPU-bound arena, but that service is not part of the current implementation.

The current tournament script persists aggregate results and local match replays to SQLite. It still accepts CLI parameters and has not yet completed the dashboard-editable tournament configuration contract.

Dashboard functions

The current Streamlit dashboard implements practical views for overview, cards, decks, deck builder, agents, arena, replays, and configuration. The complete target dashboard remains larger: experiment creation, submission lifecycle, official visualizer launch, and source-aware tournament configuration are still open.

• onboard, rename, favorite, search and suspend agents/models;
• create, revise, compare and select decks;
• register local and remote submissions;
• create experiments and append observations;
• inspect source-separated Elo for submissions, models, decks and cards;
• list local replays and open the official visualizer externally;
• edit tournament and system configuration;
• relate local evidence to remote leaderboard/submission context without mixing sources.

Related

pokemon_tcg_local_overhaul · pokemon_tcg_local_platform_status · pokemon_tcg_implementation_specification · pokemon_tcg_arena_future_architecture · pokemon_tcg_schema_evolution · pokemon_tcg_replay_data_model · pokemon_tcg_submissions_and_elo · pokemon_tcg_deck_strategy