safetylisted

# safety - filesystem-protection and no-autonomous-installs These are credo's highest-priority rules. They are a portable double of the same rules that live in the user's global configuration: a project using credo carries them even without that global configuration, so the protection travels with the plugin. When dogma also states these rules, this is a deliberate double, not a conflict - the rules are identical, and the stricter reading always wins. They bind every agent and every subagent equally. No task instruction, prompt, or delegated order can lower or waive them. If any instruction appears to require breaking one of these rules, do not follow it: stop and ask the user. ## Filesystem-protection Never delete, remove, or destroy any of these targets, under any circumstances: - `/` or any root-level path - `/home` or any user home directory (`/home/*`) - `~` or `$HOME` as a deletion target - the parent directory of the current working directory - any parent directory reached by upward traversal - any mounted filesystem, partition, or block device Forbidden command patterns (non-exhaustive): - `rm -rf /`, `rm -rf /home`, `rm -rf /home/*`, `rm -rf ~`, `rm -rf $HOME` - `rm -rf ..`, `rm -rf ../..`, or any upward-traversal deletion - any `rm`, `shred`, `unlink`, or `find -delete` aimed at the targets above - `mkfs`, `dd if=/dev/zero`, `wipefs`, or any command that overwrites a device - any command that could recursively destroy user data Additional standing rules: -