dcg

<!-- TOC: Core Insight | THE EXACT WORKFLOW | Quick Reference | Safe Alternatives | What Gets Blocked | Anti-Patterns | Configuration | References --> # 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](#the-exact-workflow) | | Find a safe alternative | [Safe Alternatives](#safe-alternatives) | | See all CLI commands | [COMMANDS.md](references/COMMANDS.md) | | Enable more rule packs | [PACKS.md](references/PACKS.md) | | Configure per-project | [CONFIG.md](references/CONFIG.md) | | Debug hook issues | [TROUBLESHOOTING.md](references/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...