Tool lesson

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.

14 minBeginner5 chapters

Educational only

The examples teach workflow and risk framing. They do not provide 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.

1DescriptionA saved strategy should explain the hypothesis and exact rulebook.Future review needs the market idea, instrument, date window, entry and exit rules, risk settings, and data source, not only a pretty return number.

2TagsTags organize research; they do not certify quality.Use tags such as seasonal-filter, RSI, cost-sensitive, or needs-forward-watch so the library can be searched without turning labels into approval.

3LanguageGross, net, and hypothetical need visible limits.Communicate that results are historical simulations with assumptions, costs, and data limits. Avoid performance language that sounds live or guaranteed.

4VersionChanged assumptions deserve a new version.If thresholds, dates, costs, exits, or filters change after reading the result, preserve the old version and name what changed.

5Next checkThe last field should tell future-you what to watch next.A responsible result ends with the caveat, invalidation condition, and next validation step instead of a command to trade.

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.

Native scroll

48s Remotion sceneSavedDescriptionChecklistVideo

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.

Storyboard beats4 cues

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.

Remotion code

SavedDescriptionChecklistVideo

The snippet is stored with the lesson so a future Remotion project can render the chapter video.

Show component snippet

import {AbsoluteFill, Easing, Sequence, interpolate, useCurrentFrame} from "remotion";

export const SavedDescriptionChecklistVideo = () => {
  const frame = useCurrentFrame();
  const reveal = interpolate(frame, [18, 92], [0, 1], {
    extrapolateLeft: "clamp",
    extrapolateRight: "clamp",
    easing: Easing.bezier(0.16, 1, 0.3, 1),
  });
  const fields = ["Hypothesis", "Market + window", "Rules + risk", "Data source", "Caveat", "Next check"];

  return (
    <AbsoluteFill style={{background: "#fff8e8", color: "#071126", padding: 72}}>
      <h1 style={{fontSize: 52, margin: 0}}>Save the research note, not just the result.</h1>
      <div style={{display: "grid", gridTemplateColumns: "0.78fr 1.22fr", gap: 30, marginTop: 62}}>
        <div style={{border: "1px solid #d9caa7", background: "#fffdf7", padding: 28}}>
          <p style={{fontSize: 18, color: "#5f6b7c"}}>Result card</p>
          <strong style={{display: "block", fontSize: 42, marginTop: 18}}>+8.4%</strong>
          <span style={{fontSize: 20, color: "#8a5a0a"}}>historical simulation</span>
        </div>
        <div style={{display: "grid", gap: 12}}>
          {fields.map((field, index) => {
            const visible = reveal > index / fields.length ? 1 : 0.24;
            return (
              <div key={field} style={{border: "1px solid #b69a5b", background: index > 3 ? "#fff6d8" : "#fffdf7", padding: 15, opacity: visible}}>
                <strong style={{fontSize: 23}}>{field}</strong>
              </div>
            );
          })}
        </div>
      </div>
      <Sequence from={104} layout="none">
        <p style={{fontSize: 25}}>Complete means understandable later, not convincing today.</p>
      </Sequence>
    </AbsoluteFill>
  );
};

Sources used for this tutorial

Backtesting and SimulationCFA InstituteUsed for the lesson's framing that a saved backtest should preserve assumptions, metrics, and validation context.GIPS StandardsCFA InstituteUsed for fair-representation, full-disclosure, and gross/net communication language around performance records.Investment Adviser MarketingSECUsed for fair-and-balanced hypothetical performance framing and risk/limitation disclosure.F-Squared False Performance ClaimsSECUsed as a cautionary example for why backtested results should not be presented like verified live performance.NFA Interpretive Notice 9025National Futures AssociationUsed for futures-oriented hypothetical-performance limitations and the warning that disclosure alone is not enough.Paper TradingCharles SchwabUsed for the final validation-step language that simulated and practice results do not ensure live success.

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.

Open Strategy Backtester