mav-scope-boundaries

You can prevent destructive git operations by applying boundary guardrails that block autonomous actions unless explicit authorization is provided in the issue. This protects production integrity across all workflows.

Yes, you can enforce policy guardrails automatically across all workflows, skills, and agents. This ensures consistent governance by preventing unauthorized infrastructure changes and authentication modifications.

Safe boundaries for autonomous development include hard limits on infrastructure changes, authentication modifications, destructive git commands, and production access. These guardrails require explicit authorization before any restricted action executes.

To authorize a restricted action blocked by production safety guardrails, you must provide explicit authorization directly in the issue before attempting the operation. This allows policy exceptions for specific tasks.

Enforcing hard limits applies automatically to all existing workflows, skills, and agents without requiring individual configuration. This ensures consistent governance and production safety across the entire development environment.

You should use explicit authorization guardrails whenever autonomous AI agents operate near production systems, infrastructure, or git history. This prevents unauthorized destructive operations and protects system integrity.