TRACK Engineer · coaching

Coaching that shows its working.

The Engineer reads your session the way a race engineer would: it finds the corners where time goes, explains why in plain language, and points to the exact laps and measurements behind every sentence. If it can’t cite it, it doesn’t say it.

Join early accessTry it ↓iPhone app in beta · Android planned
Every claim
cites a measured fact

A grounding check rejects anything it can’t back up.

Offline
questions answered in the pits

Built-in answers work with no signal; the cloud Engineer adds depth.

Never
writes to your ECU or invents data

Braking without a brake sensor is labelled INFERRED.

03TRACK Engineer · AI coaching

Coaching that shows its working.

Every number the Engineer says points to a measured fact. If it can’t cite it, it doesn’t say it.

  1. 01

    Measure

    Deterministic code turns the session into laps, sectors, corner speeds and braking estimates, each with its uncertainty. No AI involved yet.

  2. 02

    State the facts

    Every measurement becomes a numbered fact with its provenance: observed, inferred or simulated. Braking without a brake sensor is always marked inferred.

  3. 03

    Coach with evidence

    Coaching is written from those facts only. A grounding check rejects any number that doesn’t appear in a cited fact.

Session report · #31 · Cascade Ridge Raceway
Demo session
LapTimeS1S2S3
12:07.32644.47637.28445.574
22:06.33343.70537.12245.540
32:06.10643.53837.12245.440
42:06.56343.73837.18145.614
52:06.01043.54337.08445.440
F1GNSS external at 25 Hz, median reported accuracy 0.6 m (simulated demo data)
F2Best valid lap: lap 5, 2:06.010 ±0.01 s
F3Ideal lap from best sectors: 2:06.062 (theoretical — sectors from different laps)
F4Lap time spread (1σ) across 5 valid laps: 0.47 s
F5Top speed 254 km/h on lap 5, main straight
F9T7: lap 3 was 0.14 s quicker than median; minimum speed 4 km/h higher
F13T3: peak deceleration median 0.81 g vs session peak 1.06 g (derived from GNSS speed)
F14T3: minimum speed median 84 km/h, best-lap 87 km/h
F15T3: braking at 76% of session peak; estimated opportunity 0.2–0.3 s per lap (model estimate)

Ask the Engineer

Ask in plain language. Answers quote the session’s facts, and the Engineer works offline in the pits. It also says no: it won’t invent data, and it never touches your ECU.

  • ▸Offline answers: built and tested
  • ▸Cloud Engineer: beta, with a cost ceiling and grounding guard
Engineer · session #31Offline · canned demo

Pick a question to see a cited answer

01How it works

How it works

  1. 01

    Facts first

    TRACK measures each corner: braking point, minimum speed, exit speed, consistency.

  2. 02

    Find the pattern

    It compares laps to find repeatable habits, such as braking early into the same corner.

  3. 03

    Explain with evidence

    Each insight links to the laps and numbers behind it.

  4. 04

    Ask anything

    Ask in plain language between sessions; it says no when it doesn’t know.

02What’s in it

Built, tested, and labelled honestly.

Every feature shows where it really stands: built and tested, in beta, awaiting hardware validation, or planned.

  • Evidence-cited insights

    Deterministic facts turned into specific advice; tested to find an injected braking habit.

    Built · tested
  • Offline Q&A with citations

    Answers that quote the session’s facts, with a grounding validator.

    Built · tested
  • Cloud Engineer

    Deeper analysis through a model router with a cost ceiling and the same grounding guard.

    Beta
  • Lap comparison and ideal lap

    Traces, corner metrics, lap-against-lap comparison and your best sectors combined.

    Built · tested
  • Instructor review

    Students share a session; instructors reply with corner notes, starting from the Engineer’s findings.

    In the app beta · local for now

03Who it’s for

  • Self-coached driversA second pair of eyes on every session.
  • StudentsHomework between instructor sessions.
  • InstructorsA head start on every review.
Go deeper

Questions

Is it a chatbot guessing at answers?

No. It works from measured facts about your session, cites them, and a validator blocks answers it can’t ground.

Will it suggest engine tuning?

Never. TRACK only reads data and won’t advise ECU changes.

Does it need internet?

Built-in insights and Q&A work offline. The cloud Engineer needs a connection.