The Deployment Plan That Ignored Its Dependencies
### 09:12 · Release controller paused A fictional release planner confused catalog display order with dependency order. Repair one Python function to return a complete topological plan, reject unknown prerequisites and cycles, and preserve the input.
Learn: directed dependency graphs, topological ordering, fail-closed validation and deterministic regression tests.
The monitor is a dry run; no infrastructure is deployed. Passing proves this planning contract, not transactional deployment or service readiness.
Skills you'll prove
Interview Tip
I modeled task prerequisites rather than relying on catalog display order. I validated references and rejected any graph that could not produce a complete topological plan. I tested shared dependencies, disconnected tasks and cycles while preserving the caller’s data. Safe planning does not itself make deployment atomic or guarantee readiness.