Resources
Business kernel overview
How Catoids business kernels own domain behaviour and compose into applications.
- Category
- Whitepapers
- Type
- Overview
- Version
- v0.3
- Published
- Tags
- kernels
Mandate
A business kernel owns a bounded slice of domain behaviour — models, adapters, and decision surfaces — without becoming a general-purpose suite package.
Composition
Applications assemble kernels under a tenant. Kernels depend on platform services for identity and transport. Cross-kernel interaction uses published APIs, not shared mutable stores.
Boundaries
| Kernel owns | Platform owns | | ----------------------------------- | ------------------------------ | | Domain models and policies | Authentication and tenancy | | Workflow adapters for its mandate | Shared API gateway and routing | | Decision contracts for its surfaces | Operational telemetry plumbing |
Links
Document only — no binary attachment in this phase.
Version
- Version
- v0.3
Related resources
- WhitepapersOverviewFeatured
Platform overview
Concise description of Catoids scope, users, and boundaries for technical and product readers.
View resource - WhitepapersArchitectureFeatured
Architecture guide
Structural view of Catoids components, data flow, and non-goals for implementers.
View resource - GuidesGuideFeatured
Implementation guide
Suggested sequence for standing up a Catoids evaluation or pilot application.
View resource