← Back to concept explainers

Concept Fable

Semantic Memory

Conclusion first:Semantic Memory is facts, concepts, user preferences, business rules, and domain knowledge abstracted from specific events. It differs from Episodic Memory: the latter preserves experiences that occurred one by one, while the former stores reusable, stable knowledge. Enterprise Agents need semantic memory to support personalization, process constraints, customer profiles, and domain Q&A, but they must retain source, confidence, and update time to avoid solidifying an accidental event into a long-term fact.

Semantic Memory · Agent memory

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

The archive that boils old cases into rules

The South City archive has collected countless case files. Each file records who came, what they asked, which document they took, and whether it was ultimately completed. When the curator was young, he believed that as long as the case files were kept complete, later generations would naturally learn how to get things done.

As files piled up, the problem changed too. Every time a new copyist met a client, they had to leaf through dozens of old case files to guess what this type of client usually cared about. Clients grew impatient, and copyists often mistook incidental situations for general rules.

The curator first asked everyone to write summaries on the covers of the case files. The summaries were indeed shorter, but they were still stories case by case: the Zhang family was urgent last time, the Li family was wrong that time, the Wang family once changed its story. The system knew many fragments, but could not state stable facts.

A newcomer once received an out-of-town chamber of commerce. He dug up an old case file and found that the chamber had once required a paper stamp, so he insisted the client wait three days. Only later did he learn that was just a temporary requirement during last year's audit, and now the client wanted an electronic receipt.

The curator realized that past events cannot be directly treated as rules. Experiences need to be abstracted, validated, and updated before they can become reusable common sense for next time.

He had senior transcribers review case files weekly, distilling recurring facts, preferences, terminology, and constraints into a knowledge book, annotated with source, scope of applicability, and last verification time.

The knowledge ledger did not record every quarrel, only stable conclusions: which customers require two-person confirmation, which industries often ask about data retention, which forms must first obtain authorization. If a conclusion came from only a few events, it was marked low confidence.

Later, when the newcomer received the chamber of commerce again, he did not have to dig through the files from scratch. He first read the knowledge book, then reviewed the supporting case files when necessary. His answers were faster, and he less often mistook an incidental experience for a rule. The curator said: the maturity of memory is not memorizing everything, but distilling repeatedly verified experiences into knowledge that can guide the next action. Later, the knowledge book would also expire. If customer habits changed, old conclusions had to be downgraded; only if they remained stable after repeated verification were they promoted to common rules. Memory thus became both fast and not rigid.

Reveal

This story is about: semantic memory

Semantic Memory is facts, concepts, user preferences, business rules, and domain knowledge abstracted from specific events. It differs from Episodic Memory: the latter preserves experiences that occurred one by one, while the former stores reusable, stable knowledge. Enterprise Agents need semantic memory to support personalization, process constraints, customer profiles, and domain Q&A, but they must retain source, confidence, and update time to avoid solidifying an accidental event into a long-term fact.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Rolls of old case files: specific events in episodic memory
  • Cover summary: only compresses events but does not form stable knowledge
  • Treating temporary requirements as general rules: incorrect memory abstraction
  • Knowledge book: semantic memory, storing facts, preferences and business rules
  • Source, scope of application, verification time: governance metadata for semantic memory
  • Look back at supporting case files when necessary: semantic memory and episodic memory cross-check each other
  • Final insight: semantic memory is reusable knowledge distilled from experience

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

long-term memoryepisodic memoryknowledge basememory consolidationuser profileontology
京ICP备2026014272号