FIG. 09

Eight kinds of memory, one specimen each

Most context tools hold one shape, chunks of text with embeddings, which covers a policy document and none of the rest. Each kind below maps to a concrete store. This is what one record of each actually looks like.

Semanticknowledge graph

Meridian Foods
tier T1
region West
owner priya@

Stable facts about the entities the business runs on.

live

Episodicoperational store

order #4821
placed 19:42
channel web
value 84,200

Time stamped events, with the moment attached.

live

Proceduralskill library

win-back
v 4
steps 6
author ops.lead

How the work is actually done here, versioned.

live

Policypolicy graph

tier1.channel
deny sms
order finance → am
since run #4182

The constraints that are never negotiable.

live

Preferencesknowledge graph

acct 8841
channel whatsapp
window evenings
learned observed

Per entity modifiers learned rather than declared.

live

Decision tracedecision log

run #4182
input 8841, 4d late
action email finance
pack 12 citations

Input state, action taken, and the context that informed it.

live

Reflectivereview queue

correction
by priya@
on run #4182
became tier1.channel

A one line fix, reviewed, becoming a rule the next run inherits.

live

Outcomeoutcome log

run #4182
resolved 31h
baseline 96h
attributed pending

Whether the action moved the baseline it was meant to move.

in build

Adding a ninth kind is configuration, not a migration. The store is named because it has to be queryable and rollback-safe.

Illustrative. The records are invented and shaped like real ones; none came from a customer.