04 · Keep it current · Every month

A memory that stays current as people and priorities change.

Once a month we go through what your AI got wrong with you, and fix the context behind it.

It follows any of the three formats: the session, the mapping or the build. It is not software.

Every month · After any of the three formats

What you get each month

  • A fix to the context behind each thing your AI got wrong.
  • People set the direction and step in when something is off.

Best when

Your AI reads files that were right once.

  • The price list, six months stale.
  • The process that changed, the doc that didn't.
  • The onboarding guide nobody updates.

Or your strategy or your people changed since the files were written.

How the review runs

Each month starts from real answers: what your AI got wrong since the last review.

Then we fix the context behind it, so the answers stay on point.

Why every month

Written down does not mean up to date.

Context does not stay current on its own. It stays that way because someone keeps it fresh, keeps it findable, and keeps it answerable. That upkeep is the work.

Dark context is what you never wrote down. Gray context is what you did, that quietly went out of date.

Gray is worse than dark. It looks current, so you trust it, and you act on it.

A customer asks your AI what onboarding costs. It answers instantly, confidently, with the exact figure from a deck uploaded in March. The price changed in May. Nobody lied. The archive did.

ask > What does onboarding cost?

darkNothing useful. It never saw your price list, so it makes something up.
grayThe figure from the deck uploaded in March. Confident, exact, and out of date since May.
greenThe price since May. Current, and you can see where it came from.

Fast layers make your AI current. Slow layers make it sound like you.

The aim is green context: current, findable, and you can ask it.

Practical

  • Every month.
  • In English or Swedish.
  • It follows any of the three formats.

Questions about the review

Can we start with the review?

No. The review follows one of the three formats: the session, the mapping or the build. It keeps current what those formats wrote down.

Who keeps the context current between reviews?

A named owner in your team. The mapping ends with one. Without an owner, context drifts out of date because no one keeps it fresh.

Does all our context need a check every month?

No. There is no universal refresh rate. The kinds of context inside one company decay at very different speeds. Some rot in weeks, some hold for decades.

How long does it run?

For as long as people and priorities keep changing.

Keep it current.

Tell us which files your AI reads today, and when someone last checked them.

How it works

How the formats work →

The three parts, the two ladders, and why a room.