I actually think this isn't a bad idea. I really don't want an automaker treating consumer updates like a developer repeatedly pushing nearly empty commits to github to get ci green.

At the very least, I want the agency to keep a hold on the update for $N days.

That way, I am more convinced that the software engineers of the car manufacturer won't push any quick fixes that might cause bigger problems later.

In the case of urgent problems, the correct response is to ground the fleet. This will cost the manufacturer money, but I'm a software engineer for long enough to know that a quick fix won't be a safer solution.

> At the very least, I want the agency to keep a hold on the update for $N days.

What is the difference between this and "No Deploy Fridays"?

At the very least, if it touches anything that impacts the driving… maybe?

It’s a 3 ton (+) machine with people paying attention less each passing day. It should be taken very seriously.

A scalable way, and which I believe is in place, is having rules and then periodic audits validates that the controls and processes provide a high degree of assurance of compliance with the rules and regulations.

This seems far better than having an agency ad hoc review every single specific software update to vehicles - would people at the agency review the code? Do they write automation? Do they do manual verification?