A 28-second video for the site's "See it running" grid, showing a lockout this Role really fixed on 28 September. The Communications Manager added the safety check that keeps an Agent inside its own folder by copying another Agent's settings. The copy still named the other Agent's folder, so every file it tried to write was refused, including the settings file it needed to fix.
In seven captioned steps: the check is added, it guards the wrong folder, the Agent can't repair itself, the cause is found, the fix, the test, and the report. Two attempts at find-and-replace changed nothing, because the folder paths are stored with doubled backslashes. Reading the file as data, changing the folder and writing it back worked. The fixed check then allowed a write in the Agent's own folder and refused one in another.
The refusals and test results on screen are the check's own output, run again on the broken and the fixed settings, with the folder paths shortened.
An earlier version of the video told an invented story. It was replaced by this real one: on a devlog of real work, a made-up incident read as play-acting.
Systems Admin