feature
Collect playbook data
After you have a Playbook, collecting data means logging deliberate example trades for that strategy — by instrument and time period — so reports and Historical Intelligence have enough of your executions to learn from.
This is different from a plain Backtest session (general practice) and different from Definitions → Collect (research setup events).
When to collect
You have a named setup worth tracking over time
You want roughly ~100 trades per instrument before trusting Historical Intelligence readouts
You will trade the setup intentionally in a collection session
Unstructured backtests still journal in Trades; they do not build playbook-scoped training the same way.
Session Map workflow
Playbooks → your playbook → Manage Playbook → Trade Book tab
Pick an instrument tab if the book tracks more than one symbol
On Session Map, click the year/quarter cell you want to work on
Choose Open in Terminal — Chartnaut loads a Collecting Data session for that slice
Trade the setup as you would live; each logged trade feeds that playbook quarter
Collection is instrument-scoped — typically up to ten symbols per book. Focus on markets you actually trade this setup on.
Audit trades in a quarter
When a cell has logged trades, open Trades from the quarter menu to review fills — see Data explorer.
Continue a quarter later
Session Map remembers progress per cell. Return to the same quarter instead of starting duplicate sessions.
Important distinctions
Collecting Data (playbook) = logging strategy examples for Historical Intelligence.
Definitions → Collect = gathering setup events for research studies.
Plain backtest = general market simulation without playbook collection intent.
Next
Data explorer — trades in one collection session
Historical Intelligence — what enough data unlocks
Tags and R-levels — label outcomes consistently