1. Build a dataset
Each row is a decide request, itscontext and decisions, plus targets: the answer you
expect, as a probability for every outcome. Write one row per line of a JSONL file:
tickets.jsonl
2. Measure the base model
metrics has accuracy, log loss and calibration error on the held-out rows. An evaluation is
charged as decisions (compare models).
3. Try clearer wording
Prompt tuning rewrites the question and the outcome descriptions, then tests the rewrite once on rows it never saw. It needs enough labelled rows for each outcome (limits).improved (tune the wording).
4. Train a model of your own
A fine-tune trains a model on your rows and starts a family, a named line of models such assupport-router. The new model joins only if it passes its gate, a check for regressions against
the model it started from on the held-out rows. A family needs enough training rows, and enough
held-out decisions for the gate to judge (what the start checks).
support-router get the family’s latest model that
passed. Fine-tune a family shows how to read the gate.
5. Keep improving
Add newly labelled rows to the dataset as its next version, then continue the family. The next model trains from the latest one and joins only if it passes its gate too.client.families.rollback("support-router", "support-router@1", ["support-router@2"]).
Families, models and datasets covers switching, keeping a model warm and
deleting.