Core concepts
The ideas that make Modeller predictable, extensible, and safe.
Intent before implementation
Modeller starts with the situation a team wants to change, not the implementation someone first requested. An Initiative carries that intent through Discover, Frame, and Shape. System Design is opened only when a selected intervention needs technology.
A system model then describes the business concepts and behaviours that must survive changes in frameworks, storage engines, interfaces, and AI providers.
The ubiquitous language is the canonical, easy-to-find vocabulary for those concepts. Documentation, architecture, model files, and eventually code use the meanings recorded there.
Templates realise architecture
Template packs turn the model into a chosen software structure. They encode team conventions once and apply them consistently across generated outputs.
Generated code has explicit ownership
Modeller only replaces files designated as generated. Handwritten extensions stay separate, making regeneration routine rather than risky.
AI is an adapter
AI can propose questions, interventions, modelling changes, and explanations, but it does not own the Initiative or domain model. Every workflow remains usable without an AI provider, and people accept the durable decisions.