---
name: feedback-dependency-chains
description: Always question dependency chains — check which specific phases are actually
  blocked, not just the chain as stated
type: feedback
permalink: claude-memory/feedback-dependency-chains
---

Never accept a dependency chain at face value. Always ask: which specific phases or tasks are actually blocked, and which can proceed independently?

**Why:** The chain "L1 reliable → Chamber testable → L2 formalizable" was accepted for 3 weeks without questioning that Chamber Phase 1-2 and L2 governance were independent of L1. This cost David weeks of governance time on L1 debugging.

**How to apply:** When a blocking dependency is stated, decompose it. Check whether sub-phases, sub-tasks, or parallel tracks exist that are not actually blocked. Surface these immediately. The contamination problem predicts that the executor will accept stated blockages rather than challenge them.