The revision loop: how we refine your tune with your logs

A tune is not finished the moment it's flashed. The revision loop is how your calibration gets better with real driving — and it's included with every tune, not sold back to you.

The first version of a tune is a strong starting point built for your exact car, fuel and boost target. But no calibration is final until the car has spoken, and the car speaks through its datalog. The revision loop is the whole business in one circle: upload, verify, refine — and it turns at least once on every tune we sell.

The loop

1. 01**Flash** — your per-VIN file lands in your account, flash-ready.
2. 02**Log** — drive it. Record a pull the way the file asks you to.
3. 03**Upload** — drop the log. Your file's VIN is parsed before a byte moves; the wrong car is caught at your end.
4. 04**Verify** — the log is checked against your registered VIN and the build it belongs to before the tuner ever reads it.
5. 05**Refine** — if the log says so, a revision ships with full lineage, traced to your VIN.

What a revision actually is

A revision is not a full retune from scratch. It is a refinement aimed at what the log showed — pulling a boost target back where it was overshooting, easing timing where the engine was correcting, or nudging fueling where the mix ran off. Each revision carries its lineage: which version it came from, and why, so the history of your car is readable at a glance.

No silence, no black box

The build queue is visible while a revision is worked: how many files are ahead and roughly how long they're taking. When the new map is ready it appears in your account, per-VIN, with the version before it still there to compare. Nothing about your tune moves without a record of it.

If a log fails verification, you'll know why — which check it missed and what that means — rather than a silent rejection. Honesty about the loop is the point: the datalog gets a vote, and you can watch it count.