Your first drive through Driver OS

Your Driver OS

Eligible Real accounts use Home, Sessions, Progress and Karts at /driver. Community · Coming soon is visible in the menu. The blue Quick Kart button and green Coach stay within reach. A new account begins with an empty history, and every recorded result belongs to the authenticated account.

Complete the first-time profile and home-K1 steps once. The venue selector changes only the view you are browsing: choose an away venue or All venues, then return home when ready. A venue selection never moves recorded sessions.

The avatar menu opens full-width Profile, Settings, Help and Sign out. Profile changes your driver name and home K1; your username is permanent. Settings opens native email setup, compact activity/history tables and privacy controls. Help opens a separate tab. The old More tools portal and repeated setup wizard are no longer shown.

The authorized owner has a separate Owner workspace with protected operations and compact ten-row invitation/account tables. Community remains a preview with no sharing. Demo accounts retain their separate fictional experience. Older detailed workflows described below remain preserved at their original routes; they are not presented as settings in the new interface.

Historical detailed-tool preferences

Profile → App preferences lets you choose an explicit home track and whether new tabs start there or at All venues. Existing defaults stay unchanged until you save a choice. Home, Sessions, Progress and Coach share the venue you are browsing; switching venues does not save a preference or rewrite history or goals. Newer visits elsewhere remain linked, and direct Session or Event links open their own evidence. Home-track preferences stay in this account and browser; they do not sync across devices or between Dev and Production.

Where are you right now?

• I have not joined yet: Join early access and finish setup.
• I was just approved: Complete the required Profile step, then return to Home.
• I have a result to review: Bring it into the journal, then open the session.
• I am going to the track: Save the kart number or review the current action on Home.
• Something is not working: Start with the recovery guide.

Your first useful journey

1. Use your owner invitation to join early access, verify the newest email and complete setup. A second approval is not required.
2. Sign in and complete the required driver profile.
3. Connect a supported result source or add known values manually.
4. Open Sessions and check the result, laps and source context.
5. Add the kart, conditions, tags or short factual note that will matter later.
6. Use Progress after you have comparable evidence.
7. Use Coach to keep one practical next action visible on Home.

What is optional?

• Automatic K1 result forwarding saves time, but manual entry remains available.
• Quick Kart is useful at the venue, but it is not required.
• Sensor Lab adds experimental context and never blocks the core journal.
• AI explanations are limited to specifically entitled accounts. Race Day Review and other AI tools require their visible request action; opening a page does not start a paid analysis.

What good looks like

You can explain where a result came from, what changed across comparable sessions and what you plan to try next. Driver OS should make that story clearer without hiding the original evidence.

Join and set up Bring in a result Review a session

A short tour, whenever you want

After setup, you can take a five-step tour of Home, Sessions, Progress, Coach, and Connections / Quick Kart. It is optional and does not change your journal.

Replay the short Driver OS tour

Remember your rental kart

Choose Karts on desktop or More → Karts on your phone. Home shows recently used numbers for the current venue. Save kart number works without telemetry; Review saved captures opens the matching controls. History stays separate by venue, fleet and class. Save and review a number.

Set up Driver OS

For an invited Real account, /driver offers Sign in or Join with an invitation, using the newest email link or one-time code. Signup keeps the existing invitation, verified-email, age and required notice checks. Teen accounts require both existing guardian confirmations. A username is chosen once and remains permanent.

First-time setup guides you through driver profile, an explicit home K1, optional email guidance and the first-result review. This path does not ask for a home city. Driver name and home K1 can change later in Profile; your username is displayed as fixed text. The wizard is not offered again after completion. An old setup link opens Profile.

Continue and Finish wait for confirmed saves; errors explain any partial save. Email forwarding can wait. Finishing setup does not create fictional history, enable sensors or request paid AI. Email setup opens within Driver OS and has Back to setup while onboarding is incomplete. Required legal choices are handled in the native account check before racing history becomes available.

Demo Testers retain their separate fictional experience and established setup. No Real history is copied into their accounts.

Before you start

Use an email address you can open on the same phone or computer. Driver OS uses a secure email link and one time code instead of a password. In the invite-only testing flow, the owner must first invite that exact address as a Demo Tester or Real driver. Public interest signup does not grant app access.

Join early access

1. Open Driver OS and choose Join with an invitation (or Join early access in the Demo entry).
2. Enter the profile details requested on the form and accept the required legal terms.
3. Open the newest Driver OS email and use its secure link or one time code.
4. Follow the short setup steps after verification. One matching owner invitation is sufficient; an invited tester does not need a second approval after signup.

Sign in to the native iPhone app

In the internal native build, request the email from Driver OS on the iPhone where you want to sign in. Open the newest email on that phone. When the native sign-in service is available, its link returns to Driver OS; a browser may first offer Open Driver OS. The code in the email remains available if the link opens elsewhere or your email app keeps it in a browser.

Finish or recover a recording before signing in. A link requested by a different device or an older request cannot switch the recording account. If the connection drops, keep the app and its saved recordings in place and retry when online.

Open the web app from iPhone

The general web-app button opens Home. Links labeled for Sessions, account settings or a specific Event or session open that destination. When the handoff service is available for your native account, confirm the account shown by Continue as; no new email or code is required. A browser already signed into that account keeps its session. A different account is identified before you choose to switch. The link expires quickly and can be used only once.

If handoff is unavailable, expired or offline, Driver OS offers the ordinary web link. The browser may then need its usual sign-in. This does not sign the native app out. Accounts with additional authentication requirements use normal browser sign-in.

Owner invitations

Invitations and user accounts each show up to 10 entries per page. Use their separate Previous and Next buttons to browse; your unfinished invitation stays in the form.

In Owner → Invitations and access, enter the person's exact email address, select Demo Tester or Real driver, then choose Invite user. New Production invitations open app.kovacslabs.com. Check the delivery status before retrying an uncertain send. One invitation is sufficient; public update subscriptions do not grant app access.

Use Revoke invitation to withdraw an invitation before verified signup. Review the email and access type, then confirm. For an invitation already claimed by an account, use that account's Deactivate access or Deactivate demo access control instead.

A revoked invitation offers Re-invite for the same email and access type. This restores the invitation without sending email; choose Send invitation email afterward when you want to notify the person. If their email is already verified, they can sign in normally without another invitation email.

Under User accounts, the owner can deactivate Demo or Real access while preserving sign-in, profile and records. Restore access is available for deactivated Real drivers. Demo resets remain separate, and these controls never convert Demo data into a Real account. The owner account is protected from access removal.

If an email is already being sent, refresh its delivery status before revoking. An interrupted delivery may require reconciliation; retrying does not start another email. A message already delivered cannot be recalled, but a revoked invitation no longer grants access.

Use Reset demo data to restore a Demo Tester's fictional scenario while keeping completed onboarding. Reset onboarding and demo repeats profile setup. Deactivate demo access stops access and retains the account. Demo accounts cannot be switched to Real from this screen.

Set up your Driver OS

Welcome explains the journal in a few sentences. Choose Continue to start, then use Back whenever you want to review a choice.

1. Driver profile: choose the name you want to use for driving and a home city or nearby city. No street address or exact home location is needed. Your unique username is set once; your driver name and city can change later. Required age, Terms, Privacy and parent or guardian choices remain separate and must be complete.
2. What do you drive? Choose at least one interest. Rental karting appears first; expand Other driving interests for owned karting, car or motorsport events, and sim racing. Existing selections remain visible. Interests tailor setup and suggestions without hiding history or product areas.
3. K1 results: if selected, choose manual forwarding or provider guidance for supported formats. Driver OS receives only the messages you deliberately forward. You can skip this and return to Connections.
4. Garage: owned-kart and car interests offer one short vehicle form. Skip it if you want. A vehicle you choose here is added to your existing Garage at Finish. Rental karting does not require a vehicle.
5. Discover: optionally select a few directory suggestions near your city. Coverage is limited; a city with no suggestions can still finish setup. Discover remains available later.
6. Finish: review the summary and choose Finish setup. A Real journal contains only that driver's evidence. A Demo Tester's fictional pack appears only after this step.

Sensor and AI interest are available through Profile → Your driving choices → Optional setup. They are not separate steps in a new driver's default setup. Existing preferences and unfinished optional-step drafts are preserved. Interest does not enable recording, grant consent or AI access, request analysis, or create a charge.

Continue saves your choices to your account. Unfinished typing and choices are kept for that account in this browser, including when you leave and return later. When revisiting setup from Profile, Close setup returns to Profile and keeps those unfinished changes here; Continue saves them to your account for other devices. If a save fails, your choices stay on screen with a retry message; setup does not silently finish.

Optional steps offer Skip for now. Reopen driving interests in Profile → Your driving choices, and sensor or AI interests under Optional setup. Manage actual forwarding in Connections, consent in Sensor Lab, vehicles in Garage and venue follows in Discover. Changing an interest never deletes history.

Demo Testers keep real verification, username, legal choices and profile details. During setup, forwarding, native recording, vehicle creation and live location providers remain off. After Finish, Demo Connections, Garage and Discover show clearly fictional examples.

Take or replay the short tour

The optional five-step tour introduces Home (current picture and next step), Sessions (individual evidence), Progress (patterns), Coach (an action), and Connections / Quick Kart (results and kart context). It never asks you to create a race or perform a write to advance.

Use Back, Continue, or Skip tour. Escape closes it, Tab stays inside it, and it respects reduced-motion preferences. You can replay it from Profile or here after signing in:

Replay the short Driver OS tour

Know what is optional

• K1 result forwarding is optional and can be added later.
• Sensor Lab is optional and never blocks the journal.
• Model backed AI explanations are limited to specifically entitled accounts.
• Product update emails require a separate optional choice.

Demo Testers use simulated Connections and synthetic sensor summaries. Real results, uploads, analytical sync and live AI are unavailable for that tester kind.

What success looks like

For a Real Tester, Home opens with that account's own empty journal and next useful step. For an invited Demo Tester, the fictional scenario is populated only after required onboarding is complete. A persistent Demo data indicator explains its synthetic records, fixed scenario date and unavailable capabilities. Your verification, username and profile remain real.

If the email or approval step stalls

Use only the newest email. Request a fresh message if the link expired, and enter the newest one time code when signing in from an installed Home Screen app. Private testing access is required means the account has no applicable invitation. Private testing setup is not ready means the invitation is recorded but the testing environment has not been activated; this does not require a second personal approval.

Bring in your first result Open troubleshooting

Result email connections

Open the avatar menu → Settings → Manage connections. The full-width Connections page keeps Email setup, Email activity and Received history inside Driver OS, with compact tables showing ten rows per page. Back to Settings returns to account choices; incomplete setup has Back to setup.

Email setup shows your private forwarding address, trusted forwarding inboxes, Google confirmation status and local filter download. Saved changes wait for confirmation. A conflict keeps your draft until you reload saved email settings. Opening or paging the screen never checks mail, retries processing or generates imports. Check now and Open Google confirmation require explicit clicks; finish destination confirmation with Google.

Activity preserves the existing status and consent-based problem reporting. Received history lets you page through account-scoped email metadata without replaying messages. A received email is not yet a saved result, and a saved result is not proof that you reviewed it. Open session links to the recorded result when available.

Choose the path that fits the result

Use automatic forwarding for supported new K1 result emails. Use manual entry when you know the official values but do not have a supported source. Both paths should end in Sessions with the source and original laps still understandable.

Connect supported K1 emails

1. Open Connections, then open K1 Email.
2. Copy the private forwarding address and add it in Gmail. Return to Driver OS and select Check now, then open the Google confirmation shown to confirm your destination. This check runs when you select it, not automatically.
3. Download the two personalized Gmail filters. They are generated in your browser, and Driver OS does not connect to Gmail.
4. Import the filter file in Gmail. It contains one exact-sender filter shared by United States and verified UK Canary Wharf results, and one for Canadian results.
5. Before saving, verify the United States / UK Canary Wharf sender is member@from.k1speed.com, the Canadian sender is info@k1speed.ca, and both filters use Race Results in the subject, your private forwarding destination, the Kovacs Labs - K1 Results label and Never send it to Spam. Do not select Delete.
6. Forward an older original result individually if you want it in the journal. The rule applies only to new messages.

The two exact filters are deliberate. A broader K1 or all-mail rule could forward unrelated private email. Gmail filters do not retroactively forward messages already in the inbox.

Confirm the first successful result

Open the import status, then open Sessions. Confirm the visit date, venue, races and lap evidence before adding context. One source result should create one canonical race rather than a duplicate.

The supported United States and Canadian result formats work across the locations in Driver OS’s maintained K1 location directory, including numbered tracks beyond Track 1. You do not need to visit a location before Driver OS can recognize it. The email must still identify one venue, track and race time clearly and pass the existing sender checks.

Verified UK Canary Wharf Track 1 emails are also supported. They use the existing member@from.k1speed.com sender and Race Results subject rule; no additional forwarding rule is needed. Their printed date uses month/day/year. Driver OS uses Europe/London, including daylight saving, and records their standings as fastest-lap rank rather than a race finish.

Driver OS uses the venue’s local timezone and keeps UK, Canadian and United States ratings separate. An unfamiliar format, ambiguous location or conflicting race details stays visible in Received email history for review. Other UK venues/layouts and other countries’ email systems are not yet verified; worldwide K1 branding does not imply that every result format is supported.

If the email does not state a kart number, race type or racer class, those fields remain unavailable instead of being inferred.

Check import status

K1 email activity is a table of recent loaded emails. Use Previous and Next to move through ten rows at a time, Details for the status explanation, and the result or report action on that row. The page count covers the currently loaded checks, not your complete driving history. On a phone, scroll sideways inside the table to reach every column. Paging does not retry or change an import.

Connections shows your recent imports from receipt through saving and display. For new imports, Results ready means every expected race and numbered lap has been verified in storage. Display confirmation is separate: it is recorded only when the matching lap component renders in your normal Sessions view. It does not mean that you read or reviewed the result.

Earlier imports are identified as earlier history, without rewriting them or pretending they have new completeness checks. Your existing Sessions history remains available. If status checks are unavailable, that does not mean your saved results are missing.

Background checks flag delivery or processing delays and gaps in saved results. The checks read metadata; they do not fetch old emails, run parsers or send real notifications. Open Report a problem to share fixed-choice diagnostic information privately. Your consent allows the owner to inspect that report and its associated import metadata, not your other history. Do not paste original emails or other racers’ names; original-email report uploads are disabled.

In the protected development preview, these checks are read-only. Reports, display acknowledgements, forwarding confirmation, recovery and manual K1 uploads remain paused there. Existing mailbox rules continue to use the production receiver.

Manual entry

Enter only official values you can verify. Leave an unknown field empty instead of estimating it. A manual result should remain visibly different from an automatic supported import.

What Driver OS retains

New imports retain the message identifier, bounded status/reason codes and your minimized timing evidence. Other racers’ names are discarded before durable storage. Driver OS does not retain the forwarded or uploaded email body. The inbound email provider handles delivery under its own terms.

Interrupted, unsupported and duplicate imports

• Repeated supported imports reuse complete matching results. Conflicting evidence is held for review, preserving the saved result.
• If a new upload was interrupted, select the same file again. A complete result is not written twice.
• Needs review, failed earlier imports and unfamiliar formats require a reviewed recovery. Opening the app or changing a parser does not automatically reprocess old mail.
• Report a missing result before forwarding repeatedly. Do not fill gaps with guessed venue, timezone or race details.

Review the first session Connection troubleshooting

Demo Tester connections

In an invited Demo Tester account, Connections contains simulated status cards. There is no functioning inbound results address and no email forwarding, result import, telemetry delivery or analytical sync. Sign-in verification emails still work normally. The instructions below apply to separately approved Real testing capabilities.

Choose how to forward K1 results

Setup offers I’ll forward each result myself or Help me forward results automatically. Copy your private Driver OS forwarding address and send one original Race Results message at a time. If you use a different sending address from your verified sign-in email, add that address through Profile's trusted forwarding controls first.

Gmail reuses the destination confirmation and the two downloadable filters. Keep whole-mail forwarding disabled. Outlook / Hotmail can use two separate rules, each requiring the exact K1 sender and Race Results in the subject. The supported senders are member@from.k1speed.com for US results and info@k1speed.ca for Canadian results.

Yahoo's documented forwarding applies to incoming mail broadly. Driver OS has not verified an iCloud web rule that checks both sender and subject. Use manual forwarding for Yahoo, Apple / iCloud and other providers unless a verified narrow path is available. Never forward your whole mailbox to Driver OS. A saved rule is not proof of delivery; check the imported result in Connections.

Driver OS does not browse your mailbox, request its password or ask for broad email access. An automatic rule remains under your control in your email provider's settings.

Optional sensor tools

In More → Connections → Data Sources, unused Sensor Lab setup is under Optional tools. Existing sensor interest, consent or saved recordings keep Sensor Lab directly visible; a saved source remains accessible after consent is withdrawn. Opening these controls does not enable collection or change consent. Future providers remain under their separate planned-sources section.

Sessions in the driving notebook

Choose a recorded date, then a session. Its detail keeps the result's ranking basis, best lap, retained average and variation together. Lap evidence distinguishes all recorded laps from the retained subset. Faded exclusions explain the statistical rule or supplied reason; a slower lap alone does not establish traffic or a yellow flag.

Coherent source-supplied anonymous field data can show that session's comparisons. Unknown ranking basis stays unknown; fastest-lap rank is not a classified finish. The optional Nashville animation uses recorded lap durations and uniform movement on a sourced illustration, not measured speed, position or racing line.

Save a private note, known kart number or explicit context correction on the selected session. Original timing stays intact. Personal session and visit comparisons require matching context. Pagination changes the visible rows, not the calculation's evidence. Return links preserve your place.

The sections below describe the existing detailed review in More tools, including its additional filters, Events, saved analyses and widget layouts.

Review a whole day in C

Sessions opens with a by-day history. Select a date/venue, then use Day overview or a session selector above the evidence. Switch to the compact session table when looking for an individual record. Following evidence and returning keeps the selected context. Opening main Coach from a selected day or session carries that evidence into Coach without saving or changing an action.

Purple identifies the quickest recorded best lap in a day’s group; amber identifies the slowest. Ties remain visible. If purpose or racer class is missing, matching unknown sessions can still show these observed timing colors within that visit. The visible note explains that this does not establish comparable race performance. Known and unknown context never mix, and the colors do not change wider Progress eligibility.

Green requires a known, comparable result: recorded purpose, ranking basis and equal field size remain separate checks. Missing purpose/class cannot earn a green result highlight. A fastest-lap ranking is not a finishing position.

Qualifying and Race selectors give the recorded position and field size priority, while retaining the best lap. The individual result also leads with that placement. Read its ranking-basis label: qualifying order, fastest-lap ranking and classified race finish are different facts. A position with unknown basis stays a recorded position, not a confirmed finishing result.

Review a timing cue, then clear the reminder

A slower-session cue offers Review flagged session so you can compare the laps and recorded context together. Its short chart shows the observed differences from the displayed baseline. It is a prompt to inspect evidence, not an explanation of the cause.

Choose Mark reviewed after you inspect it. Undo restores it immediately; the reviewed-cues section offers Show again later. Only the reminder is hidden, for this account in this browser. Original sessions, chart evidence and saved coaching stay available. Changed evidence can produce a new cue.

Inside a flagged session, Mark date review reviewed clears the same date-and-comparison reminder shown on Home and in Sessions. It covers the flagged sessions for that date, not unrelated reviews. The timing review remains expandable with Show date review again, and Undo restores the reminder immediately.

Before you start

Make sure the result belongs to the expected venue, visit and race. Sessions is the evidence owner, so correct source details here before interpreting a pattern elsewhere.

Open the right session

1. Open Sessions and choose the visit date.
2. Review the day overview before selecting one race.
3. Check the official result, lap list and available standings context.
4. Confirm the venue, layout and class before comparing the result with another session.

Keep an organized Event together

Choose Events & session setup from Sessions to browse existing Events or create an optional container for related driving. This index also keeps Events without a currently loaded timing result accessible. Expand Event format & additional dates to choose Open/walk-in, League/championship, Group/private event, Endurance event or Practice/test when the type is known. Existing format values open automatically. Ordinary visits can stay exactly as they are, without an Event or a classification.

Add each individual session and choose its known purpose. Arrive & drive is a visit without an Event; Practice is practice within a race-day Event. The choices are separate. Qualifying and Race remain available, while an unknown purpose stays Unclassified. Endurance events also offer Endurance stint. Existing Heat, Final and stint records remain readable; editing other details preserves their original type. Indoor or outdoor describes the track, not a separate session type. Give it a useful name such as “Qualifying 1” or “Stint 2.” Attach the saved timing result when one exists; notes and source evidence can be added separately. Missing timing stays missing.

A linked Event appears as one visit in Home and Sessions. Open it for Day overview, then select Practice, Qualifying 1, Qualifying 2 or Race to see that session's timing and result. Repeated sessions are numbered in recorded order. This grouping does not combine statistics from different layouts, classes or vehicles, and does not establish how a result was ranked. Event details & setup keeps editing available. History is never classified automatically.

For a temporary team car, select temporary/team vehicle context. A label is enough to start. Make, model, year, car number and team can remain unknown until you know them. Each stint keeps its own timing, notes and source links.

Read the evidence in layers

For a post-racing overview, choose Review race day on Home or Review this visit within Sessions. Race Day Review follows pace and consistency through the visit, compares prior visits on the same recorded layout, shows anonymous field context and links useful moments back to their Session. Save its primary focus into Coach when you want to keep it for next time.

The summary compares today with your last and usual visit: green ↑ means faster or tighter, amber ↓ means slower or wider, and an equals sign means unchanged. The charts show race-by-race development; Race details & evidence keeps the numbers and Session links close by. Visit history and field trends use the same layout. Missing results leave gaps rather than becoming zero.

The review shows the included race count and last update time. New official results update the review. Different layouts stay separate, and conflicting identities or times require inspection in Sessions. Unmarked laps do not prove clear running; traffic and yellow flags need recorded context. Sensor evidence is optional and never changes official timing.

• Best lap is the quickest saved valid lap.
• Representative pace reduces the influence of excluded or unusual laps while keeping the raw laps visible.
• Lap time variation describes repeatability across the eligible lap set.
• Position and field context appear only when they were actually observed in the source.

Set a missing session purpose

Open a day, select the session, then choose Set session purpose. This opens the context editor with that timing result selected. Its date, venue, layout and a useful session name are filled from the linked timing when available; you can correct them before saving.

Choose Arrive & drive for an ordinary visit without an Event. You do not need an Event name. Choose Practice for a practice session within a selected race-day Event, or Qualifying or Race when those describe the session. A result can remain Unclassified until you know its purpose. Missing purpose is never filled merely because no Event exists. Save the explicit change, or return to the same review without saving. Purpose, optional Event membership and ranking basis remain separate facts; changing purpose does not certify a win or change timing.

Existing records with a saved Practice role and no Event appear as Arrive & drive; Practice with an Event remains Practice. This display distinction does not rewrite imported results.

Read saved analysis and notes in C

At the bottom of a session, expand Follow the evidence → Saved analysis & session notes. The evidence opens on the same C page. Existing notes, recorded tags and saved AI analysis retain their scope; a whole-day note or whole-source-session analysis is not relabeled as a fact about one lap.

Saved AI shows its current, stale or earlier-version status, measurements, limitations, sources, model and version information. Checking for an existing authorized saved answer does not generate a new one. Opening this section does not request AI or change an action. If no matching saved answer is available, the page says so and preserves the timing evidence.

Rating & result details shows the saved driver rating and change, gap to the field-best lap, timing timezone and verified grid/net positions when recorded. Country ratings stay separate; a field-best lap gap is not a finishing-time gap. Day overview totals recorded rating changes with coverage shown.

Day journal & comparison tools keeps existing day notes in their original track and session context. Edit notes, tags & kart opens the selected session's detailed editor; it also retains detailed result and timing tools. Reading saved analysis stays inside the review. Return to review restores your selected day/session and expanded evidence.

Add what timing missed

Save the machine or kart number, traffic or issue tags and a short factual note when they materially change how the run should be read. The note should preserve context, not guess at a cause.

Selecting or clearing Yellow, Traffic or another condition keeps the race’s Details open. You can make consecutive changes and save a note without reopening the section. These tags describe the race context; they do not change official lap timing.

What success looks like

You can return later and understand the result, the laps, the machine and the conditions without reconstructing the day from memory.

If something looks wrong

Do not edit several fields to make the summary look plausible. Check the source and import status first. A missing or unsupported value should remain unknown until you have reliable evidence.

See your Progress Understand the calculations Fix an import problem

Saved page layouts

In the wide review, expand Saved layout & optional Sessions widgets, then choose Customize Sessions to show, hide or reorder the existing race outcomes, representative pace and recorded-lap summaries. Expand a day inside that panel to inspect its optional widgets. These retain the existing saved widget choices and calculations; they are not table-column settings. The wide review’s by-day and individual-session history, selectors and evidence remain available. Save the layout to your account, or reset to default and save.

Use Events & session setup in Sessions to browse whole Events. Opening an Event from this list, a visit card or Progress leads to the same review. Main result labels show your position and field size; expand result details for the recorded ranking basis and source limitations.

Classify a whole driving day

In Sessions → By day, use Edit driving or Edit Event beside a day. The same controls appear inside the day review. The editor includes all loaded timed sessions at that venue on that date, even if the list is filtered. Unclassified sessions are selected first; use Select all or the individual checkboxes to change a different set.

Choose a purpose or Event, then Review changes. The before/after preview shows every selected session. Arrive & drive needs no Event and clears Event membership for the selected sessions. Practice requires an Event. Keeping each session’s purpose lets you attach an Event without flattening a practice/qualifying/race day into a single role.

Save only after reviewing the count and changes. Timing, result ranking, kart numbers, notes and recordings are preserved. If a save stops partway, completed sessions remain saved and the remaining selection stays available to review and retry. Changes made on another device require a fresh review.

Optional session setup

The session editor keeps purpose, official timing, kart number and venue/layout easy to reach. Arrive & drive shows No Event needed; Add/change Event stays available. Event-related purposes or a recorded Event reveal the Event picker.

Rental sessions summarize their vehicle context. Expand Change vehicle context to choose an owned Garage vehicle or temporary/team vehicle. Existing non-rental context opens automatically. More setup options on Events keeps temporary-vehicle creation available. These controls do not remove vehicles or non-K1 history.

Saved evidence references stay visible. Expand Add an evidence reference only when adding one; official timing works without sensor evidence.

Progress in the driving notebook

Use Pace & consistency, Racing rhythm, Competition and K1 score for different questions. Pace compares compatible recorded visits. Rhythm shows the first imported date and visit frequency, with month and day detail; a gap in imported records does not prove you did not race. Timing highlights apply to the selected comparable group and period.

Competition reviews one recorded field at a time. A finish and a fastest-lap rank remain distinct. Complete source-supplied scores describe the field; post-session scores do not predict where you should have finished. K1 score keeps supplied US K1RS/RPM snapshots within their annual period. Dated public references stay separate from your result.

Karts is a main destination. Repeated uses can show usage and compatible shared-date timing; single uses and unknown numbers remain accessible. These personal associations do not rank mechanical quality. Compare visits and session comparisons compare two compatible parts of your own history. If class, layout version or other comparison context is missing, you can still review the two recorded summaries side by side; pace deltas stay unavailable.

The detailed tools below remain available from More tools, with their existing filters, layouts and source inventories.

Pace, results and kart history

In the wide review, use Pace & results for comparable driving trends or Karts by venue for recorded kart numbers. Karts is also a main desktop destination and the first item in mobile More, backed by this same notebook. Home shows recent numbers for the currently selected venue and a route to full history. Temporary venue changes leave your optional home-track preference unchanged; All venues keeps separate venue groups. The summary uses all loaded dates and purposes at that venue, independently of chart filters and optional saved widgets.

Kart history separates the same number by venue, known fleet and racer class, and leads with recent uses among recurring numbers. Each number shows its last-used date and recorded use count. Unknown fleet/class stays separate. Single-use numbers and venues with no recurring number start collapsed. The coverage count keeps sessions with missing numbers visible. Two recorded uses make a number worth following; they do not establish a performance pattern.

Expand Pace, consistency & comparisons for personal timing and variation. For a kart with same-date comparisons, colored cells show the difference between your representative pace in that number and your other recorded numbers on the same date. Green is quicker and amber is slower, with the difference in seconds written in each cell. The latest six shared dates are shown; earlier dates remain in Comparison details & sources. If there is no same-date comparison, the small bars show recorded use counts instead of implying a pace trend.

Comparisons keep layout, racer class, session purpose, Event format and fleet separate inside each venue. Other contexts are expandable; their times are never pooled. At least three shared dates within one comparison context are needed to describe a repeated direction. Number reuse, conditions, session order and driver development remain uncontrolled. These observations do not prove a kart effect. All recorded uses shows linked sessions, available personal notes/tags, and per-session results against the recorded field. Supported field-best gaps and complete anonymous field-rating snapshots are shown with coverage; missing or conflicting evidence remains unavailable. Field sizes and opponents are not pooled into a kart score. Personal notes describe observations, not established mechanical causes. The paginated source table keeps the full evidence accessible.

Saved kart recordings shows uploaded Watch/phone session-context numbers. A unique recording within three minutes of resolved official timing is combined automatically in C when no competing race, recording or conflicting kart decision exists. Its source stays labelled Recording time match. Matches describe an association; they do not establish a kart effect or align sensor samples to laps.

Phone/Watch quick selections are also shown separately from timing-linked assignments where available. A saved capture, a cloud-delivered recording and a verified timing link are different states. These inventories do not add sessions or lap measurements to the charts. An unavailable cloud inventory does not mean a selection was never saved.

Additional evidence from C

Below the comparable trend charts, More progress evidence names the existing Competition & placements, Field ratings & time patterns, Achievements, and Overall pace & saved Progress analysis views. These detailed tools retain their layout and a Return to review action. Competition, field/time evidence and overall pace keep the selected venue, exact track/layout, vehicle/fleet, timeframe, purpose and Event context where those filters apply. Achievements are clearly labeled as career-wide. Opening a saved-analysis view does not request a new explanation.

What Progress helps you answer

Progress opens with your overall driver story. It helps you see whether pace, repeatability and outcomes are changing across your saved history without pretending that raw lap seconds from different tracks are comparable.

Before you compare

In the wide review, use the visible venue and purpose controls, then expand More filters when you need an exact track/layout, vehicle/fleet, timeframe or other recorded context. A league final, qualifying run and endurance stint answer different questions. Driver OS keeps their comparisons separate, including when they share a date and track. Ordinary history does not need an Event assignment.

Open Sessions first and make sure the result, track, class and useful context are correct. A comparison is more useful when the sessions describe the same kind of driving.

Pace and Competition

Pace covers same-layout lap times and repeatability. Expand a comparison group for its graph; other groups stay compact. Competition leads with recorded race history and shows what each position means. Metrics without eligible evidence are omitted from the main summary; Comparable results & coverage explains the gaps. A P1 ranked by fastest lap is kept separate from a finishing-position win. An unknown ranking basis stays unknown and does not remove the session's lap evidence.

Wins and podiums need a Race or Final, explicit finishing-position basis and final classification with the number of starters. Wins require at least two starters; podiums require at least three. Known DNF or disqualification outcomes remain in the eligible denominator; DNS does not. Fastest-lap P1 and top-three counts have their own denominators, with at least two and three ranked drivers respectively.

Open Comparable results & coverage to see separate layout, class, purpose, vehicle and ranking groups. Unknown classification is its own group, so a newly classified session may have fewer comparable earlier visits. Existing ambiguous result awards appear as Legacy result milestones. They remain part of the journal without certifying a win or podium.

An observed field rating describes a complete anonymous field snapshot. Ratings can be recorded after the session. Driver OS does not turn them into an expected finish or label a field strong based on unrelated tracks.

Read Progress in this order

1. Confirm the selected history. Clear filters for all driving, or narrow to a venue, exact track/layout, vehicle/fleet and timeframe. The selection follows you into the named detailed Progress tools.
2. Read the plain language overall summary before the chart.
3. Check how many tracks have repeat visits and which newer tracks are still baselines.
4. Compare representative pace and variation with the raw same-track session evidence still available.
5. Treat confidence and unavailable states as part of the result.

Home previews activity and venue history, with the most visited venues first and a route to the rest. Each venue keeps its recorded comparison contexts accessible, including ordinary visits, Practice, Qualifying and Race where present. A single-date context is a compact baseline; repeated comparable dates can support a small trend chart. These previews are not an overall pace score. Progress retains the wider history and full comparison evidence.

What the common states mean

• Not enough comparable evidence means the honest next step is another similar session.
• Overall pace direction counts first-to-latest changes inside each repeated track. Each line uses a percentage from that track's own best representative pace and is never joined to another track.
• More repeatable means lap-time variation narrowed after it was normalized by representative lap time at that track. It does not automatically mean the fastest lap improved.
• Current peaks counts repeated tracks where the latest representative pace matched that track's best. It does not compare lap seconds between tracks.
• Experience built summarizes visits, races, tracks and retained laps without treating volume as improvement.
• Baseline means that track has one visit, or not enough representative evidence, so it is kept visible without claiming a trend.
• Milestone marks a durable event in the saved record, not a prediction.

When real lap seconds appear

Choose an exact track in Driving View to switch Progress to its real best-lap seconds and same-track variation. Vehicle or fleet views also use real seconds when all matching history belongs to one comparable track; if they span multiple tracks, they stay normalized.

The optional saved AI analysis remains a separate same-track interpretation. It does not explain or replace the deterministic overall chart.

What to do with a pattern

Choose one observation you can act on. If the evidence is thin, make the action about collecting a cleaner comparison. If the pattern is stable, carry one focused target into Coach.

Review the supporting session Choose the next action Understand the calculations

Saved page layouts

In the wide review, expand Saved layout & optional Progress widgets, then choose Customize Progress to show, hide or reorder the existing observations, pace trend and route to Coach. These optional widgets preserve your saved choices and their existing calculations. The wide review’s main review, comparison evidence and retained coaching focus remain available. Save the layout to your account, or reset to default and save. A layout choice never changes a calculation or enables raw-time comparisons across different tracks.

Placements and field context

Competition shows recorded positions with field size, separated by purpose, layout, class, vehicle and ranking basis. One race is your baseline. Open the qualifying or practice group to follow those results too. Browse Events opens the same Event review available under Sessions → Events & session setup in C.

A result such as P9 of 12 is its imported placement. How results are counted explains any missing ordering method. K1 driver ratings are separate from result positions; anonymous ratings can describe an observed field but do not establish finishing order. Unconfirmed positions do not become wins or podiums.

Field + Time opens the most recent comparison group. Use its visible Compare sessions selector to switch groups on that page. Results stay within each group; limited or missing evidence remains labeled.

Review recording-start kart numbers

Matched recordings contains automatic time matches and explicit confirmed links. Expand it to inspect the race and original recording. For a time match, Review or change match → Confirm kart link retains the chosen association in your account. Automatic matches are recalculated from loaded history; opening the page does not save or change your records.

When a match needs your help, use Choose the race to link, select the official result and choose Confirm kart link. The picker shows date, venue, time and any unavailable-choice reason. The result can already have purpose/Event context: confirming the kart preserves that context, its notes and the original recording. Existing conflicting kart decisions are protected. A failed save keeps the picker open with an error; success shows Confirmed recording link.

Recordings within 45 minutes of a reported timing result appear first for review. The check uses recorded clock offsets and venue timezones, including daylight-saving changes. Same-date evidence with an unknown clock is labelled separately and never auto-matched. Automatic matching requires a unique recording within three minutes and no other result within eight minutes.

No timing day found is collapsed automatically. It means no matching day was found in loaded history, which can be incomplete; the recording is retained. If you recognize a test, choose Dismiss as test. Dismissed recordings → Restore to review reverses this. Dismissals are saved for this account in this browser; they do not delete the recording or raw evidence, and do not sync to other devices. Confirmed saved links are not dismissible as tests here; review their kart decision in the session.

Recording details opens the original record. This is separate from confirming the kart against official timing. A Watch/phone selection not yet delivered to the cloud cannot appear in this review. Selecting a kart without starting telemetry follows the native Quick Kart path, separately from saved recording context.

Relevant history filters

Venue and the core driving purposes stay easy to reach. More filters offers Track / layout, Vehicle / fleet and Timeframe when relevant. Timeframe ends on the newest recorded date in the selected driving history: choose All history, Last 30 recorded days, Last 90 recorded days or Latest recorded year. Undated records remain in All history. Event membership appears directly when your loaded history contains Events or an Event filter is selected; otherwise it is under More filters. Unused Endurance filtering is also available there. Recorded or selected specialist purposes remain accessible, including when a selection has no matching results. All-history views still include every driving context.

The two Home history charts

On Home, Beyond the last session pairs representative pace with lap variation for the same comparison group. Pace uses a zoomed scale; lap variation bars start at zero, with lower values meaning tighter lap times. Both use existing session medians for each recorded date. Open Values & calculation for the numbers and limitations. Missing values stay unavailable, and a single date stays a compact baseline. Changes in conditions or karts are not controlled, so the charts alone do not establish why a result changed.

A private goal and next visit in the notebook

The floating Coach follows the selected venue, day or session. Its deterministic guide explains available timing and lets you keep a private goal. It cannot infer a driving cause from lap time alone. You can mark a goal achieved; Home says that you marked it and lets you acknowledge it. After acknowledgement, the completion reminder retires after two weeks while the goal stays in Coach.

Add plan keeps a private visit, optional time, note and session format. A dated official event may supply starting details, but saving never books or shares attendance. The next planned visit supplies Home's countdown. Goals and plans follow your account only after confirmed saves; the floating conversation is temporary.

The sections below describe established coaching priorities and planning in More tools. Existing saved actions remain available independently of the notebook goal.

Start with one grounded observation

Open Coach after reviewing Sessions and Progress. A Coach link from a selected day, session or comparison group carries that evidence into main Coach. Navigation does not save an action. Choose one observation supported by the saved evidence, then turn it into a target you can recognize during the next drive.

Home keeps its seven history totals alongside the recent-activity bars: timed sessions, other sessions, recorded dates, Events, laps, venues and tracks. The filters narrow this view; counts and activity describe recorded experience, not improvement.

Your saved coaching priority stays compact and visible. Latest driving day and Worth a closer look come before the broader venue history so the next review is easy to find. Venue history starts with the places you visit most, with other venues still accessible. Each venue preserves its separate comparison contexts; a single recorded date is a compact baseline rather than an oversized one-point chart. Repeated comparable dates can show a small trend with a link to Progress. Raw lap times from different contexts are never joined together.

Suggestions and your priorities

Coach offers a few suggestions from journal-based rules. They are not AI-generated and are not saved until you choose Add to my priorities. That saves the exact target shown. Your first priority appears on Home; choose Make Home priority on another saved action to change it. Not for me hides a suggestion, and Restore dismissed suggestions brings it back.

A suggested sub-27 target counts separate Nashville visit dates, not individual laps. After two dates, the rule may propose three. Once saved, that target stays at three; new evidence updates its progress without moving the goal. Choose Mark completed to retain the outcome in History, or Archive to stop showing an action as active. Session planner remains available for a target you choose yourself.

Create a useful action

1. Name the next visit or session you are preparing for.
2. Choose one focus that can be repeated or checked.
3. Keep the target specific enough to review afterward.
4. Save it so Home can keep the next step visible.

Good actions describe behavior you control, such as holding a clean five lap block within a chosen range. Weak actions only say “go faster” without defining what a better run looks like.

Completed pace targets

A repeated lap-time target can count practice, qualifying and race sessions on the same layout, class and vehicle context. Several sessions on one date count as one visit. Home celebrates a completed target with a graphic using the existing achievement count. Got it clears the celebration; otherwise it lasts seven days from the first display in this account and browser. The achievement remains available in Progress and a saved coaching priority is not completed, archived or replaced automatically. Another browser has its own acknowledgement state.

Keep reminders useful

Timing-review cues offer a direct route to a flagged session and Mark reviewed once you have inspected it. The session's Mark date review reviewed action clears the same reminder for that date and comparison. Undo or Show again restores it. Clearing a cue does not remove evidence or mean its cause has been explained. Your retained coaching action stays visible until you manage it in Coach.

After the drive

When Home shows a new Race Day Review, open it for the complete post-visit story. Its Save focus to Coach action keeps you at the focus and confirms the save in place. You can inspect the supporting Session or open the relevant Track before deciding.

Return to Coach and record the outcome. Complete the action when the evidence supports it, mark it missed when it did not happen, or keep a short note when the session could not test it fairly. The outcome stays connected to the supporting session.

Where AI fits

Driver OS calculations and saved actions do not require AI. Eligible drivers may request a clearly labeled explanation of prepared evidence, but AI cannot change measurements, import a result or silently rewrite a plan.

What success looks like

Home shows one current action rather than a pile of generic advice. After the next drive, Coach preserves what you tried and what the evidence showed.

Review Progress first Read the AI boundary

Make the page work for you

On Home, expand Saved layout & optional Home widgets, then choose Customize Home. The optional widgets keep their existing calculations and saved visibility/order from your saved layout; The wide review’s main history, next review and retained coaching priority stay available. Coach keeps Customize Coach on its Overview. Show or hide the approved optional sections and use Move up or Move down to order them. Select Save layout to keep your choices in your account across browsers and devices. After the save succeeds, the editor closes and returns you to the updated page. Cancel leaves the saved layout alone.

Reset to default restores the recommended arrangement in the editor; choose Save layout to keep the reset. Your current journal or current action and essential evidence context always remain available. Missing evidence is explained in the list, and at least one optional section stays shown.

Quick Kart in the new notebook

In /driver, the floating Quick Kart control is available on desktop and phone. Your home K1 is selected first; change the venue when racing elsewhere so the capture uses the right local time. Enter the number and save while safely stopped. The current time is recorded automatically. Wait for the confirmed account-save message. This action needs a connection; the notebook does not claim an offline or simulated save.

Quick Kart shows up to three captures from today and yesterday. Choose Review captures & missing numbers in Karts for the full review, or open Karts → Review kart numbers. Unmatched captures remain available for 14 days; retained matched captures have their own expandable history. After a result arrives, choose the exact owned session and confirm it explicitly. Already-assigned sessions cannot be overwritten here. A browsing venue or nearby date alone does not establish a match. A capture is separate from a journal assignment until confirmed; incompatible, expired or conflicting evidence cannot become a successful match. You can correct a known session's kart directly in Sessions.

The sections below describe the existing web and native Quick Kart workflows in More tools, including their separate local-delivery and automatic-matching behavior.

Save and find a number

Open Karts in the desktop menu or More → Karts on a phone. Home also shows recent numbers for the current venue with Full kart history, Save kart number and Review saved captures. These actions use the existing Quick Kart sheet; saving a number never starts telemetry. The selected browsing venue does not assign an unmatched capture to a venue.

The floating Quick kart button is shown on a handheld browser with touch as its primary pointer and a screen at most 1024 pixels wide. It stays hidden on an ordinary mouse-based desktop browser. Native Driver OS capture is unchanged.

At the venue

1. Choose Save kart number on Home or Karts, or open the handheld Quick Kart shortcut.
2. Enter only the kart number you can see.
3. Save it before the run or when you are safely parked afterward.
4. Read the save status, then close the sheet when you are done. Saved on this device, cloud delivery and session matching are separate states. Offline delivery waits for a connection; an ambiguous match needs your review after results arrive. If the browser cannot retain the capture, the sheet reports that instead of claiming it was saved.

Never use a phone while driving. Quick Kart is designed for the moment before or after the run, not during it.

When the result arrives

Driver OS compares the saved kart-selection time with the venue race time. Where venue timezone evidence is available, the comparison uses absolute timestamps, including seconds, across timezone and midnight changes. Clearly supported matches attach automatically. If timing or order leaves a choice, the capture stays available for your review.

Matching rules

• A complete set of selections and races from one known visit can match in order when their times support it. Equal counts alone are not enough.
• With missing selections, only a clearly closest, noncompeting race can match automatically. The matcher leaves the missing race empty instead of shifting later kart numbers.
• A proposed match never overwrites a kart number entered directly on a race or a kart assignment you explicitly cleared.
• Ambiguous or competing captures stay unmatched. A conflicting venue kart number also needs review.
• Unmatched or test captures are removed on the first sync after 14 days.
• A confirmed kart number becomes part of the race journal.

The selection timestamp describes when you pressed Save Kart. It is not a lap-crossing timestamp. A venue result that supplies only minutes cannot establish second-exact alignment, even when the kart capture contains seconds.

What success looks like

The matched race shows the kart number in Sessions, so later comparisons can keep the machine context visible.

If no match appears

Open Quick Kart → Review unmatched kart captures after the results arrive. Each saved selection shows its capture time and nearby races, including the venue timezone and time precision. Choose the race you recognize and press Confirm race. Nothing is preselected. Reconnect first if you are offline.

The race records this as Driver-confirmed Quick Kart, preserving the original selection timestamp. Assigned or explicitly cleared races cannot be overwritten here; correct them directly in Sessions. If you forgot to save a selection at all, set the kart directly on the known race in Sessions.

The latest-capture card lasts four hours; unmatched captures remain available for review for 14 days. Native phone/Watch selections use the same time-and-order matching rules through their separate private delivery path. Matching retries when verified K1 results arrive and when the companion syncs. If a native selection still needs review, set the kart on the known race in Sessions; this web review does not recreate a missing native ledger entry.

A kart recovered from a verified Watch recording is labeled Verified Watch capture context. Its capture-start timestamp is distinct from the original selection time, which may be unavailable. Editing or clearing that kart in Sessions replaces the old attribution.

A saved number is missing from kart patterns

Open Karts → Saved kart recordings (the existing Progress → Karts by venue link still works) to inspect numbers retained with phone/Watch recording context. A unique eligible time match is labelled Recording time match; opening the page does not save a link. For other nearby recordings, Link to official timing → Confirm kart link retains the result you recognize. Existing conflicting kart decisions and links stay protected. A date alone does not establish a match.

Review recording matches and limitations

The separate phone/Watch selection inventory, where available, shows retained quick selections and their matching status. A selection still on a device is not visible in the cloud inventory until delivery completes. Missing from a pace chart does not by itself mean a kart number was lost. Only an actual timing-linked assignment contributes to that venue's pace comparisons.

Review the matched session Open troubleshooting

Is this a good or bad kart?

Open a number’s All recorded uses to inspect your result against each session’s recorded field, including the gap to the field’s fastest lap when supported. A complete anonymous field-rating snapshot may add context; it is not an expected finish or a calibrated field-strength score. Pace, consistency & comparisons retains exact-context personal comparisons and shared-date evidence. Missing or conflicting field evidence remains unavailable.

These observations help you decide what to investigate on a future visit. They cannot separate the kart from your driving, traffic, opponents, conditions or maintenance. A rental number may be reused or reassigned; it does not guarantee the same physical kart over time. Driver OS does not rank best or worst rental karts.

Your Driver OS account

The /driver experience uses your authenticated account's results. Driver name, home K1, confirmed notes, private plans and goals follow the account after saving. Temporary browsing and the floating Coach conversation remain separate. Changing your home venue never moves or relabels sessions.

Open the avatar menu for Profile, Settings, Help and Sign out. Profile is a full-width page for driver name and home K1. Your permanent username is shown as text. Completed setup is not repeated; an old setup link returns to Profile. Help opens in a new tab.

Settings → Privacy & account shows your verified sign-in details, age range and recorded notices inside Driver OS. Optional sensor collection and native source backup remain separate consent choices. A recorded cloud-storage choice is not proof that a device can upload; the backend checks current eligibility for each upload. Withdrawal opens a confirmation explaining its scope; cleanup may remain pending, and a retry is available when appropriate. Deactivated drivers can reach their own privacy and cleanup status from account recovery without loading racing history. Whole-account export or deletion remains a support request, not a self-service delete button.

Save failures and conflicts stay visible. Reload saved data (discard unsaved edits) replaces unsaved changes with the saved account state. Refresh uses a neutral loading shell while verifying the account. No private cached results appear before that check, and a denied access check clears the private view.

Community · Coming soon enables no live directory, friends, statistics sharing or messaging. The site owner's separate Owner workspace uses server authorization; a displayed name or email never grants access. Opening Owner does not modify race or kart history.

Other supported account experiences

The sections below document the earlier web interface and the native companion where those features remain available. Their layout, setup and browser-preference controls are not part of the new /driver Settings page; use the native Profile and Settings directions above for that experience.

Use a verified email to sign in. Your profile, imported results, manual journal context, saved plans and supported saved analyses follow the authenticated account.

The native app and browser keep separate sign-in sessions. Opening the browser from the native app does not copy the phone's refresh credential. Sign out retains its existing account-wide behavior: other sessions can require sign-in when they reconnect. Do not use sign-out to troubleshoot an offline recording; preserve its local evidence first.

Demo Tester accounts

The persistent Demo data indicator means driving records, vehicle examples, source summaries and saved coaching are fictional. Your sign-in, username and profile remain genuine. Demo Testers have no functioning inbound results address, raw telemetry upload, analytical sync or paid/live AI. Connections and Discover show simulated states, and synthetic sensor summaries never become accepted evidence.

The owner can reset the demo scenario while preserving sign-in, or reset onboarding and the scenario so you can repeat setup. An onboarding reset clears the driver name and home location; it preserves the verified email, username and legal acknowledgements. A reset also invalidates older tabs' saved work so they cannot restore the previous scenario. Reconnect and refresh if a reset occurred while you were away.

Deactivation preserves authentication but blocks access to the private demo. There is no casual Demo-to-Real switch. Conversion requires removing and verifying deletion of every synthetic record before real capabilities can be enabled.

Sensor storage boundaries

• Sensor Logger files are cached in the importing browser and retained in private account storage until that recording is deleted.
• Older native raw iPhone and Watch files stay in protected local application storage, are excluded from device backup, and survive sign-out until their exact cloud receipt is verified and receipt-first cleanup removes that device copy.
• The native cloud flags are false in the checked-in build. Only the explicitly signed Owner Internal archive may override private cloud delivery; analytical accepted-slice sync remains off.
• When private cloud delivery is enabled with separate consent, a private cloud copy can be retained for analysis and research even if its evidence is rejected or ambiguous. Delivery receipt, race relationship and quality remain separate facts.

Expanded internal recordings remain in private local storage. New eligible recordings can use expanded private cloud delivery when it is separately enabled for both your account and native build. Older full recordings need explicit authorization tied to the exact source and current consent; enabling future delivery does not authorize all retained history. Full iPhone copies remain retained after verified cloud recording; cloud deletion does not delete that local copy. Watch-to-phone transfer requires the same authorized account and a verified phone receipt. Review, export and exact local deletion are available in Advanced → Recording information. Signing out does not delete retained local recordings. These recordings are not accepted analytical data.

Deletion and consent are distinct

Deleting a local native file removes that device copy. Deleting an uploaded native record is a separate cloud action. While cloud deletion is pending, Driver OS hides that source from analysis but does not claim that retained database or storage objects are gone; use the available retry control or contact support if cleanup cannot finish.

Deleting one cloud recording targets that exact displayed source; a paired badge or race candidate never expands the deletion scope. Withdrawing private cloud delivery consent stops new source uploads and deletes or hides all uploaded complete native sources and their cloud metadata, while accepted slices remain unchanged. Withdrawing the underlying Sensor Data consent stops all native sensor processing and deletes or hides accepted artifacts, projections and complete native-source uploads. Neither withdrawal deletes Sensor Logger recordings, and whole-account deletion also requires separate storage cleanup.

Age boundaries

Self-service accounts are for people 13 or older. Teen Sensor Logger use is limited to motion-only files after the required attestation; a file classified as location or heart-rate is rejected as a whole. Native capture and sync are not offered as a teen workflow in the current internal build.

Saved page layouts

Home, Sessions, Progress and Coach layouts are saved separately to your authenticated account after you choose Save layout. They survive sign-out, browser restarts and signing in on another device. These preferences contain only approved section names, their order and visibility, plus update and revision metadata. They contain no race evidence, competitor names, AI output or behavioral click history. Signing out clears the layout from app memory; deleting the account also removes its saved page preferences. Reset each page with Reset to default, then Save layout.

Saved Race Day Review coaching

Where enabled for the owner, Race Day Review saves the validated analysis, its cited source relationships, model and version details, and saved time to that account. A prior answer remains marked outdated when evidence changes. Deleting a contributing source or the account removes its dependent saved analysis; operational usage metadata follows the separate private usage retention policy. Provider response storage is requested off, but provider security and abuse controls can still apply.

Account access

The owner can deactivate app access for Demo and Real accounts. Your sign-in, profile and retained records are preserved; access removal is not account deletion. New protected requests are denied after deactivation. Reconnect or refresh to see the current access status. Content already viewed, cached or downloaded cannot be recalled. Real access can be restored by the owner without changing the account type or granting new AI or native permissions.

Setup choices and recovery

Profile → Your driving choices reopens driving interests; Optional setup contains sensor and AI interests. Continue saves setup progress to your account. Unfinished choices also survive leaving and returning in this browser. When revisiting setup, Close setup returns to Profile and keeps those choices here without changing your saved profile. Your home city is used for suggestions without requesting a street address. Demo data-only resets preserve completed choices; onboarding resets repeat setup while keeping the existing username and legal requirements.

Local experience and review preferences

History filters, the simple-navigation preference, achievement acknowledgement and reviewed timing cues stay with this account in the current browser. They are presentation preferences, not changes to results, achievements, Event context or saved coaching actions. They do not sync to another device. Clearing browser storage can restore the reminders; a signed-in device starts its own seven-day achievement celebration when it first displays that achievement.

The separate Save layout controls remain account-synced. Home, Sessions and Progress expose them in Saved layout & optional widgets panels using your existing optional widgets and saved choices. The wide review’s required history, evidence and retained focus stay available. A local reminder acknowledgement does not save a page layout.

Home track and starting view

The optional home track and starting view are saved for this account in this browser. They are separate from your home city, temporary venue browsing and account-synced page layouts. Remove browser preference restores the existing opening behavior without changing your current view or driving history. Choose Home track or All venues for new tabs; existing defaults stay unchanged until you choose. Reload retains the current tab’s browsing context where browser storage is available. Preferences do not transfer between Dev and Production or to another browser or device.

Finding Profile settings

Profile groups settings into Identity & driver profile, App preferences, Connections & result emails, and Privacy & account data. App preferences contains navigation, driving interests, the tour, and the optional home-track starting view. Home city and home track remain separate choices. Saving a browser preference does not change the history you are currently browsing.

Coach in Driver OS

The floating Coach is a deterministic guide to selected evidence. It explains supported pace, variation, kart-use and field observations and lets you edit a private goal. Its conversation stays in the current tab. It does not infer a racing line from lap times or turn a note into a verified cause.

Open saved analysis & AI tools opens a native full-width page. Choose a recorded session to read its saved analysis, or use Progress analysis. Current saved answers restore without a model request; older evidence and versions are labelled. Source links, insights, limits and AI provenance remain visible. Eligible Generate, Update and Ask Coach buttons use the existing protected service and allowances only when clicked.

Plan explanations and Coach recaps remain separate requests and require supported evidence. They are not presented as durable saved history. Other historical detailed-tool and Race Day workflows described below remain preserved at their existing routes, but are not links from the new interface. No backend record or saved analysis is removed.

Floating Coach

The floating Coach stays beside the page while you navigate. Its calculated quick questions and matching saved AI do not trigger a new model request. On a phone, the panel can minimize so navigation remains reachable.

For the authorized owner, choose a Chat session, Check AI access, type a timing, consistency or result question, then Send to Coach. Chat stays pinned to that recorded session even if the page changes. Every question is independent; no conversation is saved. Only Send can use the existing shared monthly allowance. Broader progress, kart-cause, technique and unrelated questions receive bounded guidance. Sources, limits and AI provenance remain visible.

In the wide review, Follow the evidence → Saved analysis & session notes reads an existing Session answer in place. It keeps the whole source-session scope, source references, generated time, model, versions and current/stale status visible. The availability check only reads authorized saved information; expanding the evidence does not call the model. Notes and tags remain driver observations, not new AI conclusions.

Controls for requesting or refreshing saved Session/Progress analysis remain in the named detailed tools. Opening these tools does not grant AI access or expand the account allowance.

Selected evidence in main Coach

Opening main Coach from a day, session or Progress comparison keeps that selected evidence visible. It does not save a plan, complete a priority or submit a paid question. The floating Coach has its own explicit Chat session selection, which stays pinned while you navigate.

Start with Driver OS evidence

Lap times, representative pace, lap time variation, comparisons, plans, eligibility, confidence and timestamps come from deterministic Driver OS code. Review those values and their sources before asking for an explanation.

When an AI action appears

Model backed access is limited to explicitly entitled accounts and is not a general early access capability. Session and Progress tools run only after their visible request action. Opening Home, Sessions or Race Day tools does not start a new analysis. Race Day coaching requires its explicit Generate or Update action.

Every complete model answer carries an AI-generated label, evidence references and limitations. If those elements are missing, do not treat the text as a Driver OS AI explanation.

Temporary questions

A temporary protected question may include a bounded amount of selected session context, including a note when that context is part of the chosen request. The answer is not saved as Driver OS product data, although operational usage metadata is retained.

Saved Session and Progress analysis

Saved analysis uses a narrower prepared fact packet and saves the validated answer, evidence references, audit fields, version fields and model usage metadata to the account for that exact evidence.

If the evidence changes, the earlier result remains visible as stale until you explicitly request an update. An unchanged current result should restore without another provider request.

All provider calls request application response storage to be disabled. Provider security and abuse controls may still apply under the provider terms. Driver OS does not promise that the provider retains nothing.

Owner Race Day Review coaching

Where enabled for the exact owner account, Race Day Review shows AI coaching analysis inline. In the wide review, opening these tools reads an existing saved answer without a new model request. Choose Generate coaching analysis for a missing answer or Update coaching analysis for changed evidence. The official results must have settled for 30 minutes after their latest import or update, or the venue-local day must have ended. Opening early still shows the complete timing review immediately.

All six coaching sections expand into the page. Read the analysis, evidence links and source details using normal page scrolling.

The analysis is saved for the evidence it reviewed and restored on return without another model call. New results preserve the earlier analysis as outdated. Driver OS offers an explicit update after the next quiet period. A failed attempt does not retry automatically; Retry coaching analysis lets the owner try again within the same limits.

Each analysis must fit a maximum $0.02 reservation and accepted cost, a $1.00 monthly Race Day Review allowance and the existing account limits. If access, budget or provider availability prevents analysis, the deterministic review stays complete. Model, saved time, cited evidence and limitations remain visible. Saving the suggested focus is a separate action controlled by the driver.

What AI never replaces

AI does not receive complete raw email, complete sensor archives, GPS routes, heart rate or raw sensor channels. It cannot import or repair results, certify records, invent measurements, validate a weak sensor signal or silently change a plan.

Ranking facts stay fixed

Coaching uses the same deterministic ranking facts as Sessions and Progress. Session purpose, optional Event membership and ranking basis are separate. A numeric P1 or a session named “Race” cannot establish a win. Unknown basis remains explicit, and the model selects prepared claims rather than rewriting measurements.

Qualifying position does not establish the starting grid. Net positions gained needs the recorded start and classified finish in that race; it does not count overtakes or explain what caused the outcome. Changed ranking context makes older evidence snapshots stale. Owner-confirmed context currently uses deterministic review; it does not enable another paid coaching path.

Use the explanation well

Check every statement against the cited Session or Progress evidence. Keep one useful interpretation, then turn it into your own practical action in Coach.

Choose the next action Understand the numbers Review account and privacy boundaries

Saved Demo coaching examples

Demo Testers see precomputed, deterministic examples derived from fictional scenario records. The examples show their source references and limitations and are labeled synthetic. They do not call a model, incur AI usage or make claims about the tester's real driving. Event context preserves qualifying, race and stint distinctions; unsupported live Event AI remains unavailable.

Setup choices and recovery

The AI question during onboarding records interest only. You can change it in Profile → Your driving choices. Selecting it grants no AI access, accepts no consent, starts no analysis and creates no charge. Existing account approval, availability and usage limits still apply; pricing has not been decided.

Demo Testers with the race-day refresh can choose a suggested priority, put it first on Home, dismiss suggestions and mark priorities complete. These choices use fictional session evidence and do not call AI. Existing plans and saved work stay in place. Older Demo versions show the saved examples and Session planner while priority controls remain unavailable.

Venue context and selected evidence

The venue you are browsing limits relevant timing summaries. General saved goals remain available and are not rewritten when you switch venues. Direct Session and Event entries keep their selected evidence; a missing or unavailable session does not substitute unrelated Home history. Saved explanations must match their evidence and scope before reuse. Opening a venue, page or saved explanation never starts a paid request.

Notebook evidence and public references

All recorded laps remain visible alongside the retained subset used for pace and variation. Statistical exclusions describe a calculation decision, not an observed cause. Personal comparisons require matching owner, venue, layout version, class, fleet and purpose; visit summaries do not pool unrelated laps.

Field averages require the supplied comparable metric across the complete field. They average driver summaries, not every driver's pooled laps. US K1RS/RPM snapshots stay within their scoring year; missing scores and expected finishing positions are not reconstructed.

Public K1 tables show their checked date, exact scope and observed period. A rolling “Best of Month” table need not be a calendar month; an undated track record is labelled separately. These references cannot grant an official leaderboard position to your result. Lap-duration animation is illustrative uniform motion, not measured location or speed.

The broader calculations and optional research tools below remain available through More tools.

Official result

An imported result keeps official laps and available standings context. It remains separate from any public benchmark.

Published benchmark

A static track record and rolling leaderboard are different references. Each needs an exact track configuration, class, source link and retrieval time before comparison.

Driver OS calculation

Representative pace, lap-time variation, confidence and comparisons are deterministic calculations from saved results. Raw laps remain visible when an excluded lap is omitted from representative pace.

In All driving, Driver OS first calculates a representative pace for each race day, then expresses it as a percentage from the best representative pace recorded at that same track and in the same racer class. A smaller percentage is closer to that track's best. Separate track lines share the percentage scale but are never connected.

Overall repeatability expresses representative lap-time variation as a percentage of representative pace at each track. Choose one track in Driving View when you want the original seconds. A track with only one usable visit is labeled as a baseline instead of being called improvement.

Experimental sensor estimate

Route, lap, braking and motion labels describe available device evidence. They are not official timing, calibrated vehicle telemetry or a proven cause of performance.

Race Day Review

Each review keeps one exact venue, recorded layout, class and layout version together, using venue-local dates and official timing. Long gaps or unresolved timing can split a visit or require review. Different layouts never share a lap-time calculation.

The day’s representative pace is the middle value of its available per-race competitive averages. Typical lap variation is the middle of the retained per-race variation values. The longer personal baseline uses the middle of prior comparable visit values, so one unusually long visit does not outweigh every other visit. Lower seconds mean faster pace and tighter variation.

A lap is called clean or affected only when individual-lap evidence says so. Excluding a slow lap from representative pace does not prove traffic, a yellow flag or a driver error. Full-lap spread includes all retained official laps and appears under its own disclosure. Cloud-saved conditions are contextual; device-local tags and notes are not part of this review or its AI packet.

Earlier journal results with unresolved official provenance can preserve a faster personal best, but cannot establish a new official best or fill a missing comparable visit. The review explains when this limits the history comparison.

The usual best lap is the middle of the best laps from earlier comparable visits; it is separate from your all-time personal best. Podium and win trends show the share of known finishes in each visit. Field-strength trends average the observed field ratings, giving each rated race equal weight. Fastest-lap trends appear when verified comparisons exist, include ties and leave missing comparisons as gaps. A P1 finish does not by itself prove the fastest lap; that label and a zero lap-time gap require an explicit field-best time.

Highlighted slowdowns show both the actual lap time and how much longer it was than a usual lap. Recovery shows the following lap and the reduction in time. These changes do not establish what caused them. The evidence notes are intended for every driver, including those new to racing.

Reconnecting Driver OS

Refreshing /driver shows a neutral loading shell while the account and saved results are checked. It does not replay onboarding or show another account's cached data. If the check fails, Try again reconnects; Account & privacy remains available for your own consent and cleanup status when driving access is paused.

Save errors stay visible. Reload saved data (discard unsaved edits) replaces the current draft with saved account data, so copy unsaved notes you need first. A partially saved username is permanent; follow the recovery message instead of choosing another.

Use Settings → Result email connections for email setup, activity and received history; Settings → Privacy & account for account choices. Help opens a new tab. An empty history is normal for a new Real account; missing lap, field or score evidence is not filled with invented values.

The sign in email did not arrive

Confirm the address, wait a moment, check spam and request one fresh email. Use only the newest secure link or one time code. Older messages stop being valid after a new request.

The secure link expired or opened on the wrong device

Return to the sign in page and request a new email. If you are signing in from an installed Home Screen app, enter the newest one time code shown in the email.

The native email link or web handoff did not complete

Use the newest email on the iPhone that requested it, then choose Open Driver OS if offered. The email code is still a fallback. Do not reinstall, sign out or delete recordings to fix a connection problem. Wait until any recording or recovery has finished before trying to change accounts.

For a native-to-browser link, reopen it from the native app if it expired. Check the account shown before continuing. If the service is unavailable, use the ordinary web link and sign in there as usual; the phone keeps its session and recordings.

I verified my email but still see approval status

Driver OS is invite-only. A verified account without an active owner invitation cannot open private data. Use the public interest signup if you have not been invited. If the owner already invited this exact email, refresh or sign in again; one Demo Tester or Real Tester invitation is sufficient. Repeating signup does not add approval.

Home says my profile is incomplete

Open Profile and complete the required driver name and home location. K1 forwarding and Sensor Lab are optional and should not block the core journal.

A forwarded result is not visible

Open Connections → K1 Email, check the delivery/save status, then check the date and venue filters in Sessions. Use Report a problem if the result is still missing. A processing delay is a reason to investigate before forwarding again; earlier history is not automatically reprocessed.

A manual import failed

For an interrupted new upload, select the same file again. Driver OS does not retain the raw upload, and a completed matching result is reused. If the import says Needs review, use the private problem report; repeating an unsupported file does not repair its format.

Progress is empty

Open Sessions and confirm you have comparable saved evidence for the selected range and scope. One isolated or unrelated result may be correctly insufficient for a trend.

Quick Kart did not match

Confirm that the result has arrived and that the capture time is close to the intended race. If several races are equally plausible, enter the known kart number directly on the correct race.

In the wide review, also check Progress → Karts by venue → Unlinked recordings. A recording-start kart number can be retained in a standalone session context without a known venue or official-result link. This account-wide inventory remains visible under venue filters. Open its editor and inspect the saved context before linking a result. The app cannot safely assign a venue or race using only a date or a familiar kart number.

Retained phone/Watch quick selections appear in a separate inventory where available. A cloud inventory failure is not proof of missing device data. Do not delete or recreate recordings to make a pace chart look complete.

A Sensor Lab chart is empty

Read the chart’s empty state. It distinguishes a missing channel, unavailable retained source, failed quality check and a lap whose timestamps do not overlap the signal.

I cannot find a phone or Watch race

For expanded recordings, open Advanced → Recording information in the iPhone app. Complete local copies stay retained. Eligible new recordings and explicitly authorized older full recordings appear in web Sensor Lab only if separately eligible for expanded private cloud delivery and fully verified. Uploading and Verifying cloud recording are not completion. For an interrupted upload, return to the iPhone app when connected and use Retry if offered; the full local source remains retained. If the Watch has not transferred its source yet, keep both apps on the same authorized account and reconnect normally. Do not sign out, reinstall or delete evidence to force recovery.

For older cloud-backed recordings in Sensor Lab, use Driver OS iPhone, Driver OS Watch or Paired sources, then check the page range and use Next for older recordings. A source with a supported official-time association has Open race or Open race windows. The Race-linked session selector includes native sources even when their quality is rejected or unproven. Standalone bench tests, missing official timing and competing race intervals do not receive a race association.

Native quality reviews are temporary in this release. Reloading clears the review result, not the cloud recording or official race; select Review quality to calculate it again.

A native upload or deletion is still pending

Keep the signed-in companion open with a usable connection. An interrupted or unverified upload remains on that device for retry. Receipt verified means the exact private cloud record and object are durable; it does not mean the source passed quality review, matched a race or became analytical evidence.

If Sensor Lab says source deletion is still finishing, the private cloud source stays hidden from analysis while cleanup is pending, but deletion is not yet complete. Use Retry source deletion when it is offered. If the state persists, use the support, privacy and legal contact route.

The route is beside the visible lane

The route is an unsnapped GPS trace. Normal device accuracy and indoor reception can move the line by several feet or meters.

The journal looks stale

Open Profile, then Data and Sync, and refresh. If offline, the last account bound saved journal remains readable until the connection returns.

A Help link opened the wrong topic

Use the topic navigation or a stable article URL. Legacy #topic links and the complete guide’s ?all=1 route remain available for compatibility.

Saved page layouts

On Home, Sessions or Progress, first expand that page’s Saved layout & optional widgets panel to find Customize. If a layout says it could not be loaded, open Customize and choose Load saved layout before editing. If another device changed that page, load its current layout and make your choices again. A failed save never claims success; the page keeps its last confirmed layout. A freshly signed-in device loads the account layout, and opening Customize refreshes it. Cancel discards an unsaved draft.

An edit loses its place

Tags, notes and local display controls should keep their surrounding section open and remain in view. Background updates preserve unfinished fields for the current account and screen. Opening another race or navigating to another page starts that screen’s normal state. A validation error may move focus to the field that needs attention.

If a control still jumps away, use Support to name the page and action. Do not include private notes, recordings or sign-in details.

Account access is deactivated

The owner has removed this account’s app access. Your sign-in and saved records are preserved. Contact the owner if you need access. Signing in again does not bypass deactivation.

Setup choices and recovery

If setup cannot save, check your connection and retry. Back, refresh and signing in again preserve this account’s saved steps. No fictional history should appear in a Real account. If a Demo scenario cannot finish preparing, use the existing Refresh access control; do not request another invitation or reset the account yourself.

K1 import status checks

Use the paginated K1 email activity table to scan received times and statuses, then expand a row’s Details before choosing its result link or Report a problem. The owner’s authorized import and private-report queues are separate paginated tables; parser, adapter, generation, reason and alert details remain available per import. On smaller screens, scroll within the table to see all columns.

Connections → K1 Email separates delivery, complete saving and display for new imports. Earlier imports retain their history and are labelled accordingly. A format, venue or local-time warning requires reviewed evidence, not a guessed value.

If a result is saved but has no display confirmation, open its Sessions lap view and check the date, venue and current filters. Display confirmation only records that the expected lap component rendered. If the result is still missing, use Report a problem and consent to sharing its diagnostic metadata. The owner receives only the report and linked import information. Background checks create in-app health alerts; real email notifications and original-email reporting uploads remain disabled.

A session says Unclassified, or its day colors differ

Select the session in C and choose Set session purpose to enter known context. Unclassified means the purpose was not recorded; it does not mean lap timing is missing. Do not choose Race just because the timing provider calls every run a race.

Select Arrive & drive for an ordinary visit with no Event. Select Practice for practice within a chosen race-day Event. These are separate choices. When a timing result is selected, known name/date/location details are prefilled; you can save only the context you know and return to C. An older saved Practice role without an Event displays as Arrive & drive; an absent role remains Unclassified.

Purple and amber can describe observed best laps within a visit even when matching purpose/class is unrecorded. Read the scope note. Green needs eligible recorded result context and does not appear just because a session has the quickest lap.

Open detailed tools provides additional editing and comparison tools. Return to review restores your selection. The earlier experience switcher is retired; remembered A and B choices open the wide review without resetting saved filters or widgets.

A reminder disappeared, or reappeared on another device

Got it hides an achievement celebration, while Mark reviewed hides a timing cue. The achievement and original sessions remain available. Use Undo immediately or Show again in the reviewed-cues section. An achievement celebration also expires seven days after its first display in that browser/account. These states do not sync across browsers; new evidence can create a new cue.

Inside a flagged session, use Mark date review reviewed. It clears the same reminder as the overview action, for that date and comparison. The timing details remain expandable and offer Show date review again.

Home seems to omit a familiar venue or session type

Check the venue, Event and purpose filters first, then More filters for exact track/layout, vehicle/fleet and timeframe. Clear those selections for all history. The Home history preview starts with frequently visited venues and keeps the rest accessible. Within a venue, expand its other contexts to find Practice, Qualifying, Race or ordinary visits when those purposes are recorded. Distinct layouts, classes, fleets and purposes cannot share one pace line. One-date groups stay compact baselines rather than claiming a trend. Progress retains the full eligible history.

Saved session evidence opened another layout

In the wide review, expand Follow the evidence → Saved analysis & session notes to read existing evidence on the same page. Source/session scope, limitations and saved AI provenance remain visible. Open detailed tools provides additional editing and comparison tools, with Return to review to restore your place.

The Real driving notebook

The /driver notebook provides Home, Sessions, Progress and Karts with a floating deterministic Coach and Quick Kart. It reads owned evidence and saves supported private notes, plans, goals and preferences. Existing onboarding eligibility still applies; the home-venue path does not require a city.

Community is visible in the main menu and marked Coming soon. The authorized site owner has a separate Owner entry for the existing protected admin controls. Public venue and leaderboard references are dated snapshots. Lap replay is illustrative motion derived from durations. Model-backed AI, imports, native tools and broader features remain in More tools, with the boundaries below unchanged. Demo accounts retain their separate fictional experience.

Available in early access

Approved accounts can use the private journal, supported result imports, Sessions, Progress, Garage, Tracks, Quick Kart, Discover and deterministic Coach foundations.

Still being tested

• Sensor Lab and Race Fusion are source-neutral, read-only research surfaces and do not overwrite official results. Rejected and ambiguous sources remain visible but non-analytical.
• The native iPhone and Watch companion remains internal-only. The checked-in native cloud flags are false; only the explicitly signed Owner Internal archive may override private cloud delivery, while accepted-slice sync remains off. This is not a public native release.
• Expanded internal recordings can be inspected in Recording information. Expanded private cloud delivery requires a separate native-build and account enablement for new recordings or explicitly authorized older full sources; it defaults off and retains the full iPhone source. Analytical promotion and Health access remain off. Per-race setup remembers phone/Watch defaults. Updated captures distinguish the shared race stop from acquisition end and report phone non-contribution when known. Original recordings remain unchanged. Physical battery, long-duration continuity and transfer performance are still being tested.
• Sensor-derived scores and automatic conclusions are not treated as settled product behavior.
• Model-backed AI is limited to explicitly entitled accounts and runs only after a visible request.
• Some provider connections remain unavailable until a dependable, authorized path exists.

Driver OS is independent and is not affiliated with or endorsed by K1 Speed, Sensor Logger, Apple, Google, or the venues and timing providers represented in imported data.

Venue context in the notebook

Your account's home K1 and the venue you are browsing are separate choices. Venue details shows saved catalogue information, reviewed names, timezone and official links. Viewing another venue does not change your home preference. A listing does not guarantee opening hours, all configurations or every email format.

Public location and track references are dated snapshots. Follow the official link before a visit. Garage, track following, owned vehicles and broader discovery remain in More tools, as described below.

Find somewhere to drive

Use Discover with your saved home area for nearby options, or switch to Trip mode for a temporary destination. Follow a place you want to keep without pretending you have already driven there.

Always confirm hours, booking requirements, age or height rules and track availability with the venue before traveling. A directory result is not an endorsement or a promise that an event is available.

Keep places in Tracks

Tracks combines followed places and venues from your saved driving history. When the first supported result arrives, Driver OS should update the existing place rather than create a duplicate. In the wide review, View sessions opens that exact track/layout’s history; the selection remains visible under More filters and can be cleared for all history.

For recognized K1 tracks, View official track map opens the verified official track page in a new tab. Separate View weekly best times and View 30-day best times links appear only when the exact venue, layout and racer-class page is known. Otherwise, the card explains what is unavailable and retains the official directory link where known.

These are external K1 pages. Driver OS does not load K1 track artwork or leaderboard results. K1's current layout or lists may change; your saved official timing, history and personal best remain in Driver OS. An automatic source connection remains disabled pending written permission or a supported connection.

Optional home track

Driver OS offers Home track & starting view in Tracks and Profile. Choose a track from your recorded venues and optionally start new tabs at Home track or All venues. Until you choose, Driver OS keeps your existing view. Your home city remains a separate Discover preference.

The Venue control carries the browsing context across Home, Sessions, Progress and Coach. Summaries and evidence suggestions use that context; newer visits elsewhere remain linked. Direct Session and Event links open their own evidence. Saved coaching priorities remain available across your journal. Venue changes do not rewrite history, goals or your opening preference.

Driver OS saves the opening preference for this account in this browser only. Reloading keeps the current tab's view when browser storage is available. It does not sync between devices, and clearing browser data removes it. Layouts, class and purpose still determine which results can be compared.

Keep machines in Garage

Use Garage for owned karts, cars and other machines that belong to your driver record. Rental fleet activity stays connected to the venue and should not appear as an owned vehicle. Opening a vehicle or fleet’s history in C keeps that vehicle/fleet selected; clear it under More filters to return to all driving.

In session setup, expand Change vehicle context to choose between Rental vehicle, an account-owned Garage vehicle, and a Temporary/team/borrowed vehicle for the individual session. A temporary vehicle does not enter Garage automatically. Its description may initially be unknown; optional car number and team details can be added later.

If a temporary vehicle later belongs in your permanent Garage, open its details and explicitly choose Save to Garage with a Garage name. This creates one permanent entry without rewriting the context of earlier sessions. Synthetic Demo vehicles cannot use this conversion path.

Use Edit to correct an owned vehicle's name or type without changing its existing session links. Delete requires a separate confirmation and is available only when no session still links to that vehicle. If a vehicle has linked history, open its linked sessions and reassign them first.

What success looks like

Each session keeps the correct venue, layout and machine context. You can move across rental karting, karting, sim racing and track activity without comparing unrelated raw lap seconds.

If a place or machine looks duplicated

Check the exact venue, layout and ownership type before changing anything. A followed destination, a venue from imported results and an owned machine represent different kinds of context.

For two accidental copies of the same owned machine, keep the one with linked history and delete the unlinked copy. Driver OS also blocks a new owned vehicle when its name and type exactly match one already in Garage.

Prepare the next action Review a session

Setup choices and recovery

Setup can suggest a few existing directory places after you choose a city and interests. No match does not block setup. Owned karting and car interests can add one optional vehicle at Finish using the same Garage as the rest of Driver OS. Rental drivers can skip Garage. Later preference edits do not recreate deleted vehicles or restore places you unfollowed.

Open More → Connections. If Sensor Lab is not already visible, expand Optional tools and choose Open on Sensor Lab recordings. Existing recordings, saved sensor interest or consent keep it directly visible. Sensor interest is also available in Profile → Optional setup; interest does not grant consent.

Sensor Logger file import

Secure the phone or Watch before driving and start or stop only when parked or outside the vehicle. Export one Zipped CSV recording at a time. The selected file is cached in this browser and retained privately in account storage until you delete that recording.

Location supports route, speed and repeated-loop estimates. Accelerometer and gyroscope channels provide relative motion only. Heart rate is optional and is not required for driving analysis.

Choose the Sensor Logger recording mode that matches the devices you secured before the session:

• iPhone Only Mode records the mounted phone channels.
• Phone & Watch Mode combines the mounted phone with a worn Watch in one integrated workflow.
• Watch Only Mode records the worn Watch when no phone recording is available.

Keep the exported channels together. Driver OS uses their timestamps and device metadata to distinguish phone, Watch and combined recordings; it does not treat one device as if it measured the other.

Driver OS native companion

The iPhone and Watch companion is internal-only. Private cloud delivery requires an enabled internal build, account eligibility and separate consent. It is the destination for complete recordings used in analysis. Native release defaults remain off. Only the explicitly signed Owner Internal archive may enable the private cloud delivery override; accepted-slice sync remains off. This is not a public native release.

Older native recordings retain their existing private cloud delivery behavior. Private cloud storage has its own consent. When that consent and the Owner Internal override are enabled, a new raw phone or Watch source may be retained privately for analysis and research even when it is rejected or ambiguous. Cloud delivery does not accept the source, link it to a race or turn it into an analytical slice. Idle, walking, stationary, removed-Watch, unusable and ambiguous recordings do not become accepted analytical evidence.

For those older recordings, the companion keeps a local copy until the private cloud receipt is verified. Only then can receipt-first cleanup remove that exact device copy. If upload or cleanup is interrupted, the local copy remains available for retry; unrelated recordings must remain untouched.

Expanded internal recordings

Expanded internal builds record supported motion, magnetic field, compass, attitude, altitude and movement context in a private local recording. Race telemetry controls motion collection; Location is separate. Heart rate is unavailable and Driver OS does not request Health access. A missing or denied individual sensor does not stop the other available channels.

Use Start race, Stop race, optional Kart number, and Cancel recording while safely stationary. Open Advanced → Recording information on the iPhone to verify retained observations and inspect channel availability, permissions, sample rates, gaps and errors. The view can prepare a private export or confirm deletion of that exact local recording.

Each new Start opens Recording setup on the device you use. Review the remembered phone and Watch choices, adjust placement, wrist, motion or GPS if needed, then choose Confirm & start. Your confirmed choices become the next defaults and stay attached to that race. Canceling the review starts nothing and keeps the previous defaults. The receiving device uses the same confirmed setup without a second prompt. Update both apps and open them once before using this setup together; remembered compatibility allows later offline use.

Turn both motion and GPS off for a device you want excluded. Selecting both devices requests both sources; verify their actual recording state before locking the phone. A force-closed or unavailable app may not contribute sensor data. Recording information distinguishes verified saved files from sensor quality and reports invalid sample timing without changing the original observations. Updated internal recordings preserve the actual acquisition end and the shared race stop separately. Full-source diagnostics include the complete recording; the recorded race overlap is a separate derived view. A late or failed phone start can produce an explicit no-contribution result.

Expanded recordings stay local unless expanded private cloud delivery is separately enabled for the native build and your account. A Watch recording must first transfer to the paired iPhone and receive its exact verified receipt. That phone receipt proves transfer to the iPhone; a separate receipt verifies cloud storage. New eligible, finalized recordings then upload through the iPhone. An older full recording requires explicit authorization for that exact source under the current consent. Limited previews remain excluded.

Ready to upload, Uploading and Verifying cloud recording are unfinished states. Stored in cloud requires every part and the exact final receipt to be verified. Interrupted uploads remain local and can retry when the iPhone app is available again; background completion is not guaranteed. Expanded local copies remain retained after verification. Cloud delivery makes the full source available for analysis. It does not promote the source into accepted telemetry or enable accepted-slice sync.

In the compact native Sessions screen, choose the optional Event, Session type and vehicle for the next recording, or create an Event. Open full Sessions in Driver OS uses the existing signed-in web handoff for history, edits and comparisons. Finish the active recording before opening the web app or changing its context. Event selection and recording remain available offline; web handoff requires connectivity.

Indoor metal and motors can distort compass readings. Calibration and heading accuracy remain visible; a repeated shape is not proof of kart heading, steering, a racing line or lap timing. Walking and step information describe device movement, not race performance. Actual channel support and continuity still require physical testing.

Safe operating boundary

• Mount devices before moving.
• Never interact with a phone or Watch while driving.
• Treat routes, speed, braking and motion labels as estimates.
• Official timing remains authoritative.

Using the companion at indoor K1 races

Continue using it for kart context and optional recording when that is convenient. Save the kart number while safely stationary before each race, wear the Watch, and identify whether the phone is mounted, carried, stationary or excluded. Check the assignment in Sessions after the official result arrives.

Recording every indoor race is not required for official-timing analysis. Current native motion evidence has not established a useful lap-performance measurement, and a stationary phone does not measure the kart. More ordinary recordings can document delivery reliability, but they do not replace independent lap-crossing timing and separately labeled idle, handling, staging and racing intervals. A controlled validation visit remains a separate decision. Outdoor GPS has its own future accuracy and reliability gate.

Setup choices and recovery

Onboarding saves sensor interest only. It never turns on sensor processing or private cloud delivery. Review their separate consent controls in Connections → Sensor Lab. The native companion remains private testing with no public download; web eligibility does not guarantee a TestFlight invitation. Accounts aged 13–17 cannot use native capture.

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.