Thanks — "control flow decision, not a tooling decision" is a better way to put it than I did, honestly. I'll probably steal that framing next time. The "start with the simplest abstraction" rule of thumb is a good one to name explicitly too. I've seen (and been guilty of) reaching for LangGraph on day one because it's the newer/cooler tool, then realizing three weeks in that the workflow never actually branched — just added state-management overhead for nothing. Curious if you've run into the reverse case — a system that started as a clean linear chain and then organically grew a branch or two, where it made sense to refactor into a graph rather than start there? That transition point seems like it'd be its own interesting post.