Datasets
Real-world engineering tasks, each with a ground-truth answer.
>Fine-tuning (SFT)>Evals
[ Human-authored training data ]
Custom datasets, reasoning traces, RL environments and evals, written from scratch by senior engineers and domain specialists, and tuned so your model solves only 10–30% of them.
Every task is tuned until your model solves it only 10–30% of the time. A task your model always solves teaches it nothing, and one it never solves gives it no signal.
Each column counts tasks by how often your model solves them. Only the green ones ship to you.
142 of 388
36.6% of written tasks ship. The rest go back for a rewrite or are dropped.
Example histogram of tasks by how often your model solves them. Tasks it solves 10–30% of the time ship. At 0%, or at 80% and above, they are dropped. Everything else goes back to its author for a rewrite. 142 of 388 tasks ship in this example.
Every datapoint is created from scratch by senior engineers and domain specialists. Never scraped, never synthetic.
Real-world engineering tasks, each with a ground-truth answer.
>Fine-tuning (SFT)>Evals
Step-by-step solutions from senior engineers, dead ends included, so a model learns how the answer was found.
>Fine-tuning (SFT)>Step-level rewards (PRM)
Runnable tasks that score the agent’s work automatically, with rubrics where a test can’t decide.
>Reinforcement learning>Verifiable rewards
Private benchmarks, graded by experts, for places where public benchmarks are saturated.
>Private benchmarks>Grading rubrics
One example task, tested on a frontier model.
The task is fair to the agent, and your model solves it only 10–30% of the time on the first try.
Two senior engineers or domain specialists review it separately for clarity, correctness, edge cases, originality and difficulty. Both must approve.
The last step before delivery. Only a task that passes it is delivered.
Usually 10–50 tasks. We use it to settle goals, format and difficulty before scaling up.
Scoped on what you’re training for and what model and difficulty to calibrate against.
We settle the schema and QA thresholds with your team.
Senior engineers and domain specialists write each task from scratch, under NDA and work-for-hire agreements.
The three QA layers described above, run against your model.
In your schema (JSONL, Parquet or RL environments), after a final acceptance test.
Your model solves it 1–3 times in 10.
Automated checks, two reviews, an acceptance test.
Written fresh for your project, and never resold.
On us, sent under NDA within 48 hours.
A frontier model has already seen most public text, and training it on its own output repeats its mistakes. New tasks, written by senior engineers and domain specialists, give it material it hasn’t seen.