Memory
Manage learned knowledge, active model state, and retained memory versions.
Memory groups learned knowledge by memory ID. Each memory maps to a subject in the API. Open a memory to see its active state and version history; each version is encoded in an adapter.
Choose Add knowledge to internalize a passage directly from this page. Try in playground opens a fresh conversation with that memory selected. Learning creates a durable request that you can inspect in Activity.
This is learned model state, not a searchable document store. The page does not retain or reproduce the source passage, offer per-fact editing, or guarantee perfect recall.
Memory list and details
A subject with no active adapter uses the base model. A subject with an active retained version routes new requests to that version. The list shows status, loaded version count, last learned time, and active version. The detail view adds the memory ID, model, retention deadline, and routing behavior.
The listing is bounded to 100 subjects and 50 recent versions per subject. Treat the displayed count as the loaded recent history rather than an unlimited archival count. Keep important release IDs in your own application records.
Version table
Each row shows a version identifier, validation counts, learned time, retention deadline, and a Use version control. The validation fraction describes that candidate's checks, not a universal model score. The retention deadline is confirmed checkpoint metadata, not a permanent-storage guarantee.
The active badge identifies the current route. Newest-created and active are different properties: an automatically conflicting candidate may be newer but inactive, and a rollback may intentionally activate an older version.
Activate a version
Choose Use version for a retained inactive version and review the confirmation. New requests will use it; running requests retain their original adapter. The operation includes the version the console expects to be active, preventing a concurrent route change from being silently overwritten.
If activation conflicts, refresh the subject state and review the other release. Do not repeatedly force the action without understanding which version should win. An expired candidate cannot be activated through the normal control.
Roll back
Select a retained older version and activate it using the same control. Rollback changes future routing. It does not refund learning, delete newer versions, or alter already-completed answers.
For subsequent learning, the rolled-back version becomes the parent of newly admitted internalizations. That matters if you were trying to retain knowledge from a newer release: choosing an older parent can intentionally omit those later updates.
Investigate missing knowledge
First inspect the source job and its activation result. Then compare the subject ID and the inference job's recorded adapter version. An answer generated by an earlier snapshot is not evidence that a later candidate failed to learn.
If the route is correct, run an independent evaluation without the source in context. See Versions and routing, Deploying updates, and Knowledge troubleshooting.