Dry-run replays decision paths against recorded or synthetic books (exact mechanics depend on your kit). It is the primary gate for config mistakes, missing credentials, and obvious policy errors before you enable live routing.
Passing dry-run is not go-live
Treat a green dry-run as necessary, not sufficient:
Venue latency, partial fills, and oracle drift can still invalidate assumptions.
Risk limits must match real account and venue constraints.
Use Risk controls and your kit’s operator notes before widening throughput.
Audit output
Capture dry-run logs and JSONL output when you change profiles. Compare against prior baselines using Replay and audit.
