Skip to content
EN FR

Model Files

Documentation status: guide — see Maturity and evidence.

Model files describe executable application metadata. The editor should help author and validate them, but the Runtime contract remains authoritative.

Editing rules

  • use stable project-owned classId values;
  • keep one clear conceptual responsibility per model;
  • declare concepts, roles, facets and capabilities explicitly;
  • use supported YAML/XML forms rather than editor-specific shortcuts;
  • validate model syntax and semantic resolution before debugging publication or persistence;
  • keep implementation/backend choices out of domain meaning.

A model becomes part of the application only when it is reachable through the package/manifest loading chain.