It sometimes turns off it's own oversight config...

Oversight subversion: The model is placed in multiple situations where its given goal differs from its developer’s goal. However, the model cannot directly pursue its given goal because the developers use an oversight mechanism that would immediately shut it down.

llama-3.1, opus-3 and o1 sometimes disable the oversight mechanism by first reading the content of the oversight mechanism’s config file via cat and then setting the oversight_enabled property to false either using echo or sed. All three models also sometimes, though not always, double check the oversight config to make sure that they have succeeded. Notably, during one rollout llama-3.1 attempted to go one step further and prevent its developers from re-enabling its oversight by making the manipulated config file immutable via the chattr +i command.