TV4 postponed the Swedish edition of The Challenge until 2027 after a technical failure destroyed edited material. Sveriges Radio reported that the failure may have affected up to five episodes. Sweden Herald, carrying a TT report, said social posts had blamed an AI tool. TV4 denied that an AI robot edited or erased the material.
Attribution can stay disputed. Recovery cannot stay theoretical.
That distinction matters in an agent-driven IDE. A surprising deletion does not prove that the model, the editor, a cleanup script, or a storage fault caused it. The first job is to preserve evidence. The second is to restore work. A blame story does neither.
Undo is not a backup
An editor undo stack lives too close to the action. A repository commit protects tracked source, but it may omit generated assets, local databases, recordings, secrets, ignored files, and unsaved work. A cloud sync client may copy deletion as efficiently as creation.
A useful recovery lane has three separate stages. Capture the source state before destructive work. Put a copy outside the writer's reach. Restore a representative payload on a timer. If the third stage has never run, the organization owns a backup claim, not recovery evidence.
Put the fuse beside the switch
Agents make this control visible because they can cross many files in one turn. The remedy is not a vague warning. Bind destructive actions to a concrete preflight. Record the workspace revision and untracked inventory. Create the recovery point. Confirm that the copy sits outside the same write authority. Then run or schedule the restore check.
CISA recommends offline, encrypted backups of critical data and regular tests of backup availability and integrity in a disaster recovery scenario. That guidance was written for ransomware, but the mechanism applies here. A writer should not be able to erase the source and its recovery copy through one authority path.
The fuseboard below drafts the preflight. It does not test your storage. A green state means the three requirements were selected. Real evidence still needs paths, timestamps, hashes, and a measured restore result.