Record the baseline
Store these with the agent’s code and evaluations, so every later review has something to compare against:- The process it was built from, and the version used.
- The evidence behind its behavior: the observations or an evidence summary.
- The policies, dependencies, tools and model configuration it relies on.
- The evaluation set and the release result.
- The owner, and the next review date.
Know when to review
- On a schedule. Set the next review date in the baseline.
- When the process changes. A known change to the process, its owner or its systems.
- As capture comes in. Companion needs to run often enough to cover the processes and exceptions the agent depends on.
- From the change feed. The Within MCP returns recent process changes. It’s a bounded set with no date cutoff, so it doesn’t prove nothing changed before its window.
Classify the change
Start with recent changes, then pull the current details of each process the agent uses and compare them with the baseline. Where behavior matters, look at current observations too: the documented process can stay the same while the way people run it, its exceptions or its systems change.
The classification is your decision, not the tool’s. Confirm material changes with the process owner before you change how the agent behaves in production.
Maintenance review
Decide what’s next
Keep the previous version available, so you can roll back under your deployment controls.
Who does what
Where to go next
Measure the value
Show the agent is still paying off.
Keep agents current (developer docs)
The developer view, with the MCP tools behind each step.
Need help? Use the in-app chat — click the chat bubble in the bottom-right corner of Within (staffed 24×5) — or email support@within.ai.