Kaidera OS
Cortex memory in Kaidera OS
How Kaidera OS uses Cortex for project memory, registry data, decisions, handoffs, evidence, and boot context.
Based on Kaidera OS Cortex integration architecture and public-safe Cortex memory docs.
What Cortex does
Cortex is the memory and coordination backend for Kaidera OS. It stores project context, decisions, lessons, handoffs, evidence, registry data, and boot context so workers do not operate from an empty prompt each time.
Three-store separation
The system separates project memory, worker registry, and app operations. Cortex memory records project knowledge. The Cortex registry records project and worker identity. The app database records console settings, local overrides, autonomy flags, and run state.
Why separation matters
Separation keeps durable project knowledge distinct from local UI preferences and current run state. It also makes it easier to move, inspect, back up, and reason about the data behind a project.
What workers read
Workers can read boot context, project decisions, lessons, prior handoffs, workspace metadata, relevant docs, graph context, and other evidence made available through Cortex for the selected project.
What workers write
Workers should write meaningful work products, decisions, lessons, evidence, and handoff updates back to Cortex. The goal is an auditable memory trail, not hidden local notes.
Project boundaries
Cortex lookups are project-scoped. A worker should operate as agent@project, using the selected project key and workspace root. If memory appears empty, check the selected project, Cortex health, and workspace root before changing worker behavior.
Operational checks
Use Settings and the Dashboard to confirm Cortex health before trusting graph, history, explain, worker routing, or dashboard counts. A red Cortex state should be fixed before running high-autonomy work.
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 →