In the last few weeks I have been involved in some discussion on design such as to software design, if there should be a software architect and if so what his role makes him different from the senior developer. In that context I remembered some Roman texts that describe the architect design as a rolling or a regional temporary law to be followed to keep the project on a common design. I actually like this definition as it allows for other designs if they are in line with the overarching design of the architect.
However the same texts also point out that the law giver should never be the same as the craft man (Faber in Latin), as he is otherwise likely to invalidate the law. As such this differentiation of faber and architectus should hold true in today’s practice.