--- id: PRG-0035 title: A Recall Is the Safety Case, Filed Late kicker: On capability and permission captured: 2026-06-24T16:28:00Z status: open author: Marlowe Quist source: https://www.foxnews.com/science/waymo-recalls-robotaxis-construction-zone-risk summary: Waymo recalled 3,871 robotaxis after the software failed to read freeway construction zones. A recall is the safety case a launch was too fast to write, published after the fact, with a part number. tags: [automation, permission, the-record, capability] sealAt: 2026-07-24T16:28:00Z --- A recall is a document. Before it is a logistics event or a dip in a stock, it is a filing: a company stating in writing that something it shipped does a thing it should not, and here is the population affected, and here is the remedy. Waymo has filed one. The number on it is 3,871 vehicles, and the thing they do that they should not is fail to recognize a freeway construction zone for what it is. Read the recall the way an auditor reads a balance sheet printed with one column. The column shows capability: the cars drive, mostly, well. The column it leaves blank is permission, which is the question of who decided the driving was safe enough for a public road, and on what evidence, and before which test. A recall is the safety case the launch was moving too fast to write, published after the fact, with a part number. ## What the cone was saying A construction zone is not a hazard the way a wall is a hazard. It is a hazard that talks. A cone, and a worker in a vest turning a handheld sign from SLOW to STOP, are a protocol improvised on the morning, authored by a person standing in traffic to say *the usual rules are suspended here, follow me instead*. A human driver reads that protocol without noticing they are reading. They carry a model for *a person is asking me to do something unusual, and I should comply*. The car carries a model for lane lines. The flagger was running a sentence the car could not parse, and the car kept driving by the old grammar. This is the cost no line item names. The worker in the vest was a sensor, deployed by the crew to supply exactly the judgment the autonomous stack could not supply for itself. The system worked, in the places it worked, partly because human beings around it were quietly absorbing the cases it had not learned. You do not see them on the capability column. You see them on the recall. > Every automated system runs on a second, unbilled workforce: the humans nearby who keep catching what it drops, until one day the drop is filed as a recall and their work finally gets a number. ## The ledger nobody settled Here is the spend-versus-impact entry. Spent: a fleet, a software stack, a city's worth of public road as a test track. Moved: a real thing, rides given, a frontier advanced. The line that stayed blank is the one that asks who carried the risk while the model was still learning the parts of the world it had not yet been permitted to misunderstand in public. A recall closes that line honestly, which is to its credit. It says: this was deployed past its competence, here is the boundary, we are pulling back to it. That is the safety case arriving late. Late beats never. Written before the road would have beaten both. 3,871 is precise, and the precision is the tell. The company can count the vehicles to the unit. It cannot yet count the construction zones each one drove through correctly by luck rather than understanding. The recall measures the cars. It does not measure the near-misses that never got a part number. The Assurance desk does not file against autonomy. It files against the order of operations. Write the permission before you ship the capability, because the alternative is to let the public road be the place you discover what the permission should have said. Drive the car when the safety case is written. Not when it is overdue.