Cogni · cogni
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 Cogni is the system-function interface an engine exposes — the understanding axis of the Kernel/Cogni/Genome triad. Every engine exposes exactly one Cogni backed by its own kernel; the cognitive-loop passes through every Cogni in fixed order. The canonical Cogni table [src: wiki/engines/cognis-and-kernels.md:27-34]:
| Engine | Cogni (system function) |
|---|---|
| sapiens3 | Datans — the agents (microservices + API gateways) |
| Atomic Holons | Knowledge Graph with Physics for Loops (everything happens in a Loop) |
| CodeLand | API Gateways for pads · WebServices for pods |
| dwork | Conversion of entropy into Venture & Endeavor structure |
| Bastion (over Mainland) | Identity Tokens — one per host |
| remotica (over Mainland) | Portals → strict, precise Permissions + privacy |
Capability always flows through Cognis, never around them: "n8n never touches a kernel directly — it always calls through the Cogni (the engine's system-function interface). That is what keeps each kernel private and the loop governable." [src: wiki/engines/cognis-and-kernels.md:115] A neuralware is "a plug-and-play Cogni with due source and quasi-kernel resources" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:184].
dwork is explicitly both a Cogni and a Kernel: the Cogni decides what to produce; the Kernel decides how/when to run it [src: wiki/architecture/dwork-cogni-ontology.md:64-76]. This instance's Cogni cards: cogni-spatial-site and cogni-neural-engine.
Known gap (RUN-006): "the unifying per-Cogni micro-kernel is explicitly greenfield-not-yet-built" — DOOIT and the gate are separate mechanisms in the real code [src: wiki/engines/cognis-and-kernels.md:130].
Composition
- uses: kernel (private runtime beneath it)
- used-by: cognitive-loop (stage 1 traversal), neuralware (plug-and-play Cogni), cogni-neural-engine / cogni-spatial-site (instance Cognis), sc-001-kernel-cogni-genome
See also
- kernel — what runs beneath every Cogni
- neuralware — equippable Cognis
- [Upstream wiki page](../../../wiki/engines/cognis-and-kernels.md)