Annotations: ① Breadcrumb back to the list; the header shows the display name and the Status chip. Hovering the Status chip shows a tooltip with its reason, e.g. Active since 2026-09-30 · v3 first activated (variant; there is no Lifecycle card). Status is derived: Draft until any version is activated; the first activated version makes it Active, and deactivating the last activated version makes it Draft again (manually set Inactive or Archived stay unchanged). ② Description under the name (the class name is no longer here; it moved to the info strip ⑤): one line of secondary text, truncated with an ellipsis, full text in a tooltip on hover. Without a description it shows a grey Add description that edits inline (Enter saves, Esc cancels; empty-state variant ⑯). ③ Backtest is an MUI ButtonGroup split button. The main part Backtest runs immediately with the last settings of this strategy (version: latest from source folder; period: the last one used, the first time the dates in code); no dialog opens; the page switches to the new run (v7 / Run #43 · Running, variant ⑰), which also tops the Backtests drawer (03g). The ▼ part opens a menu with one item, Run with options…, which opens the Run backtest dialog (03i; menu shown open as a variant). ④ Edit (icon) opens display name / description / market. The ⋮ next to it is the strategy menu (variant, open) with the manual status actions: Set inactive… (confirm; paused: no bots can be added, running bots keep running; on an Inactive strategy the item reads Reactivate) and Archive… (confirm; read-only, allowed only when no bot is running; an archived strategy shows Unarchive, which restores the previous status). There is no Activate or Deactivate button in the header. Active and Draft are never set by hand: they follow from version activation (Activate vN on the version line of the run card ⑦; a version is deactivated from its clickable ✓ Activated chip there, in the info strip ⑤ or in 03f ⑤, confirm 03l, only while no bot uses it). Only Inactive and Archived are manual, via this menu. ⑤ Info strip, one Portenza card with two rows between the header and the run card: strategy-level facts that do not depend on the selected run. Row 1, the strategy facts: Class (full Lean type name, monospace), Source (Local folder and the path truncated from the left, full path in a tooltip; the newest dll under bin/** is read on every Backtest), Market Crypto · Binance spot, Registered date, and Versions 7 · latest v7 with View history (dialog 03f). Row 2, the live usage: Activated clickable chips ✓ v5 ▾ ✓ v3 ▾, each opening a menu with Deactivate (same as 03f ⑤ and the chip on the run card ⑦), enabled only while no bot references the version (here both are used, so disabled); Add bot offers only activated versions, default the most recently activated. Bots: running count and View in Bots → (the Bots page, sidebar QUANT › Bots, filtered by this strategy). A Draft strategy shows Versions 1, Activated None yet and Bots "activate a version first" (empty-state variant ⑯). No page tabs: below the strip the run card (⑥–⑨) and the sub-tabs (⑩) follow directly; the full run list lives in the Backtests drawer (03g), opened from All backtests (14) on the run card (⑧) or All backtests → in the cascader (⑭); version history is a dialog (03f); bots are managed on the Bots page. URLs: /strategies/vegas-tunnel (latest completed run) and /strategies/vegas-tunnel/runs/42 (a specific run, same layout; sub-tabs add /trades, /logs). ⑥ Run card under the info strip; without a run in the URL it shows the latest completed run (Running and Failed runs are skipped). Its title is a 2-level cascader v7 / Run #42 ▾ (MUI popover with two columns, versions › runs; variant, open) that picks version and run in one go. Status chips appear only when something needs attention: blue Running with progress, red Failed; a completed run shows no status chip. The Latest chip marks the latest completed run (Best · Net Profit on the best run, ⑱). URLs stay /strategies/vegas-tunnel and /strategies/vegas-tunnel/runs/42: the run number is unique per strategy, so the version is implied by the run; runs are identified by Run # only. ⑦ Version line (14px, directly under the cascader) describes the selected version: Built 10-24 23:41 (dll build time) and Activate v7 (contained, small), which belongs to the version: no confirm, Snackbar v7 activated with Undo (variant). An activated version shows the green ✓ Activated ▾ chip instead (variant, open; also ⑱); its menu has Deactivate, enabled only when no bot references the version (running or stopped; deleted bots don't count), opening the confirm 01l. On the right the version summary: 2 runs · best +48.2%. ⑧ Right end of the title row: All backtests (14) (outlined, small) opens the Backtests drawer with all runs of every version (03g); a thin vertical Divider then separates the run ⋮ menu (variant, open): Rerun this version (same version, period and parameters; selects the new run), Download results JSON, Delete (confirm; activated versions keep their flag). ⑨ Below a Divider the run details, four items: Period (here set in Run with options…; otherwise "from code"), Started 2026-10-24 23:44:06, Ended 2026-10-24 23:45:48, Duration 1m 42s. The version is not repeated (it is in the cascader); initial capital, fee model, resolution and parameters come from the code and are not shown. ⑩ Sub-tabs Overview | Trades (37, round trips) | Logs (smaller second-level MUI Tabs) switch the run content; URLs …/runs/42, …/runs/42/trades, …/runs/42/logs. Header, info strip, run card and sub-tabs stay in place on all three; there is no right rail, so Overview, Trades (03j) and Logs (03k) use the full width. ⑪ Statistics card, full width, collapsed: only the first two rows with the 8 core metrics in Karlo's order (the Backtests drawer, 03g, shows Net Profit, CAGR, Sharpe and Max DD of them): Total Trades (round trips = W + D + L, 37), Net Profit (USDT and %), CAGR, Win Rate (wins / draws / losses); Sharpe, Sortino, Profit Factor, Max Drawdown · Recovery 162 d (Lean DrawdownRecovery: longest peak-to-new-peak recovery). More ▾ expands the remaining 22 rows (Total Orders, End Equity, Total Fees, Calmar, volatility, win / loss stats, Alpha / Beta, Buy & Hold, …). With Total Fees 0 on crypto an amber Alert sits above it (variant). ⑫ Equity (log scale) against a dashed Buy & Hold BTCUSDT benchmark with the same capital; drawdown below on a shared x-axis; hover shows a crosshair on both. ⑬ Cascader, left column Versions: Latest, Activated (with bot mode, run count and best Net Profit), then the draft versions (not activated, not used by any bot; here v6, v4, v2, v1) collapsed by default, because local development creates many versions; search finds any version by number; View version history → opens 01f. ⑭ Right column: only the runs of the version highlighted on the left; All backtests → opens the drawer (03g). ⑮ A version with no runs yet (variant, hypothetical v8) shows No runs yet and Run backtest in the right column. ⑯ Empty state (variant): a strategy with no completed backtest shows "No backtest yet" and a large ▶ Run first backtest button (same as the header Backtest: dates in code, no dialog; Run with options… beside it). Rows of the list page (03) land here for such strategies. ⑰ Running (variant): after Backtest the cascader shows v7 / Run #43 with the Running chip and progress; Logs streams live, the other sub-tabs fill in when it completes. ⑱ Older run (variant): an info bar You are viewing Run #38 (v5). Latest is Run #42 · Back to latest above the run card. A failed run (variant, v4 / Run #36) shows the Failed chip and the error summary and opens on Logs.
Sample data: versions, hashes, runs and bots are for illustration only. VegasTunnel is a hypothetical spot long-only example.