Using the Platform — Tools, Data & Workflows

Core screens

Screen	Purpose	Key actions	Learning resources
Strategies List	Browse evaluated strategies with scores and metrics.	Filter by pair, interval; sort columns; open details.	List help, Indicator reference
Strategy Detail	Inspect indicators, performance stats, and trades.	Review factors JSON; read notes; export signals.	Detail help, Basics
Executed Trades	Audit historical entries/exits recorded in the system.	Filter by strategy name, date; download CSV.	Trades help
Analytics	View aggregate statistics across strategies.	Compare cohorts, spot outliers, monitor releases.	Risk guide

Headline: Shows name, trading pair, interval, evaluation date. Confirm the data is recent.
Performance metrics: Daily profit, win rate, profit factor, drawdown. Cross-check against your risk plan.
Bands & factors: The first_band/second_band JSON defines indicator types and parameters. Use the Glossary if a term is new.
Trades table: Review recent signals and outcomes. Note streaks or regime shifts.
Documentation links: Jump to the relevant category page (e.g., Moving Averages) for deeper context.

Tip: Save annotated screenshots of detail pages when you adopt a strategy so you can revisit why you chose it.

Use the CSV download buttons to pull trade history into spreadsheets for analysis.
Track metrics such as expectancy, drawdown, and time-in-trade. Compare to live results weekly.
For Python users, load CSVs with pandas.read_csv and build dashboards (avoid exposing keys or private data).
Archive CSV snapshots before making major changes so you can revert or audit performance.

Daily: Scan the Strategies list for new entries, log interesting setups, update your watchlist.
Weekly: Review the Analytics page, note regime shifts, update risk levels.
Monthly: Retire underperforming strategies, archive notes, and add new learnings to your playbook.
Team sync: Share the Learning Hub link with new hires, assign a mentor to review their first trades.

Use the inline help buttons for contextual tips.
Report bugs or suggest improvements via [email protected].
Keep track of documentation updates in your internal changelog so the team stays aligned.