Track Lab is becoming part of the normal LapMind loop
23 September 2026
At first, Track Lab was something you reached through imported diagnostic evidence. That was useful for research, but it was never meant to be the normal product flow.
The current LapMind loop is much closer to DRIVE → SESSIONS → LAP → ANALYSE → TRACK LAB.
A saved lap can now carry its own local trace and open straight from Sessions into analysis. No ZIP. No file picker. No diagnostics workflow for normal use.
That sounds like plumbing, but it changes the product. Sessions are no longer only a record of what happened; they can become the doorway back into the drive.
The map side is changing too. Track Lab is moving away from a generic trace floating on a canvas and toward a more faithful track-specific presentation. Recent Android work also found and closed a global left/right mirroring defect, so orientation now matches the real driving direction in physical testing.
Tsukuba is where that change has become visible. The current Android experiments can show a recognisable track surface rather than only a line: road shape, the pit path, kerbs and selected trackside surface detail sit underneath the driver’s own cyan trace. It suddenly feels much more like returning to a place you drove, rather than opening a telemetry plot.



Tsukuba has already been through real-device visual review, and the presentation is still being refined. That is the interesting part of the current phase: getting the map to look convincing without allowing presentation polish to outrun the evidence underneath it.
It looks promising, but this is exactly where LapMind should stay disciplined: a good-looking map is not automatically an approved product feature.
Track Lab is still experimental. The difference is that it is starting to feel like part of LapMind rather than a laboratory attached to it.
And the important part has not changed: the saved driving evidence stays local.