Waymo's recall looks less like a car problem than a software-supervision problem.

The paper's Thursday brief said the 3,791-vehicle disclosure made the recall a fleet census. Friday's companion point is regulatory: the old recall vocabulary is too small for a cloud-updated robotaxi network.

The Next Web described the flooded-road recall as a software fix for robotaxis. [1] Bloomberg reported the underlying incident. [2] Electrek carried the OTA remedy and fleet count. [3] Each account fits the NHTSA format: identify defect, define affected population, describe remedy.

But autonomous fleets do not fail one vehicle at a time. A robotaxi can detect water, classify a road, choose a route, trigger a remote operator, receive a map update, and then carry the same changed rule into thousands of vehicles. The recall document is therefore not just a consumer-protection notice. It is a public snapshot of a software release cycle.

That changes accountability. Regulators need to know not only which cars were recalled, but which model version was running, which hazards were reclassified, and how fast the updated rule reached every operating city.

The car recall is still necessary. It is no longer sufficient. The vehicle is the endpoint; the fleet logic is the product being regulated.

-- THEO KAPLAN, San Francisco