Public Comment

New Jersey is considering rules for autonomous ride services, including testing mileage, safety drivers, insurance, accessibility, and vehicle sensors such as lidar. Some proposals use sensor redundancy as a safety floor. Developers argue that rigid technology mandates can freeze today's engineering choices into law, while safety advocates argue that companies should prove performance before carrying passengers without a human driver. An operational design domain defines where and under what conditions an automated system is intended to work. The state must decide whether safety should be demonstrated through prescribed equipment, measured outcomes, staged deployment, ordinary traffic law, or a future federal framework. Robotaxis should have to prove they are safer than a novice experiment, but the law should judge results instead of picking a favorite sensor forever. Start small, publish the evidence, and make the company responsible when things go wrong.

What proof of safety should robotaxis owe New Jersey?

Overall results

1
56% support · excluded by 6%
7

Crash, intervention, reporting, insurance, and cybersecurity thresholds measure the outcome the public needs while allowing safer technology to evolve.

2
55% support · excluded by 6%
1

Geofenced service with safety drivers lets regulators observe real operations and expand only after the system meets published milestones.

3
49% support · excluded by 11%
1

Waiting avoids a patchwork in which each state's technical rules make nationwide deployment more costly and confusing.

4
44% support
7

Redundant sensing and substantial supervised mileage establish a concrete floor before a vehicle carries the public without a human backup.

5
44% support · excluded by 11%
1

Federal manufacturing rules and existing traffic liability can cover automated vehicles without a separate state approval bureaucracy.

About the author