Type Rules

The behaviour a memory's type governs: whether it can be contradicted, whether it expires on its own, what a correct update does to it, and the query shape that should surface it.

Why it matters in a memory layer

Type is where a memory's whole life is decided, and the load-bearing entry is can_contradict. Only a claim about now can be made false by another claim about now, so almost every mechanism at this level — conflict detection, arbitration, supersession — applies to exactly one of the four types. Getting this wrong routes preferences into a type that never expires, and they then outlive the person's actual preferences.

Connections

Taught in: The Typed Memory Model

Used in: Contradiction Detection · Decay and Memory Tiers · Extraction Pipelines · Hybrid Ranking · ADD, UPDATE, MERGE, NOOP

Do not confuse with: The Memory Record