Architecture
The implemented architectural principles and module seams of Modeller.
Modeller is organised as a set of deep modules. Each exposes a small, stable interface while hiding parsing, validation, rule evaluation, projection, planning, rendering, output, and integration details.
Implemented foundation
The architecture is behaviour-first, with a Modeller-owned canonical model, typed rule expressions, immutable context snapshots, pure explained evaluation, explicit lifecycle governance, deterministic persistence, and diagrams as projections.
The executable path is:
- Compile RML into the canonical model; SAF remains the low-level engineering format.
- Run staged semantic validation.
- Resolve configuration and a validated template pack.
- Create a deterministic generation plan.
- Render templates through a bounded adapter.
- Preview or safely apply owned output.
- Expose the same contracts through the CLI and editor integration.
Executable conformance, compatibility, security, and explanation evidence guard these contracts. Architecture 101 gives the concise system tour; the architecture decisions record why each boundary exists.
Historical source material remains under legacy drafts and the migration record. It is evidence for the implemented architecture, not competing current guidance.