The mapping
| U.S. vehicle rule | What it does | Physical AI rule | Articles |
|---|---|---|---|
| FMVSS 100 series, crash avoidance: brakes (135), stability control (126), automatic emergency braking (127) | Prevents the crash | Detect people, then slow or stop before contact; stay stable | 9, 10 |
| FMVSS 200 series, crashworthiness: occupant crash protection (208), interior impact (201) | Limits injury during the crash | Limit force and pressure on contact; soft, rounded, yielding surfaces | 13, 14 |
| FMVSS 300 series, post-crash: electric-vehicle shock and electrolyte protection (305) | Limits harm after the crash | Safe state after an event; battery and electrical isolation; nobody left trapped | 11, 17 |
| Lamps (FMVSS 108) and minimum sound for hybrid and electric vehicles (FMVSS 141) | Makes presence and intent known | Light, sound and speech signals before and during motion | 7 |
| Theft protection and rollaway prevention (FMVSS 114); accelerator control (FMVSS 124) | Prevents unauthorized or unintended motion | Checked identity before start; no motion on a fault | 8, 17 |
| Manufacturer self-certification (49 CFR Part 567) | The maker certifies each vehicle to the standards | The maker certifies each unit to the Safety Principles before shipment | 34 |
| Defect report within 5 working days and a free remedy (49 CFR 573.6) | Gets unsafe vehicles fixed in the field | Defect decision, fleet hold, free fix | 11, 21 |
| Event data recorders (49 CFR Part 563) | Standardizes the data captured before a crash | A robot event recorder | 22 |
| NHTSA Standing General Order | Requires crash reports when driving automation was engaged | An incident report whenever autonomy was engaged | 22 |
| SAE J3016 levels, operational design domain, minimal risk condition | Says who is driving and where the system may operate | Autonomy levels, operating envelope, safe state | 3, 9 |
| State driver licensing and vehicle registration | Ties each driver and vehicle to a record | Enrolled operators and identified units | 8, 19 |
FMVSS 127 has a September 2029 compliance date and was still under court challenge in April 2026, so it serves here as a model, not settled law.

Comments
Comments are open for 60 days from publication. Comments posted here are public once Dunster Physical AI has reviewed them. Comments and emails are not treated as confidential, and Dunster may use them to improve the Safety Principles. Please don’t send patient information or anyone’s confidential material. To raise a safety or security concern privately, email info@dunster.ai.
No comments on this page yet.