CUST.3:10 - Architectural Rationale

The family is defined through common useful result and compatible provision, not one universal implementation layer. This allows technical components, service methods and local contributions to remain distinct while supporting the same customer use.

Constructing before qualifying makes the admission decision inspectable. Retaining local residue prevents the family from becoming a disguised catalogue of every historical customization.