Cortex · the company brain

Everything your company knows, in one governed mind.

Cortex is the memory the whole workforce runs on: your documents and data, the decisions people made, the lessons the agents proved, and the Operating Record of everything that happened. Every agent, yours or a vendor's, reads from it and writes to it under audit. It is tenant-exact, encrypted with your keys, and never pooled across customers. Your company gets smarter; nobody else gets your company.

Private alpha · design partners only Tenant-exact memory Your keys (KMS / BYOK) Every read audited Never pooled across customers
01 What it holds

Four kinds of knowing, one memory.

A chatbot forgets the conversation. A framework keeps a vector store. Cortex is what a company actually knows, kept in a form an agent can use and an auditor can trace.

Knowledge

Documents, data and primary sources

Your documents, systems of record and read-only public primary sources, retrieved with citations, so every answer says where it came from.

Skills

How the work gets done here

Reusable recipes the workforce learned on your operation: the way your close runs, the way your intake is triaged, the exceptions that always come up.

Lessons

What went wrong, and the fix

Failures are mined into guidance, proven to lift results on held-out work, shipped as a watched canary, and retired if the lift disappears.

The record

Everything that happened

The Operating Record: every action, decision and sign-off, signed and hash-chained, so Cortex can recall not just facts but what the company decided and why.

02 Who writes to it

Every agent. Every person. Under the same audit.

Cortex is not a side database for one product. It is the shared memory of the whole workforce, and of the people who supervise it.

Lightwork's own departments

Second Shift and Forge packs

Every specialist reads from Cortex before it acts and writes back what it learned, with the entry signed into the Operating Record.

Agents you didn't build

Agentforce, Copilot, in-house, open-source

Through Fleet Governance, outside agents deposit lessons and recall them: roster-gated, Shield-scanned, tenant-bound, with value attributed per vendor.

People

Approvals, corrections, decisions

When a human approves, denies or corrects, that decision becomes part of what the company knows, and the next agent to face the same case finds it.

cortex · write pathoperating record
finance-close · recall: "accruals over $25k need controller sign-off"✓ CITED
copilot-ops-02 · deposit: vendor onboarding lesson✓ ON ROSTER · CLEAN
j.alvarez · corrected redaction rule✓ SIGNED
lesson #418 · held-out evaluationLIFT CONFIRMED · CANARY
lesson #402 · lift gone after 30 daysRETIRED · REVERSIBLE
· agent not on roster · recall ·✗ DENIED

Fig. 03 · A recall cites its source. A deposit is scanned and roster-checked. A lesson has to prove itself and can be retired. An unknown agent gets nothing.

03 How it's kept

Your company gets smarter. Nobody else gets your company.

The data and learning principle is non-negotiable: each customer's usage improves their own isolated workforce, on their own data, inside their own boundary.

Tenancy
Tenant-exact. One tenant's Cortex is never read by, trained on, or aggregated with another's. No hivemind, no telemetry, no pooled data.
Keys
Encrypted at rest with your own keys (KMS / BYOK). One tenant's key can never open another's.
Reads
Every read is audited and roster-gated. Recall is an action that passes the same governance gate as anything else.
Deployment
Self-hosted, air-gapped, or hosted by Daybreak Labs. The same Cortex, the same gates, the same record; you choose where it lives.
Learning
Lessons are proven on held-out work before they ship, watched as canaries, and reversible. The evaluator that scores improvement is held to a locked benchmark, so it can't grade its own homework.
Sharing
Cross-instance exchange is opt-in, operator-run and signed, and carries consolidated lessons only: never raw data, never automatic.
Get started

Give your workforce a memory you own.

Bring one department and the knowledge it runs on. We'll show you what Cortex does with it, and what the record looks like afterwards.