Entity Memory

An entity keeps a long-term memory that survives across all of its conversations. It decides on its own what is worth remembering, and you can inspect, curate or clean up everything from the Entity → Memory panel.

Memory is always active for a Digital Entity — it comes with the upgrade and cannot be switched off, together with the entity's state, attention and todo list.

Conversations are temporary, memory is not

A conversation is a temporary container — it ends, and some of the entity's own activations happen in conversations you never open. Only what the entity deliberately writes down survives: a durable fact goes into Memory, something to keep in mind right now goes into Attention, and work to be done later becomes a Todo.

So when you tell an entity something lasting, it stores it in the same turn instead of merely acknowledging it:

You: I am the owner of ERP.BG.

Entity: Noted and remembered — you own ERP.BG.

The stored item then appears in the Memory panel as a fact about you, and comes back in later conversations without you repeating it.

Each memory item has:

Examples of what an entity typically stores:

Storing versus recalling

An entity only writes to memory when you actually tell it something new or changed. Questions are not stored:

You: What is my name?

Entity: (searches its memory) You are Ivan Argentinski.

Storing the same knowledge twice is also prevented — if the entity tries to save something it already holds, the existing item is kept and nothing new is created. When the knowledge has genuinely changed, the entity updates the existing item instead of adding a second one, so recall stays clean.

How the entity recalls things

The text of every memory item is semantically indexed at the moment it is stored, so the entity can retrieve relevant memories by meaning, not only by exact words. Each entity keeps its own private memory search — memories are never mixed with other entities or with the shared knowledge indexes. Each item has an indexing state:

Example: you tell the entity "I prefer short answers in the morning." It is saved and indexed immediately, so a later question like "how should you write to me?" finds it right away, without any manual indexing step.

Who a memory is about

Preferences, relationships and observations are always attributed to a person. By default the entity attributes them to whoever it is talking to, so several people can work with the same entity and each gets their own preferences back:

When a memory is about someone else, the entity records that person instead. Facts and procedures usually have no related user at all.

Memories about other people and things

A memory can be attributed to someone other than the person talking:

Either way, you can ask "what do you know about X" and the entity filters its recall to that subject.

What kinds of things it remembers

Memories are filed by kind, and each kind is used differently:

Each memory can also record who or what it is about — a colleague with an Operator account, or any other person, customer, team, project or company by name.

Recent memories come first

Recall favours what is fresh: among memories that match a question equally well, the ones updated most recently are returned first. A strongly matching old memory still wins over a weak recent one, and nothing becomes unreachable with age — for questions clearly about the past, the entity switches the recency preference off.

Managing memory yourself

In the Entity → Memory panel you can search the memory, filter by person, archive or restore items, delete items permanently, and trigger re-indexing after bulk changes. Deleting is final — the entity will genuinely no longer know that thing.