Platform service

Cortex memory

A plain-language guide to how Cortex helps Kaidera remember projects across long-running work.

Public draft for dev reviewLast verified 2026-05-22

Created from Phase 2 docs inventory and public-safe Cortex memory narrative.

What Cortex memory is

Cortex memory is the project memory layer behind Kaidera. It helps the platform remember goals, decisions, work packets, user instructions, files, evidence, and relationships that matter to the project.

Why it exists

AI work becomes unreliable when each session starts from zero. Cortex memory exists so a project can continue across days, workers, reviews, and changing instructions without forcing the customer to repeat everything.

The six memory views

Users can think of Cortex memory as six views that serve different purposes.

  • Records remember what was said, decided, assigned, completed, or blocked.
  • Recall finds related context when the same idea is described in a different way.
  • Project map helps reviewers understand which product areas may be affected.
  • Knowledge graph connects business concepts, requirements, roles, systems, and decisions.
  • Artifact memory keeps useful files, diagrams, screenshots, and outputs attached to the project.
  • Boot briefing gives a worker or operator the current context before work resumes.

What users should see

Users should see fewer repeated questions, clearer handoffs, better review summaries, and more reliable continuity when a project pauses and resumes.

What to configure

Customer admins and project owners should configure project boundaries, who can access project memory, what knowledge sources are approved, and when sensitive material requires a separate enterprise process.

What to avoid

Do not treat memory as a place to put secrets, unrelated files, or stale instructions. Memory quality improves when the project has clear goals, current source material, and good evidence.

What can go wrong

If an AI worker seems confused, the cause may be missing project context, conflicting instructions, stale source material, or unclear boundaries. Fix the memory inputs before increasing autonomy.

Read next

Read Cortex knowledge graph next if you want to understand how project concepts connect. Read Cortex handoffs and evidence if you want to understand how memory supports review.

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 →