Research Note

Automated Driving Claim Evaluation Framework

An automated-driving claim is incomplete until it names the system, version, dynamic driving task, human role, fallback, operational design domain, remote assistance, veh

Aug 4, 20262 min readBy Dalton Anderson
In this article

Automated Driving Claim Evaluation Framework

An automated-driving claim is incomplete until it names the system, version, dynamic driving task, human role, fallback, operational design domain, remote assistance, vehicle, jurisdiction, permit, evidence, and current availability.

NHTSA distinguishes Level 2 advanced driver assistance from Level 3 through 5 automated driving systems. In Level 2, the driver remains responsible, monitors continuously, and must be ready to control steering, braking, and throttle. A mature ADS performs the full dynamic driving task within a defined domain.

Tesla's current support page describes FSD Supervised as an advanced driver-assistance feature that requires an attentive driver and does not make the vehicle autonomous.

Claim-completion record

ElementRequired answer
SystemProduct, version, hardware, software, vehicle, and date
Driving taskSteering, acceleration, braking, detection, response, and planning performed
Human roleDriver, monitor, fallback-ready user, passenger, remote assistant, or supervisor
DomainRoad, geography, speed, weather, light, map, traffic, and other constraints
FallbackHuman takeover, minimal-risk condition, stop, or other response
AuthorityJurisdiction, permit category, exemption, reporting, and effective date
EvidenceExposure, interventions, crashes, scenarios, methodology, and limitations
AvailabilityTest, pilot, employee access, invited users, public service, or consumer feature

NHTSA crash reports have exposure, duplicate, reporting, classification, and comparability limits. A count without miles, domain, severity, reporting scope, and methodology is not a safety comparison.

California DMV separates safety-driver testing, driverless testing, and deployment. A private event ride or company filing is not a deployment permit.

Sources

Follow the evidence.

  1. ir.tesla.com: tsla 20251231 genir.tesla.com
  2. nhtsa.gov: automated vehicles safetynhtsa.gov
  3. dmv.ca.gov: autonomous vehicles program permit resourcesdmv.ca.gov
  4. open.spotify.com: 40qV14aYmmoYMkcQdIO21eopen.spotify.com
  5. ir.tesla.com: tsla 20260128 genir.tesla.com
  6. nhtsa.gov: standing general order crash reportingnhtsa.gov
  7. nhtsa.gov: voluntary safety self assessmentnhtsa.gov
  8. tesla.com: AItesla.com
  9. tsapps.nist.gov: get pdftsapps.nist.gov
  10. faa.gov: activity archivefaa.gov
  11. daltonanderson.net: elon musks big bets starship teslas ai fleetdaltonanderson.net
  12. faa.gov: spacex starshipfaa.gov
  13. ir.tesla.comir.tesla.com
  14. tesla.com: we robottesla.com
  15. daltonanderson.ghost.io: elon musks big bets starship teslas ai fleetdaltonanderson.ghost.io
  16. tesla.com: fsdtesla.com
  17. esto.nasa.gov: trlesto.nasa.gov
  18. spacex.com: starship flight 5spacex.com
  19. nist.gov: autonomy levels unmannednist.gov
  20. youtu.be: c6yeP cvRzwyoutu.be

From this episode

Two useful next steps.

Research Note · 1 min

Tesla We Robot State Record

Tesla's October 2024 We, Robot event should be maintained as three product records.

Article · 1 min

Tesla We, Robot: Cybercab, Robovan, and Optimus

Track what Tesla revealed at We, Robot and separate Cybercab, Robovan, Optimus, FSD Supervised, Robotaxi service, production, permits, and forecasts.

Return to the episode