logic-sandwich

To refactor orchestrator methods, split state gathering, pure intent computation, and side-effect application into a three-layer pattern. This approach maintains top-level module readability by delegating side effects to a dedicated orchestrator.

The three-layer pattern for orchestrator refactoring separates code into state gathering, pure intent computation, and effectful application. This technique preserves behavior while keeping orchestrators clean and decision logic testable.

Extract pure decision logic from a mediator method by pulling it into a pure helper function like decideInputIntent. This isolates decision logic for testing while delegating side effects to a lightweight orchestrator.

You need to separate state gathering and side effects when working with deep-modules codebases where top-level modules must stay orchestrator-focused. This separation enforces testable boundaries and clear naming for complex orchestration methods.

Yes, this refactoring approach works ideally for deep-modules codebases. It enforces using a pure helper for decision logic and keeps side effects in a dedicated orchestrator, ensuring top-level modules remain readable.