The Weekly Loop
Formula Analytics / Weekly Loop ← Back to About

System reference · not marketing copy

The Weekly Loop

Every job Formula Analytics runs on its own, all week, laid out in the order it actually fires. Clock-fixed jobs come straight from the cron lines in .github/workflows/*.yml. The four diamonds are the Conductor's phase transitions — they carry no fixed clock time of their own; they fire off the real FastF1 session schedule via f1analytics/schedule.py, so they're placed here at a typical weekend's hours, not an exact one.

one-time cron job continuous cadence — see panel above that day Conductor phase transition (session-timed)

Continuous · Monday–Thursday

Market snapshot → alerts → redeployevery 6hf1-ops.yml
Stewards feeddailystewards_feed.yml
MON

Telemetry pull

04:00 UTC
f1-ops.yml

Extracts Monday's qualifying + race lap/session metrics before the ingest step needs them.

Results ingest

06:00 UTC
f1-ops.yml

Refreshes the classified results seed now that telemetry has landed.

Kalshi odds backfill

07:30 UTC
backfill_odds.yml

Adds the just-settled race's price-candle history to the backtest's historical-odds store, ahead of the model gate.

Settle → report → health

08:00 UTC
f1-ops.yml

Realizes paper-ledger P&L from the classified results, builds the Monday retro, then runs a health check — one chain.

Model gate

08:00 UTC
model_gate.yml

Full walk-forward evaluation of the live model against history — the week's one formal correctness audit.

Dashboard deploy

08:30 UTC
weekend_dashboards.yml

The week's only Monday publish, timed 30 minutes after the retro chain so that page is actually live before it deploys.

TUE

Base-model evolution review

10:00 UTC
base_evolution.yml

Epic 7's slow second clock — reviews the week's accumulated race records for durable proposals a single result shouldn't drive. Always human-gated before touching the live model; never a dependency of any weekend phase.

WED

FIA upgrade report · pass 1

09:00 UTC
f1-ops.yml

Checks for the official upgrade-submission PDF — usually still "not yet published" this early in the week.

THU
No unique job — the Mon–Thu snapshot/alert/deploy chain and daily stewards feed above keep running.

Continuous · race weekend, Friday–Sunday

Market snapshotevery 2hf1-ops.yml
Dashboard render + alertsevery 2hweekend_dashboards.yml
Stewards feedhourlystewards_feed.yml
FRI

EARLY → PRE_QUALI

~mid-morning · session-timed

Fires once the first practice (or sprint) session is 3 hours old — not on a fixed clock. Opens human_gate, registered first: nothing else in this phase runs until it clears. 48h auto-accept.

FIA upgrade report · pass 2

09:00 UTC
f1-ops.yml

Second pass — the submission PDF usually lands by Thursday or Friday.

FP2 practice stints report

18:00 UTC
f1-ops.yml

Long-run pace read once Friday practice 2 wraps.

FP2 practice stints · late slot

21:00 UTC
f1-ops.yml

Same report, timed for calendars running a later Friday session.

SAT

Telemetry pull

02:30 UTC
f1-ops.yml

Extracts Saturday's practice metrics ahead of the qualifying predict passes.

Health check

12:00 UTC
f1-ops.yml

FP2-report deadline check, timed ahead of race day.

Predict re-runs

12:30 / 14:30 / 20:30 / 22:30 UTC
f1-ops.yml

Re-fires as the qualifying result reaches different timezone broadcasts.

Predict → record signals

17:30 UTC
f1-ops.yml

The official post-qualifying pass — the run that actually books paper trades.

PRE_QUALI → POST_QUALI

~evening · session-timed

Fires once Qualifying is 3 hours old. Opens gate_post_qualy — a shorter 12h auto-accept, since race day is close.

SUN

Predict fallback

06:30 / 10:30 UTC
f1-ops.yml

Catches qualifying results landing in very late timezones.

POST_QUALI → PRE_RACE

90 min pre-race · session-timed

The quiet phase — one last weather refresh ahead of lights out.

PRE_RACE → POST_RACE

race + 3h · session-timed

Runs the long chain: ingest → race log → settle → ratings advance + pages → race context → WoW report + delivery → handoff → loop_restart → base-evolution kickoff → gate_post_race (48h auto-accept). loop_restart writes next week's trigger plan right here — the moment that fires Monday's telemetry pull, above.

Always on

Not on a schedule

Sunday's POST_RACE chain writes next week's plan — then it's Monday, 04:00 UTC, again.