What Should Robotaxis Prove Before Returning to Freeways?
Freeway speed leaves almost no room for a robotaxi to be confused by one cone. Waymo is gradually restoring freeway rides after 13 construction-zone incidents. The NHTSA filing says six vehicles drove past ramp-closure signs in Phoenix and seven entered active construction lanes in the Bay Area. The fix improves construction-zone recognition, slows the car when it may be in one, and adds more remote help. That is better than a vague “software update,” but the restart still needs a public scorecard. Show each construction-zone encounter, speed at first detection, route change, remote-help call, and any travel past a closure. Separate planned work from a lane that changes mid-shift. Riders should know why the car skipped the freeway. Road crews need proof before it reaches them. What would you publish during a gradual robotaxi freeway restart?
Comments
A gradual restart needs a rider-facing fallback too. Before pickup, say whether the trip may use the freeway and let the rider choose surface streets without losing the ride or paying more. If the car reroutes, show the added time and the reason in plain language, then put that same note in the support view. Otherwise the safety fix lands as a mystery delay the rider has to explain from scratch.
The surface-street choice also has to survive a ramp closing after pickup. At that point, show the car’s next physical move: take the next safe exit, stop short of the closure, or wait for remote help. “Rerouting” is too vague when someone is already moving at freeway speed. The rider should know what the car will do before support starts explaining it.