The model in the repository is developed and used jointly. Due to the many connections between the elements in the model, an adjustment to the model almost always has an effect on sub-models of other modelers. To this end, work agreements and tool functionalities are necessary to make this transparent and to prevent unauthorized model adjustments.

Every element in the repository has a life cycle of creation, use, mutation and archiving, including iterations. Due to the many connections that exist in an architecture repository, every modeler must have insight into the life cycle phase of an entity. To this end, agreements must be drawn up about the use of these elements based on the phase.

The metamodel and the chosen modeling languages are also joint in a shared environment. Therefore, there needs to be agreement on these artifacts within the modeling community. To this end, consultation forms must be set up to obtain and safeguard this agreement. In addition, the metamodel must be consultable by the entire community.

Joint modeling is based on agreements about how the joint model is developed and maintained. To this end, the work processes and agreements must be known to all modelers and the agreements must also be monitored.

The architectural process and products are also joint in a joint environment. Therefore, there needs to be agreement on these artifacts within the modeling community. To this end, consultation forms must be set up to obtain and safeguard this agreement.

The content actually becomes the collective architectural product of the community. That is why quality requirements are imposed on this joint model. To this end, this responsibility must be known to everyone and there must be a role that monitors this responsibility.