Know the version
Save the strategy code, configuration and historical report that precede the paper run. A label such as “RSI bot” is not enough if several rule variants share that name.
Verify time and data
Check the selected market, interval and last available observation. Define a stale-data condition and how the system behaves after downtime. Do not assume the bot is running correctly because a status badge is green.
Set observation boundaries
Write the simulated starting capital, position assumptions, review date and stop conditions. Separate an exit rule inside the strategy from an operational instruction to pause the experiment.
Inspect an actual event
When a qualifying signal occurs, compare the observed data with the rule, recorded position and delivered alert. A setup without any eligible signal may require more observation rather than a forced trade.
Review before revising
Record what happened before changing the strategy. Keep the original run and begin a new version when rules change. This makes later comparisons intelligible.
Sources and next steps
- Premiss pricing and paper bots ↗Paper bot allowances, supported alerts and separate approved live access.
- Premiss signal bots ↗Public description of strategy alerts and delivery workflows.