The core principle asserts that software abstractions should only be introduced when specific theoretical conditions—namely high coupling or requirements for future variation—are met, rather than being applied preemptively based on design patterns. This mechanism posits that functions serve as sufficient primitives for managing simple state variations (e.g., prompt styles), whereas classes and protocols are necessary to define stable interfaces that decouple system components from volatile external details (e.g., LLM provider SDKs). Within the domain of software architecture, this concept relates to the parent discipline by defining a heuristic boundary between "premature optimization via abstraction" and "necessary structural adaptation," ensuring that complexity is generated only when it reduces overall system fragility.
The core principle asserts that software abstractions should only be introduced when specific theoretical conditions—namely high coupling or requirements for future variation—are met, rather than bei…