Guides
Assembling business kernels
Compose modular kernels that own domain behaviour without collapsing into a suite module.
- Guides
- 1 min read
Scope
Business kernels package models, adapters, and decision surfaces for one domain slice. Prerequisite reading: Core concepts and Modelling a domain.
Kernel mandate
State the kernel's problem boundary in one paragraph. Anything outside that boundary belongs in another kernel or shared platform service.
Composition rules
- Kernels depend on platform services for identity and transport
- Kernels may call other kernels only through published APIs
- Avoid shared mutable databases across unrelated kernels
Configuration ownership
Tenant configuration for the kernel lives with the kernel's admin surfaces. Do not scatter cycle or policy settings into unrelated products.