Back to the blog

AI Governance

Log the Memory, Not Just the Model.

By John Utley

Published

An operator maps the connected stores used by several AI agents.

When a company investigates a bad AI outcome, the first question is usually which model did this. That is necessary and not sufficient. If prompts, retrieval stores, or long-term notes have changed since launch, the model identifier alone will not reconstruct the decision.

Log three things together: the model version, the memory version, and the evidence retrieved for that call. For a forecast, that means the rules and definitions in force, plus the records the system used. For a support or research agent, it means the prompt, the documents it could see, and any memory it wrote back.

This is the monitoring work already implied by NIST AI RMF Measure and Manage, and by ISO 42001 monitoring and continual improvement. It does not require a new framework. It requires a record you can actually produce.

Practical rules: version memory separately from the model. Restrict who can write to slow memory. Review those writes before they affect production. Test a rollback. Write down what would trigger a re-validation, such as a material change to retrieval sources, a spike in exceptions, or a new use case.

If you cannot show, for a past decision, which version of the model and the memory produced it, that is the gap to close first. The learning-loop scorecard asks this directly. A Learning-Loop Audit maps the stores, the write rights, and the missing logs.

Keep reading

Related articles

An operator arranges three layers of agent memory with a visible workflow between them.
AI Strategy

Lesson Promotion: The Review Step Most Agent Teams Skip.

A useful correction is not the same thing as a new policy. Name the person who decides when a lesson may move from a session into durable memory.

Three streams of task records pass through a human approval gate before becoming lasting memory.
AI Governance

Validate Once Is Not Enough: Continual Learning, NIST, and ISO 42001.

Controls written for a frozen model need a second life after launch: versioning, decision logs, and re-validation triggers mapped to NIST and ISO 42001.

An operator maps the connected stores used by several AI agents.
AI Governance

Your AI Will Soon Learn on the Job. Is Your Governance Ready?

Most AI governance still assumes a model that is validated once and then stays still. That assumption will not survive systems that keep learning after launch. Here is what to install now, with the tools you already have.

Three streams of task records pass through a human approval gate before becoming lasting memory.
AI Strategy

Fast, Medium, Slow: A Memory Model for Enterprise Agent Teams.

Long-term memory for agents does not have to mean an unreviewed pile of notes. Separate this task, the daily record, and approved policy, and promote a lesson only after a person reviews it.

Related reading