From model to application
How a model in the hub becomes runnable code: modeling, fetching metadata, generating, project scaffold, and how schema changes run in a controlled way through the MCP server.
Topics in this subject area
- 1.Modeling in the hub
What you define in the hub: system, folder, model, field, relation, rules, endpoints, roles. And which modeling rules apply.
- 2.Code generation in the build
The build fetches the metadata from the hub, stores it as a YAML cache, and generates 15 classes per model from it. This page explains the flow and what is created when.
- 3.The project scaffold
What a new project gets the first time (POM, main class, configuration) and which branches exist, for example CIAS embedded or removed.
- 4.Generated code and custom code
Why generated code is never changed by hand, and where your custom code belongs: hooks, custom filters, custom controllers and services, configuration.
- 5.Schema change through the MCP server
How an AI client changes a model through the hub's MCP server: read, validate the blueprint, plan the change set, approve, apply exactly once.