{"id":"facade-asymmetric-subsystem-simplification","text":"Facade establishes an asymmetric simplification relationship: the subsystem remains completely unaware of its Facade (no back-references maintain subsystem independence), and typically only one Facade exists per subsystem (often implemented as a Singleton), creating a strictly one-directional dependency that simplifies client access without introducing any coupling burden on the subsystem itself.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["facade-often-singleton","facade-subsystem-unaware-of-facade"],"outlist":[],"label":"One-way dependency with singleton uniqueness establishes asymmetric simplification"}],"dependents":["facade-implements-asymmetric-dip","facade-mediator-centralization-spectrum"],"metadata":{"source_type":"derived","review_result":"pass"},"created_at":"2026-06-17T23:28:16+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":"facade-asymmetric-subsystem-simplification","truth_value":"IN","reason":"SL justification valid","antecedents":["facade-often-singleton","facade-subsystem-unaware-of-facade"],"label":"One-way dependency with singleton uniqueness establishes asymmetric simplification"},{"node":"facade-often-singleton","truth_value":"IN","reason":"premise"},{"node":"facade-subsystem-unaware-of-facade","truth_value":"IN","reason":"premise"}]}}