Define a first version of our Architecture Principles

🧩 User Story

As a project contributor I want to have clear and concise principles for the architecture of CIVITAS/CORE 2, in order to have an outline that enable me to make good architecture decisions in the project.

🎯 Goal & Context

The goal of this issue is to define a set of principles the architecture of CIVITAS/CORE 2 should follow at all time. The should take into account the boundary conditions of the domain, the stakeholders and the requirements. Especially they should foster software development practices and architecture decisions that are in favor of a collaborative open source project which is managed vendor-neutrally, like CIVITAS/CORE is.

🛑 Boundaries & Implementation Notes

The architecture principles should be documented in our documentation. Each principle should have a title and a short description. The principles should not be ranked.

✅ Acceptance Criteria

This issue is considered done when:

• a set of suitable architecture princuples is proposed
• the principles are accepted by the architecture board
• the principles are documented on a page in our documentation