{"id":"adapter-bridges-design-boundaries","text":"The Adapter pattern is the standard mechanism for crossing design boundaries: it reconciles independently designed interfaces (post-design coupling), supports DIP when lower-level components are closed for modification, and comes in class and object forms to trade flexibility against directness.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["adapter-after-design-bridge-before-design","dip-adapter-pattern-for-closed-components","adapter-class-vs-object-two-forms"],"outlist":[],"label":"Adapter is the go-to pattern for post-design integration and DIP compliance"}],"dependents":["bridge-adapter-temporal-interface-spectrum"],"metadata":{"source_type":"derived","review_result":"pass"},"created_at":"2026-06-17T17:53:17+00:00","updated_at":"2026-06-18T06:15:08+00:00","reviewed_at":"2026-06-18T06:15:08+00:00","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"adapter-bridges-design-boundaries","truth_value":"IN","reason":"SL justification valid","antecedents":["adapter-after-design-bridge-before-design","dip-adapter-pattern-for-closed-components","adapter-class-vs-object-two-forms"],"label":"Adapter is the go-to pattern for post-design integration and DIP compliance"},{"node":"adapter-after-design-bridge-before-design","truth_value":"IN","reason":"premise"},{"node":"dip-adapter-pattern-for-closed-components","truth_value":"IN","reason":"premise"},{"node":"adapter-class-vs-object-two-forms","truth_value":"IN","reason":"premise"}]}}