Architecture Guide

This guide describes the architecture of the CIVITAS/CORE platform: how the platform is built, which concepts it applies, and why each decision was made.

The guide has four sections.

Platform Architecture

Several views of the platform. The component view shows the whole system and the areas it is divided into. The domain model gives the entities and their relations. The capability map gives the functions, independently of the technology that supplies them.

The section also holds the rules that apply to every part: the architecture principles, the security principles, the open-source standards and the TR 03187 conformance statement.

Architecture Decisions

Every Architecture Decision RecordArchitecture Decision RecordA document capturing an architecture decision. Each ADR has a stable identifier and short title and is managed through four lifecycle states: Proposed, Accepted, Deprecated and Superseded., accepted or superseded. Each record gives the context, the decision and the consequences, so a reader can follow why the platform is built the way it is.

Platform Concepts

The central concepts that describe the logic of the platform: how a user gets a Permission, how a person is authenticated, and how a model controls the flow of data.

Technical Designs

A logical description of the technical concepts that the platform implements: the message bus, the pipeline engine and model management. Each design shows the components, the interfaces between them, and the decisions they follow.