dcg

name	dcg
description	Handle blocked destructive commands and

DCG: When You Get Blocked

Core Insight: Blocks are checkpoints, not errors. A safe alternative almost always exists. Find it before mentioning override.

Constraints

• Never request, generate, or run an allow-once bypass because only the human may authorize and execute the exact blocked command.
• Preserve the user's intended outcome with the narrowest reversible alternative because the guard protects state, not merely command spelling.
• Explain the matched rule and surviving risk before asking for judgment; never retry, obfuscate, or route around a DCG block.

Quick Navigation

I need to...	Go to
Handle a block right now	THE EXACT WORKFLOW
Find a safe alternative	Safe Alternatives
See all CLI commands	COMMANDS.md
Enable more rule packs	PACKS.md
Configure per-project	CONFIG.md
Debug hook issues	TROUBLESHOOTING.md

---

THE EXACT WORKFLOW

When blocked, follow this sequence every time:

1. Run `dcg explain "cmd"` → Understand why (see trace)
2. Check Safe Alternatives table → Use if exists (DON'T mention override)
3. No alternative? → Explain risk clearly, let human decide
4. Human approves? → THEY run: dcg allow-once CODE

Never: Ask for override first. Never retry silently. Never circumvent.