> ## Documentation Index
> Fetch the complete documentation index at: https://klarityai-add-transformation-playbook.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Keep agents current

> An agent built against last quarter's process drifts. Diff it against the Company Brain and refresh what moved.

A build is a product, not a one-time artifact. As the business changes, an agent built against last quarter's process drifts out of step with reality and its accuracy degrades.

## The update step

Point your assistant at a repository of your existing agents and run it against the Company Brain. It pulls fresh process data, diffs it against what each agent was built on, classifies the drift, and proposes the rebuild.

Classification matters here. A renamed field is noise. A new compliance step is not.

```text theme={null}
Our process changed. Run this agent's repo against the company brain and tell
me what's drifted and what to refresh.
```

## Why this compounds

Because [Companion](/transformation/company-brain) keeps running, the Company Brain always reflects current reality. Transformation compounds instead of decaying.

That is also why Discover is worth running on a recurring cadence rather than once. The refresh is only as good as the picture behind it.

<Note>
  [Recent process changes](/tools/observations-and-changes) is the tool your assistant reaches for to see what moved since a given date.
</Note>