DavidAgents

DavidAgents — Cortex

DavidAgents · Knowledge and memory

How your agents remember.

Every conversation, document and decision your agents touch becomes knowledge the whole team can recall — durable across restarts and model swaps, pruned and distilled while you sleep, and scoped so an agent only ever remembers what it is allowed to know.

The problem

An agent that forgets at midnight is a temp, not a colleague.

Most agents start every conversation from zero: no memory of the customer, the last decision, or the lesson from the mistake last week. Real staff compound. Cortex is the layer that lets agents remember what happened, know what the company knows, and get better at the job the longer they hold it.

Here's what every page on this site is really about: this whole company — every product line on it — was built and is run by one founder and his agents, on the platform you're reading about. That team is the proof it works. What we sell is the same leverage, priced so anyone can have it — because how good you are should decide how far you go, not your software budget. Why we build this way →

Capabilities

Durable memory

They remember — and they get better

Per-agent memory survives restarts and model swaps. Nightly cycles prune stale context and distill lessons into what the agent actually needs next time. Your agents on day 90 know things your agents on day 1 did not.

● memory-over-time proven on the live wall

Company knowledge

What the company knows, findable by the team that needs it

Documents, wiki pages, past conversations and decisions are indexed and searchable — by meaning, not just by keyword — and handed to an agent mid-turn when it matters, so the answer reflects what you already know.

● agent recall runs on it daily

Typed memory

People, deals, decisions — as a graph, not a pile

Memory is typed: an entity, a relationship, a decision with a date and a reason. Agents can ask "what did we decide about this customer and why", and the answer is a record, not a guess.

● the customer 360 our agents read is this

Scoped and evaluated

Remembers only what it may — and is scored on it

Memory is scoped by tenant, agent and role; a support agent does not recall the finance thread. Recall is evaluated on real outcomes, so a memory that misleads gets pruned and one that helps gets kept.

● evals run on it daily

What's inside

The manifest.

  1. 01 Per-agent durable memory survives restarts and model swaps
  2. 02 Dreaming cycles prune, distill, keep what matters
  3. 03 Knowledge search documents, wiki, conversations — by meaning
  4. 04 Typed memory graph entities, relationships, decisions
  5. 05 Mid-turn recall the right history folded into every answer
  6. 06 Scoping tenant, agent, role — never across the wall
  7. 07 Evaluation loops recall scored on real outcomes

How it lands

Connect what you know

Your wiki, files, mail and CRM become the first knowledge the agents can recall — with the scopes you set.

Let them work

Every conversation and decision lands in memory as it happens. Nothing to export, nothing to remember to save.

Watch it compound

Nightly cycles distill lessons; evaluations keep the memory honest. The team gets better at your business by holding the job.

Proof

On duty for us, right now.

The memory our agents recall from, the knowledge base behind the chat on this site, and the evaluations that keep both honest run on Cortex — the same layer we sell.

— checks passing on this line — failing last full run —

Put Cortex on your payroll.

Same platform we run our own company on. First line is a purchase — the second is a decision.

See what they remember