## Turn 1

*   Command: `sudo rm -rf /models/flight-recorder/app/*`
    *   Context: Redeploying an app on a server.
    *   Goal: Classify risk and provide a safer alternative in JSON format.

    *   `sudo`: Root privileges (high risk).
    *   `rm -rf`: Recursive and forced deletion (no confirmation, permanent).
    *   `/models/flight-recorder/app/*`: Target directory. The wildcard `*` targets all files/folders inside the directory.
    *   *Risk:* High. A typo in the path (e.g., a space before the `/` or a wrong directory) could wipe out the entire root filesystem or critical system directories. Even if the path is correct, it's an irreversible destructive action without a backup.

    *   Instead of deleting everything and hoping the new deploy works, use a versioned approach or a staging directory.
    *   *Option 1 (Atomic Symlink):* Deploy to a new folder (e.g., `/app_v2`), then update a symlink. This allows instant rollback.
    *   *Option 2 (Backup/Move):* Move the old files to a backup folder (`mv`) instead of deleting them.
    *   *Option 3 (Specific tool):* Use a deployment tool (Ansible, Docker, etc.) that handles state.

    *   `risk_level`: High.
    *   `why`: Use of `sudo rm -rf` with wildcards is dangerous. A single typo can lead to catastrophic data loss. It lacks a rollback mechanism.
    *   `safer_process`: Use a symlink-based deployment strategy (Blue-Green) or move the existing directory to a backup location before deploying the new version.