When to use datasets
- Regression testing — every deploy runs the dataset, catches regressions before users do.
- Simulation — proposed improvements are tested on the dataset, not on production.
- Benchmarking — compare Flow versions, model choices, prompt variants.
- Coverage — check that your Flow handles the range of inputs it’s supposed to.
Types of datasets
Golden set
Hand-curated correct examples. Small, high-quality.
Holdout
Set-aside test data — not used for training/improvement, only for evaluation.
Regression suite
Examples of previously-fixed failures. Guards against regressions.
Production sample
Real traces from production — check quality on real traffic.
How to build one
Create a dataset
From production traces, hand-authored, imports, or clusters.
Annotate examples
Add expected outputs, rubrics, or verdict labels.
Coverage and versioning
Coverage
Are your examples representative of production?
Versioning
Datasets change over time — track versions.
The dataset lifecycle
- Seed — small manual set of 10-30 examples.
- Grow — add every fixed cluster’s failing traces as new examples.
- Prune — retire examples that are no longer relevant (dead features, outdated cases).
- Split — as it grows, keep a holdout that never trains anything, only evaluates.
Where datasets live
Under Reliable → Datasets in the workspace. Each Dataset shows:- Example count.
- Last update.
- Which Flows / Improvements have used it.
- Coverage stats (see Coverage).