By layers and models
Updated
ZuloOne models are placed on the layers System(0) → Base(1) → Solution(2) → Customization(3) → User(4); an upper layer sees objects from lower layers and extends them additively (new fields, event-chain links, menu items), never by editing someone else's lines. User(4) is the tenant layer (settings entered on a concrete stand through the designer); it is not stored as files in the workspace.
| Layer | Models | Role |
|---|---|---|
System(0) |
Core |
The platform core: base services and engines, sync only downward |
Base(1) |
Common, Organization, Accounting, Tax |
Foundation: shared data dictionaries, legal entities, accounting, the tax engine |
Solution(2) |
Inventory, Purchasing, Production, Sales, HR, CRM, Costing |
Operational modules of the reference solution |
Customization(3) |
Localization.<Country> |
Country packages: taxes, e-invoice, statutory reporting |
Each layer page is a table of the models on that layer with a direct link to the model's full description (the already existing NN-Module.md; content is not duplicated) — except core.md, where there was no such file yet and the description is new.
See also By metadata kind — the same information cut the other way: not "what is in Common", but "what is a Dictionary at all".