3 ms·
The blog post already explains this. > Automatic Failover to a neutral state if the AI control system does violate safety constraints. Smooth Transfer during f
by Ajedi32 8y ago
The blog post already explains this.
> Automatic Failover to a neutral state if the AI control system does violate safety constraints. Smooth Transfer during failovers to prevent sudden changes to the system. Rules and heuristics as backup if we need to exit AI control mode.
- candiodari 8y agoThat'd just be one automatic system attempting to compensate for another going offline. Same question poses : what guarantees are in place to force maintenance of the second system (the one that never runs, except in exercises or disaster) ? How long until management demands the datacenters work with cooling that just provides, say, five nines of cooling capacity ? Can you guarantee that doesn't happen ? Do engineers at Google even care that that doesn't happen ? In other words, how long until Google loses the ability to pull the plug on this system from a physical perspective ? How long until Google loses that ability from an economic perspective (that turning it off would incur unacceptable costs) ?
- Ajedi32 8y agoYou keep it maintained the same way you keep any other backup system maintained; with regular tests. And if it ever reaches the point where the AI system is so reliable that they're comfortable ditching the backups, I'd call that a win.