Privacy and analytics

We use necessary technical cookies and, only with your consent, analytics and marketing pixels to improve the website and measure campaigns.

Privacy policyCookie policy
Docs
English
EspañolEnglishFrançaisDeutschItalianoPortuguês

Getting started

  • What is Nömad?
  • Getting started with Nömad
  • Create your brand and complete the Genome
  • Invite your team
  • Glossary

Brand OS

  • What is inside Brand OS
  • What is the Genome?
  • Who is Nödo?
  • What does a Brand Manager do?
  • Brand Kit and Library
  • Posts and calendar
  • Connections
  • Meetings

Work

  • Work and tasks
  • Ordering work
  • Following, reviewing and approving deliveries
  • Custom quotes
  • Yes, there are humans behind it

Account and billing

  • Plans and pricing
  • Billing and payments
  • Roles and permissions
  • Workspaces and multiple brands
  • Languages, apps and data

Help

  • How to get help

API

  • Brand API

MCP

  • MCP server

Connectors

  • Brand connectors

Nödo and agents

  • Nödo in the brand
    • Memory
    • Widgets
Nödo and agents/Nödo in the brand
Concept1 min read

Memory

What a brand remembers, who decides and how it is searched.

On this page
  • How something becomes memory
  • Search

Updated on January 1, 1970

Previous
Русский
한국어
日本語
中文
हिन्दी
Open the app
Nödo in the brand
NextWidgets

In this section

  • Widgets
Can't find what you need? Write to usWrite to usGo to the app
© 2026 Nömad · Nömad documentationLinkedInInstagramFacebookTikTokYouTubeX
Go to nomad.oooBack to top

On this page

  • How something becomes memory
  • Search

Brand memory keeps what must survive between conversations. It follows the model the large labs have converged on: a small core always present and the rest retrieved on demand, with people deciding what is permanent.

KindWhat it holdsWhen loaded
CoreBrand soul and accepted rules (max 6 KB)Always
Facts and decisionsAccepted assertions with source and temporal validityVia memory.search
EpisodesSummaries of closed conversations and worksVia memory.search
ProceduresKit instructions and brand guardrailsAlways, trimmed
PersonalEach person preferences in the brandOnly in their conversations

How something becomes memory

  1. Nödo or the background extractor proposes a fact or a decision, citing the message, task or file.
  2. Extraction only reads shared conversations; never internal or private threads.
  3. A person accepts, corrects or dismisses it in Genome › Memory.
  4. On acceptance it is checked against accepted memory: what it replaces moves to history with an end date, never deleted.
  5. Accepted memory is indexed for keyword and semantic search.

Search

memory.search combines keyword and semantic search, fuses the results and returns each hit with its source. It accepts asOf to ask what was true on a given date.