Appearance
Definitions
Verified module boundaryFeature-pack interpretation
File-level companion page: Definitions source map
Verified anchor
NGB.Definitions/NGB.Definitions.csproj
Why this module matters
NGB.Definitions is the place where descriptive model and platform feature packaging come together.
Its verified dependency shape tells us it connects:
- metadata
- accounting
- operational registers
- reference registers
- persistence abstractions
That is exactly what you would expect from the module that packages reusable platform features for runtime.
Working interpretation
Definitions are where the platform answers questions such as:
- what catalogs/documents/reports exist?
- which business engines participate?
- how should runtime see these features?
- what definitions are reusable across verticals?
Use this page together with
Important boundary
Definitions should stay closer to describing and packaging platform features than to executing them. Execution belongs in runtime; storage realization belongs in PostgreSQL.