Follow the decisions in a paper run

What you will learn

Connect the pieces while keeping fills and positions explicitly simulated. This is a draft lesson outline for the course preview.

The idea

A paper run exercises the program without sending real orders. It can reveal mismatched inputs, stale state, and unclear decisions. Simulated fills do not establish how real orders would execute.

A small example

Design a small status panel with connection state, last event time, hypothetical position, and the most recent decision reason. Label the entire run as simulated, including any displayed profit or loss.

Try it yourself

Create a paper-run checklist covering startup, a disconnect, a repeated event, reset, and shutdown. Save the log for each scenario.

Before you move on

Can a stale or disconnected feed still trigger a decision? Can you tell the difference between a decision and an assumed fill?

Use Next lesson below to continue the course, or return to the course overview.