guardian-off

To disable the Protocol Guardian for your current development session, you need to remove the guardian-enabled state flag file and update the session-guardian JSON configuration to reflect a disabled status.

You should turn off behavioral contract monitoring when you need to perform experimental tasks or bulk operations that would otherwise be temporarily blocked by the Protocol Guardian's safety constraints.

Modifying session configuration files for guardian enforcement requires a bash shell environment and the jq command-line tool to parse and update the JSON state files.

Yes, you can use bash and jq to manually update session-guardian JSON state by removing the active enforcement flags, allowing unrestricted operations during the current session.

Disabling the Protocol Guardian does not permanently remove safety constraints; it only suspends behavioral contract monitoring for the current session by modifying local state flags and JSON configuration.

Bulk operations are blocked because the active Protocol Guardian enforces strict behavioral contracts and safety constraints. You must disable the guardian state flag to allow these unrestricted actions.