Skip to content
EN FR

Application Layer

Documentation status: architecture — see Maturity and evidence.

The application layer assembles packages, concepts, relations, actions, rules, events, views, collections, processes, and services into an executable application.

Role

An application selects and configures what must be loaded and executed. It must not duplicate business meaning already carried by the models.

It provides, in particular:

  • a deployment boundary;
  • package composition;
  • a Runtime context;
  • persistence and service choices;
  • activation policies;
  • integration and publication points.

Architectural rule

Business meaning belongs to concepts, relations, rules, actions, and processes. UI renderers, transport DTOs, endpoints, and database details remain projections or adapters.

This separation allows UI, transport, or execution topology to evolve without rewriting the business model.

  1. declare concepts and relations;
  2. add rules, actions, and events;
  3. define persistence and views;
  4. compose the package;
  5. select the Runtime and services;
  6. publish only the required capabilities.