If workflow decisions live in the route handler, the boundary and policy concerns collapse together.
Naming the pitfall early helps you design tests, reviews, and safer boundaries. Connect the idea to a realistic coding decision so recall is easier when solving similar questions.