Guides  /  Models and routing

Where does the training data for a smaller model come from?

Answer

From the traffic your agents have already handled. Every interaction leaves a record of what was asked and what the model returned. Grading is scoring each of those responses against the criteria you set for a good answer, and the scored records are the training set.

Without a score, prompts and completions teach a smaller model to imitate the larger one, mistakes included. The score is what tells the training which responses were worth imitating.

The mechanism

Grading is what makes the records usable.

Collecting traffic is straightforward. Any system serving agents can log what went in and what came out. A log holds no opinion about which responses were good, and a smaller model trained on all of it reproduces the average of the larger one.

Grading supplies the opinion. Structured output is scored by a rule: a query either parses and returns the right rows, or it does not. Unstructured output is scored by a second model reading the response against criteria you wrote.

The same evaluation decides whether a response was acceptable to serve. Running it produces the quality signal and the training signal at once.

production traffic evaluationgrades every run trainingon graded records shadow runagainst live traffic promoted when quality holds and token use falls
What it removes

Nothing has to be exported.

A stack assembled from separate products has to move this data. The trace lives in an observability tool. The evaluation runs somewhere else. The training job reads from a bucket a pipeline wrote. Each hop is a copy, a schema, a permission boundary, and a bill.

When evaluation, training, and inference run on the same runtime as the agents, the trace the agent emitted is the record used to grade, to train, and to serve. There is no export step, because nothing left.

Akka Verify reads that same record for governance, so training adds no second data-handling surface to review.

The requirement

Coverage matters more than volume.

Enough trafficThe work you want a smaller model to take has to appear in production traffic at volume. Rare paths stay with the larger model.
Evaluations that mean somethingA grade is only as good as the criterion behind it. Where the criterion is vague, the training inherits the vagueness.
Coverage, not volumeTen thousand near-identical requests train less than a few hundred that span the range of the work.
A promotion gateA candidate has to be measured against the incumbent on live traffic before it serves any of it.
Questions

Related questions.

How much traffic is needed before this is worth doing?

The volume depends on how narrow the task is. A well-bounded task with consistent structure needs far less than an open-ended one. The test is whether a sample of the work you want to move is representative of all of it.

Does this need labelled data?

Training needs no separate labelling project. The evaluations that already decide whether a response was acceptable produce the labels as a side effect of running.

What if the incumbent model is often wrong?

Then the grades say so, and the records that failed are not what the candidate trains toward. A model trained on scored traffic learns only from the responses that passed.

Whose data is the model trained on, and where does it run?

You own the model. The model is tuned from an open-weight base inside your own environment, and the weights that result are yours to keep and to move.

On Akka. Evaluation, training, and promotion are capabilities of Akka Optimize.