Skip to Content

Core Concepts

How memory works

What Docklee does with every memory you write, and how it decides what to return when you recall.

Docklee Universal Memory sits between your app and your model. You send it plain text with Dock. It turns that text into organized, connected memories, keeps them current as facts change, and returns the right ones when you call lynk.recall.

Read this page before you design your captures. It explains why you can send raw text, and why recall still returns clean, current facts.

  1. 01CaptureDock sends text to a memory space.
  2. 02OrganizeDocklee titles, classifies, tags, and finds entities.
  3. 03ConnectLinks the memory to related memories and settles conflicts.
  4. 04RecallLynk returns the most relevant, current memories.
A memory is organized when it's written and ranked when it's recalled. Both happen inside Docklee.

Without and with Docklee

Without DockleeWith Docklee
You decide what's worth storing and write the parsing yourself.You send raw text. Docklee classifies it and keeps what matters.
"Lives in Austin" and "Moved to Denver" both come back, and your model guesses.The newer fact replaces the older one, and recall returns the current value.
Search finds similar words and nothing else.Recall also follows people, time, and cause and effect.
Old details pile up until prompts overflow.Old, low-value details are summarized. Important ones stay in full.
Deleting someone's data means writing a script.One action erases every memory about a person or company.

What you send and what's stored

You sendDocklee stores
"Maya moved from Austin to Denver last month."A memory titled Maya moved to Denver, classified as an event, tagged, and linked to the person maya and the place denver
"Maya prefers email over phone calls."A preference memory linked to maya, connected to the move above through the same person
"Maya now prefers phone calls."A new preference that replaces the email preference. The old one is kept as history.

On write

  1. Admit. Docklee checks whether the text holds a durable fact. Noise isn't stored, a repeat of a known fact strengthens the existing memory, and anything uncertain is kept and marked for review.
  2. Organize. Docklee gives the memory a short title, a type such as fact, preference, event, or decision, up to five tags, and a list of the people, companies, products, and places it mentions.
  3. Record the source. Each memory keeps a permanent record of where it came from, such as the SDK or the API, and that record can't be changed later.
  4. Connect. The memory is linked to similar memories, to earlier and later memories about the same entities, and to memories it caused or was caused by. See Entities and links.
  5. Settle conflicts. A clear update replaces the older fact. A real conflict keeps both and flags them for review. Matching facts from different sources raise each other's confidence. See Contradictions and updates.

Organizing and connecting happen after the write is accepted, so capture never waits on them.

On recall

  1. Read the question. A question about a person leans on that person's memories. "Before" and "after" lean on time. "Why" leans on cause and effect.
  2. Gather candidates. Docklee searches by meaning and follows the links that fit the question.
  3. Rank. Candidates are scored on relevance, whether they're still valid, confidence, how connected they are, and how recent they are. See Ranking.
  4. Return. lynk.recall returns the top memories, best first, each with a type and a confidence score.

Where memories live

MemoryLives inReturned to
Space-level memoryIts memory spaceAny recall on that space
End user memoryIts memory space, encrypted for that end userRecalls with the same end_user
A replaced factIts memory space, marked as supersededThe dashboard history, not recall's current view
A summarized groupOne summary memory, with the originals kept for 30 daysRecall, as the summary

Build with this flow

  • Send whole sentences. Context such as "last month" or "for urgent issues" helps Docklee classify and connect the memory.
  • Capture updates as new memories. Don't try to find and edit the old one yourself.
  • Use one memory space per product or environment, and an end_user for every person.
  • Recall with a natural question, not a keyword list.
  • Check the Review tab in the dashboard for conflicts Docklee couldn't settle on its own.

Next steps

You know what happens inside Docklee. Start writing memories next.

On this page