Status: IN
Adapter and Facade, as complementary interface-boundary patterns operating at different scales (one-to-one post-design vs. many-to-one by design), establish abstraction boundaries that can align with the Dependency Inversion Principle. To the extent that higher-level modules depend on the abstractions these patterns provide rather than on concretions, this alignment supports the conditions that DIP requires — and since DIP is a prerequisite for OCP, these patterns may indirectly facilitate systems that are open for extension without modification.
Boundary patterns are the concrete mechanism by which DIP's abstraction requirement is fulfilled at system interfaces
Depends on (SL): adapter-facade-interface-boundary-pair, dip-enables-ocp