# Weigh driving against setup, with the evidence.

**Racing's AI reads the synthetic Jerez comparison and writes competing driving and setup hypotheses, each tied to the evidence it cites and to what is missing.** You correct the context, request a revised analysis and leave with one editable test plan. It advises; engineering judgment stays with you.

## What the AI race engineer does today

Everything here ships today on the synthetic scenario. The model runs on the OpenAI API and is called only when you request an analysis.

1. Reads the evidence you selected: run medians, the laps you kept, the A02 and B02 corner windows and each run's reported context.
2. Writes driving and setup hypotheses, each with the evidence it cites, what remains uncertain and which measurements are missing.
3. Proposes one next test that can tell the explanations apart.
4. Takes your corrections. Add what the data cannot show, then request a revised analysis. Earlier results keep the revision they were built on.
5. Turns the proposal into one editable test plan you save: the change, what to hold constant, the measurement, the success criterion and the stop condition.

## What it does not do

It interprets measured differences; it does not prove a cause. Every result carries the label AI-generated, advisory.

- It does not fill a missing measurement with a guess or a zero.
- It does not claim a lap-time gain for any change.
- It does not choose the test for you. The plan is yours to edit before you save it.

## What is sent, and when

Only when you request an analysis, the selected evidence and your saved context notes go to the OpenAI API with storage disabled. The provider may keep requests for up to 30 days for abuse monitoring. [Data ownership](https://apexscout.racing/data-ownership) shows the full flow.

## The method behind the debrief

The debrief follows the order an engineer would. [Driving or setup: separating causes](https://apexscout.racing/guides/driving-or-setup) explains how to read the traces. [Designing one discriminating test](https://apexscout.racing/guides/one-discriminating-test) explains how the next test is chosen.

## Design-partner roadmap, 2027 season

Planned with design-partner teams for the 2027 season. Not available today.

- A per-team isolated model trained only on that team's data. No cross-team training and no shared model.
- MoTeC and AiM CSV import, so the debrief reads your own logged sessions.
- Team data stays the team's, with export and deletion when a team leaves.