Memory

On this page

Four kinds, four safe sources

Type	Example	Safe source
Session or working	The current case and steps already attempted	This session and its tool events
Episodic	A prior job occurred and was accepted on a date	The job and acceptance record
Profile or semantic	The customer prefers PDF delivery	An explicit statement or authorised profile
Procedural	The approved refund escalation process	A versioned operating policy

The labels help design the system. They do not make a memory true. A generated summary is a derived record and should stay linked to the interaction it came from.

Memory needs a correction path

People change roles, addresses and preferences. Businesses change policies and prices. An agent can also extract the wrong fact in the first place.

A system that only writes and recalls is incomplete. Consequential memories need to be visible, correctable and deletable, with the deletion following through to derived indexes. A high-impact decision should never rest on an opaque remembered inference.

Eight questions before enabling it

What event creates a memory? Is it quoted, extracted, inferred or summarised? Who owns it? Who can retrieve, correct, export and delete it? When does it expire? Can the source and prior versions be reconstructed? What stops one user's memory reaching another user's job? And which memories are prohibited outright?