Your agent runs the same job a thousand times and ends every one exactly as capable as it started.
The improvement loop runs through you, by hand, in the prompt.

Every mistake the agent makes becomes another instruction in the file.
It grows, and you find out it got too long when rules start being skipped without warning.

The ticket got reopened. The deploy held. The refund went out twice.
That signal sits in your logs and never reaches the thing that needed to know it.

Everyone wants a smaller model tuned on their own traffic.
You need the input, the action taken and what happened next, joined up. Most stacks keep the output and throw away the two things that give it meaning.


The path from a bad run to better behaviour goes through a person, every time.

Prompt archaeology
Six months in, nobody remembers why half the instructions are there. Removing one is a gamble nobody wants to take, so the file only ever grows.

Evals for the failures you noticed
You write tests for the problems you caught. The ones that slipped past never get written, which is exactly the set you needed.

A training set you never kept
Tuning needs the input, the action and the result, joined up and labelled. By the time you want it, you have logs of the output and no way to score them.







Across agents, models, and teams.