domain-application-separation

To separate domain logic from UI orchestration in ClojureScript, move pure business functions and data schemas into domain namespaces while leaving framework-specific UI wiring in the application layer. This enforces domain purity and keeps application code handling UI.

Domain purity in clean-code architecture means business logic namespaces contain no framework-specific orchestration or UI wiring. Domain functions operate only on pure data transformations, making them framework-agnostic and independently testable.

You should refactor re-frame namespaces during architecture reviews when domain business logic becomes entangled with UI orchestration, making testing harder and refactors risky. Splitting them enforces a clear boundary between pure logic and application layer.

Yes, this domain separation approach works when adding new pages in re-frame apps. It provides patterns to place pure domain functions and data definitions separately from application namespaces, ensuring UI wiring stays isolated from the start.

The best way to migrate functions into domain namespaces in ClojureScript is to move pure business logic and data transformations while leaving UI enrichment and framework-specific orchestration in application namespaces. This maintains a strict architectural boundary.

Mixing business logic with UI wiring makes refactoring risky in CLJS because domain code becomes tightly coupled to the framework. This entanglement prevents independent testing and complicates moving functions without breaking application orchestration.