Kaidera OS
Kaidera OS operational ontology
A documentation guide to the generated Kaidera OS operational ontology: the appliance design, the objects that govern work, and the boundaries between Kaidera OS, Cortex, and OpenKai.
Documentation guide based on the canonical Kaidera OS ontology dated 2026-09-02. The interactive ontology is generated from that source; this guide explains how to use it without changing its generated pages.
What the ontology is for
The operational ontology is the technical map of Kaidera OS. It relates real operating objects to their backing code, tables, endpoints, and interfaces so an operator can trace how decisions, work, security, and delivery fit together. Use the interactive map to explore its architecture, assurance layers, atlas, and individual domain pages.
Current appliance design
The current reference design is a Linux VM appliance with three cooperating parts: a native Kaidera OS console, locally installed harness CLIs, and Cortex services running as Podman containers on loopback ports. The console holds the operator workflow and launches local harness processes; the services retain project, graph, and operational state in named volumes. This is the topology the ontology documents, not a replacement for the installation guide.
Cortex: coordination and durable evidence
Cortex is the coordination and memory layer behind Kaidera OS. It carries project context, decisions, work products, handoffs, evidence, and registry data so worker teams can operate against durable, project-scoped history rather than an empty prompt. Kaidera OS presents and operates that information through the local console while Cortex remains its own open project.
OpenKai: one projection seam
OpenKai is the independent open agent harness and TUI in the reference design. It owns its CLI and TUI, session format, releases, research surface, and provider configuration. Kaidera OS owns the control and management projection that lets an operator use the harness inside the appliance. The boundary is deliberate: the products integrate through a defined seam instead of becoming one codebase.
How this documentation stays current
The interactive ontology is generated from the canonical Kaidera OS ontology document. Do not edit its published HTML pages by hand. When the ontology changes, Kaidera OS regenerates and supplies the complete folder; the website republishes that artifact and this guide is refreshed to help operators navigate the new design.
Website context
Connect this guide back to the product story
The technology docs map links this page to the public technology narrative and helps buyers move from a capability overview into the right operating guide.
Open technology docs map →