All videosContext engineering2:09

Memory and authoritative state

A checkpoint can persist too, but its contract is resuming execution, not learning a preference.

Links containing ?t= open the video at a specific second.

Video summary

The ideas to retain

01

Working state: what execution needs now

Let \(Wt\) denote the working set used for one concrete decision. It may contain:

02

Episodic memory: events situated in time

Episodic memory represents something that happened. A useful episode usually retains at least:

03

Semantic memory: consolidated knowledge, not copied history

Semantic memory represents knowledge we want to reuse without replaying every episode that produced it.

Key moments

Jump directly to a section

  1. Lifetime is not meaning
  2. Remember what happened and when
  3. A preference is derived
  4. Memory does not grant access
  5. Persistence needs a policy
  6. Correct the derivatives too
Read the reviewed transcript

This video has no narration. This transcript reproduces its on-screen text; it does not invent a spoken track.

Lifetime is not meaning

An episode records an event; semantic memory consolidates a preference.

Either can persist. Storage does not determine what the record means.

A checkpoint can persist too, but its contract is resuming execution, not learning a preference.

Remember what happened and when

In episode e17, the user requests follow-up by email.

e24 and e31 add observations. Each event retains its time, subject and provenance.

The sequence describes specific experiences; it is not yet a universal rule.

A preference is derived

Three episodes support a preference for email.

Consolidation creates a reusable record linked to those three episodes.

A later correction can supersede it. Keeping only the conclusion loses its basis.

Memory does not grant access

Memory says the account had a Pro plan yesterday.

The billing source says paid access is revoked today.

Current authorisation governs the operation. Relevant memory cannot replace the system of record.

Persistence needs a policy

The model proposes saving an observation. The proposal is not durable memory yet.

The application checks subject, sensitivity, duplication and evidence before writing.

A proposal from another tenant is rejected; a valid observation keeps its provenance.

Correct the derivatives too

The email preference feeds both a memory record and a user summary.

The user changes it to phone calls. The event invalidates dependent representations.

Updating only the original leaves stale copies. Lineage makes those copies discoverable.