← Academy

The War Room

Every screen — what it does, how to use it

8 minLesson 8 of 8Reference

Seven screens, one job each. Here's what to open and when. A normal day flows Scanner → RaceDay → Desk → (settle) → Scorecard, with the Harness as the gate that decides whether any of it can go live.

Behind the screens: the data pipeline

The screens only show what the pipeline feeds them. It runs from the command line (or on a schedule), and each step has a self-test so nothing silently breaks:

the daily / weekly loop
npm run ingest:drf -- card.DRF --commit # DRF → canonical races/runners
npm run migrate:results -- --commit # finish + closing odds (the benchmark)
npm run features:build -- --version=v3 --commit # speed/form/pace → signal
npm run harness:run -- --feature-set=v3 # the verdict
npm run audit:factors -- --feature-set=v3 # which factors earn their weight
A winning day, start to finish
Open the Scanner → pick the strongest overlays → check each in RaceDay → stage stakes on the Desk and place paper bets → let races settle → review CLV/ROI on the Scorecard. Repeat. When the Harness flips to EDGE, the same flow goes live.
Takeaway
Scanner finds it, Desk fires it, Scorecard judges it, Harness gates it. Learn that rhythm and the platform turns into muscle memory.
The War Room · Academy · Closebeat