Deterministic Core, Non-Deterministic Shell

The article proposes "Deterministic Core, Non-Deterministic Shell" as an evolution of the "Functional Core, Imperative Shell" architecture pattern, arguing that determinism rather than pure functional programming is the key requirement for testable code. A deterministic core—whether purely functional or imperative—produces the same outputs given identical inputs, making it easier to test and reason about, while the non-deterministic shell handles side effects like I/O, network calls, and database operations. This approach broadens the applicability of the pattern beyond purely functional languages while maintaining the testability benefits.