Backtest: Save And Communicate Results Responsibly
A final Backtest lesson for turning a result into a responsible research record: complete saved notes, useful tags, fair gross/net language, version discipline, and a future-you validation prompt.
Lesson promise
Frame the question
What should I record before this backtest becomes part of my routine?
Check the evidence
Use 5 guided chapters to read freshness, confidence, and caveats in order.
Move into the tool
Open Open Strategy Backtester with a checklist instead of a blank screen.
Educational workflow only. No trade recommendations, personalized advice, leverage guidance, or guaranteed outcomes.
Chapter 01
Save the result as a research card
Trader question
What should I record before this backtest becomes part of my routine?
A saved result is useful only if it preserves the hypothesis, market, date window, rulebook, risk settings, data source, cost assumptions, result limits, and next validation step.
Desk checklist
- Write the hypothesis in plain language.
- Record market, window, rules, risk, and data source.
- Add caveat and next validation before saving.
Interactive proof
Save strategy dialog and description field
Use the Responsible Result Card Builder to complete every required field before the saved strategy unlocks.
A saved strategy is a research artifact. Its value comes from the rulebook, assumptions, caveats, and next validation note that make the result reviewable later.
Interactive desk lab
Backtest Responsible Result Card Builder
A practical Backtest save lab for completing hypothesis, market window, rulebook, assumptions, caveats, tags, versions, and next validation before treating a result as reviewable.
A practical Backtest save lab for completing hypothesis, market window, rulebook, assumptions, caveats, tags, versions, and next validation before treating a result as reviewable.
A saved result needs a complete research note
A blank save dialog fills with hypothesis, market, window, rulebook, risk settings, data source, caveat, and next check before it becomes a research record.
A tempting result card sits beside an empty save note.
Required fields appear one by one.
The completion badge stays locked until caveat and next check are present.
The final frame stamps research record, not recommendation.
Lesson notes
The full chapter walkthrough in reading form — use it to review the lesson or skim ahead before working through the interactive steps above.
Chapter 01
Save the result as a research card
What should I record before this backtest becomes part of my routine?
A saved result is useful only if it preserves the hypothesis, market, date window, rulebook, risk settings, data source, cost assumptions, result limits, and next validation step.
Save strategy dialog and description field
- Write the hypothesis in plain language.
- Record market, window, rules, risk, and data source.
- Add caveat and next validation before saving.
Chapter 02
Use tags as research shelves
How will I find this result later without confusing labels for approval?
Tags and favorite flags are organization tools. They should help the learner find research families, cost-sensitive ideas, and forward-watch candidates without implying the strategy is ready.
Tags, favorite flag, and saved backtests list
- Tag the idea type, indicator family, and validation need.
- Use favorite for review priority, not conviction.
- Avoid tags that imply guaranteed quality.
Chapter 03
Communicate gross, net, and hypothetical limits
Would this result be misleading if someone saw it without the caveats?
A responsible result separates gross and net, states the assumptions, and names the hypothetical nature of the backtest. The learner should not write as if the result is live, guaranteed, or complete.
Result read card, metrics, and strategy description
- Label gross and net assumptions clearly.
- Say historical simulation or hypothetical backtest.
- Keep limitations close to performance numbers.
Chapter 04
Version changed assumptions
Did I change the strategy, or only explain it better?
If a threshold, date window, exit, cost setting, or filter changes after reading the result, the learner should save a new version and write why. Silent overwrites hide overfitting and make review harder.
Save/update strategy flow and saved strategy names
- Keep copy edits separate from rule edits.
- Create a new version for changed assumptions.
- Write the change reason before rerunning.
Chapter 05
End with the future-you retrieval prompt
What would I tell future-me about this result?
The final note should say what was tested, what would make it less trustworthy, and what to check next. That turns the saved backtest into a reusable learning object instead of a trophy.
Saved backtests list, result notes, and next steps
- Name the main observation.
- Name the caveat or invalidation condition.
- Name the next validation step.
Sources used for this tutorial
Next step
Open the tool with the checklist beside you.
Move from the lesson into the matching Bullion Brains tool, keep the checklist visible, and treat the output as evidence until the caveats are clear.