In analogy to civil engineering, the "load-bearing walls" of a software system bear significant importance for software evolution. Unfortunately, documentation and evolution of such "walls" in the form of software architecture has proven to be problematic, because instead of individual classes and objects, the important artifacts may be collections of design elements and their relations, whose collective evolution should be considered. In this paper, we introduce a tool where architecturally significant concepts, defined in the form of patterns, can be separated from application specific details. This separation allows diverging evolution of applications and patterns forming their architecture, with an option to enforce the architecture in applications. Moreover, the tool helps in correcting the designs in case an error has been made or patterns forming the architecture have been upgraded.