Kovacs Labs
DRIVER OS GUIDE · EARLY ACCESSOpen Driver OS ↗
09 // SENSOR EVIDENCE

Read the source library and Race Fusion carefully

Advanced evidence reference: storage, delivery and analytical usefulness are separate facts.

Start with the source and its limits

A recording can be stored successfully without being usable for analysis. Delivery receipt, session relationship, data quality and analytical acceptance are separate facts.

Sensor Lab and Race Fusion are advanced research views. Rejected or ambiguous sources remain non-analytical. Phone and Watch signals are not calibrated vehicle telemetry, and weak signals must not become confident driving advice.

Read the deeper reference

The preserved guide below explains retained sources, timing relationships, quality gates and accepted slices. It is separate from the everyday Sessions → Progress → Coach path and does not change official results.

Understand the numbers · Sensor setup reference · Privacy and deletion

Detailed previous guidePreserved guidance · 2026-09-28

Source library

Expanded recordings remain available in the native app’s Recording information view. When expanded private cloud delivery is separately enabled for your native build and account, verified complete sources appear here for analysis. Older full sources require explicit authorization for that exact recording under the current consent. Review quality retrieves and verifies each chunk, then reports the existing channel availability, permissions, rates, gaps and errors. For recordings with a separate race-stop boundary, a derived interval excludes observations outside that boundary while the full source stays unchanged. An older source without that boundary does not receive an invented race window. Expanded review does not calculate official-lap sensor coverage or establish telemetry usefulness. Download full recording saves a verified archive in desktop Chrome; channel review is also available on phone. Local native copies remain retained.

A limited compatibility preview is not a full source and cannot be used for quality analysis or accepted telemetry. Older native cloud recordings and Sensor Logger files retain the library behavior described below.

Sensor Lab keeps each physical source visible: Sensor Logger, Driver OS iPhone and Driver OS Watch. Use the source filters to show any one of those sources or Paired sources. A paired badge means two same-account sources overlap in the same visit; it is not a quality decision or analytical acceptance.

The library shows six physical sources per page, newest first. Previous and Next keep the list manageable; the range and total show how much is available in the chosen filter. Changing the source filter starts at page one. Opening a recording or race and returning with the page's Sensor Lab link preserves the filter and page during that browser session.

Storage, delivery receipt, race relationship and quality are separate facts. A native source becomes an official-time candidate only when its absolute timestamps sufficiently overlap an authoritative race window. One continuous recording can span several separate official races without becoming several physical sources. Competing or insufficient official intervals remain unresolved. Rejected, ambiguous and not-reviewed sources remain visible for research, but they do not produce telemetry insights or change the journal.

Quality review is temporary in this release. Reloading Sensor Lab or opening it in another browser returns native candidates to Not reviewed until a later release adds durable review state.

Race Fusion

Start with the official result-sheet laps. Saved Sensor Logger race links and query-time native official-time candidates are shown as distinct relationships. Race Fusion adds sensor context only when timestamps, quality and the selected race support the comparison; a delivery receipt, paired badge or time overlap alone is not acceptance.

The same Session, race and recording selectors now include Sensor Logger, iPhone and Watch sources. Choose a race to see its official lap story and only that race's native evidence. Open race in a native source card goes directly to its official window. Existing Sensor Logger recording links still work.

Opening a recording restores a temporary analysis view without upgrading its saved summary or uploading another archive. Explicit recording actions remain separate from browsing. A native review whose official timing, lap boundaries or evaluator changed is withheld until you review the current evidence again.

For older native formats, quality review reports coordinate-free coverage and continuity by official lap. Recording-interval overlap is not sample coverage: sample count, whole-window rate and gaps show where data is actually missing. Leading and trailing gaps count, and malformed motion cannot be classified as stationary. These diagnostics remain research-only, do not establish racing activity, and never infer vehicle speed, racing line or calibrated kart G.

Accepted native slices

An accepted slice is interval-trimmed, compressed, account-bound and visit-bound. It is not a complete cloud recording. Analytical accepted-slice sync is disabled in the current checked-in native build, so accepted slices remain local.

Sensor Lab research gate

The research gate shows what is already useful as bounded context, what still needs a controlled test and what should not be collected routinely indoors. Its next batch uses paired, phone-only and Watch-only captures across several visits. Unusable captures still count, and shuffled or ambiguous controls must pass.

A passing gate keeps that result inside Sensor Lab first. It does not move telemetry into Sessions, Progress or Coach, accept a complete cloud recording or change official timing.

Reading the signals

  • Route, GPS speed and repeated-loop detection are estimates and may degrade indoors.
  • Braking, rotation and incident cues are not pedal data, calibrated vehicle G or crash detection.
  • Compare motion only across similar placements and environments.
  • Empty states distinguish a missing source from evidence that failed a quality or time-overlap check; the source itself can still remain visible in the library.
  • Sensor Lab does not replace official timing and does not use AI to decide whether a signal is valid.

Read the source and metric definitions

Race timing and sensor alignment

Venue race time, official lap duration and recording time describe different things. A result can provide lap durations to milliseconds while reporting the race time only to the minute. The email's delivery time cannot fill in the missing race-start seconds.

Race Fusion shows the venue time and its precision, the embedded recording start, and any recorded kart provenance. A kart time match helps identify a race; it does not prove where lap one begins in the recording. Sensor patterns fitted to official lap durations remain research alignment until an independent crossing reference validates them.

Indoor official-timing analysis, indoor motion usefulness, outdoor GPS telemetry and motion supporting outdoor GPS have separate evidence gates. An inconclusive indoor motion result does not reject outdoor GPS.

Adding all official lap durations to a known first counted-lap start, or subtracting them from a known final counted-lap finish, gives a possible recording window. The timing details show both interpretations when the venue timestamp's meaning is unverified. This arithmetic cannot recover seconds missing from the original result.