Acquire
Define signal provenance, timebase, drop behavior, and session metadata.
Active developmentRacing / GR86 development log
Telemetry before parts
Treat the car as a system. Establish the measurement loop, label the conditions, change one thing, and keep enough context to know whether it helped.
Vehicle and driver conclusions require named track, sensor, setup, and environment evidence. Repository-static analysis is not a lap, a dyno pull, or a safety claim.
Platform / Toyota GR86
Build the evidence loop.
The current engineering lane is the telemetry foundation: acquisition, timestamps, session context, derived signals, comparison, and honest uncertainty before configuration advice.
Read the noteDevelopment ledger
Explain
Turn raw channels into reviewable behavior without hiding filters or assumptions.
PlannedCompare
Bind setup and conditions to repeatable baselines before drawing conclusions.
PlannedChange
Use evidence to prioritize hardware, setup, driver practice, and the next sensor.
Owner / track gate