Kernel · kernel
Owner directive (2026-06-12), canonical. "A Cogni is an engine's system-function interface; its kernel is that engine's private runtime and resources." [src: wiki/engines/cognis-and-kernels.md:3] — and per OWNER-2026-07-10: "Define the Kernel (Code), the Cogni (understanding) and the Genome for this." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:473]
Content
A Kernel is an engine's private runtime and resources — the Code axis of the Kernel/Cogni/Genome triad. Each cogni runs on its own kernel; kernels are never shared and never reached into directly: "each kernel is separate … a capability is only live when its Cogni (or an equipped Neuralware) is wired into the loop" [src: wiki/engines/cognis-and-kernels.md:78]. The canonical kernel table [src: wiki/engines/cognis-and-kernels.md:27-34]:
| Engine | Kernel (runtime + resources) |
|---|---|
| sapiens3 | the environments and keys for each datan |
| Atomic Holons | Knowledge Graph + DataLake + Database + Cache |
| CodeLand | the element ladder: SPOT · SITE · DISTRICT · biome · SPACE |
| dwork | the DWork scheduler (cycles / runs / particles / squads) |
| Bastion (over Mainland) | the token controls each host's Backpack and Wallet |
| remotica (over Mainland) | Gateways and access |
The Kernels stage is stage two of the cognitive-loop (Cognis → Kernels → Neuralwares). A neuralware carries only quasi-kernel resources — it never touches another engine's kernel [src: wiki/reference/neuralware-catalog.md:3]. For this instance, the built kernel is kernel-spatial-site (CodeLand District Spatial Site) plus kernel-neural-engine: "prepare the kernel of CodeLand District Spatial Site, and Atomic Holons for the composition of the data, dynamic work for the dynamic system of interaction" [src: ...knowledge-management-and-concept-modeling.md:512].
Known gap (RUN-006): "reference.ts header asserts 'rule/function bodies copied verbatim' but all six kernel source: strings differ from the real ruleset-registry.ts" [src: wiki/engines/cognis-and-kernels.md:129].
Composition
- uses: engine-private resources (env, keys, KG, scheduler, gateways)
- used-by: cogni (each runs on one), cognitive-loop (stage 2), kernel-neural-engine / kernel-spatial-site (instance kernels), genome (bootstraps engines onto kernels), sc-001-kernel-cogni-genome