Appearance
Definitions and Metadata Collaborators Map
Verified anchorsTemplate interpretation for extension work
Collaborator map
text
NGB.Metadata
├─ DocumentTableMetadata
└─ DocumentColumnMetadata
↓
NGB.Definitions
├─ DefinitionsRegistry
└─ DocumentDerivationDefinition
↓
NGB.Runtime
├─ DocumentService
└─ IDocumentDerivationServiceVerified collaborator roles
DocumentTableMetadata
Structural table description used by Runtime to understand head and part tables.
DocumentColumnMetadata
Structural column description used by Runtime for:
- allowed field checks
- required-field validation
- lookup and options metadata
- DTO metadata construction
DefinitionsRegistry
Immutable registry for:
- document definitions
- catalog definitions
- relationship type definitions
- derivation definitions
DocumentDerivationDefinition
Declarative configuration for platform-level draft derivation:
- source type
- target type
- relationship codes
- optional handler type
DocumentService
Runtime orchestrator that:
- resolves type metadata
- builds effective document models
- validates payloads against metadata
- exposes derivation actions
- delegates draft derivation to derivation service
IDocumentDerivationService
Runtime boundary for:
- listing derivation actions
- creating derived drafts from registered derivation definitions
Execution-oriented reading
The verified-source interpretation is:
- metadata records describe the shape
- definitions registry describes the registered business universe
- runtime services execute against that universe
- derivation service is a runtime action engine driven by definitions
Extension checklist
This is template guidance inferred from verified anchors.
Add a new structural field
Touch Metadata first.
Add a new business type
Touch Definitions and whatever registry/module wiring feeds Runtime.
Add a new “create based on” action
Touch Definitions first via derivation definition, then supply handler behavior if needed.