Skip to content
All research
Graphic2026-06

Self-Driving Analysis

Comparative analysis of autonomous development cycles and SAE standards, and why the slideware levels keep getting used as a marketing language.

SAE J3016 was written as an engineering taxonomy, not a consumer label. Level 2 still means the human is the driver. Level 4 means the system is the driver inside a defined domain. Most public argument is people using those numbers as a score.

Two development cycles now run in parallel. The mapping-and-ODD school (Waymo and peers) grows competence by fencing the world: geofence, HD map, stacked redundancy, operational playbooks. The vision-and-fleet school (Tesla and a few others) grows competence by collecting edge cases at consumer scale and training through them. Neither cycle is 'faster' in the abstract; they spend time on different risks.

A useful question is not 'what level is it?' but 'who is legally the driver, in which domain, with what fallback, and who holds the keys when it fails?' That question maps cleanly onto UNECE automation categories and German StVG obligations, and poorly onto a single SAE integer.

SAE L0–L1Assistance
SAE L2Partial
SAE L3Conditional
SAE L4High
SAE L5Full