- Checks
- 6 / 7
- Reward
- 0.86
- Trace
- recorded

Post-training systems
Own how yourmodels learn
Formal Engines expresses a task as an executable environment, then uses its outcomes for training, evaluation, and release decisions.
Explore the systemThe training environment is the specification.
Formal Engines represents a task as executable state, tools, permitted actions, constraints, and success checks. Training and evaluation run against the same versioned definition.
Each rollout returns a score together with the trace and reasons behind it. Those outcomes can train the next checkpoint or remain sealed for evaluation.
- Task world
- Inputs, tools, state
- Verifier
- Checks, judges, outcomes
- Evidence
- Score, trace, version
task answer_with_sources
state query, evidence_set, response
tools search, retrieve, cite
constraint every_claim.has_source
success answer.correct && citations.resolve
Every result remains bound to the environment version that produced it.
- Task set
- sealed
- Evidence
- complete
- Decision
- recorded
One protocol from rollout to release.
Every checkpoint is tested against the environment version that produced its training signal. Changes can be traced to the model, the task definition, or the verifier.
- 01
Specify
Encode tasks, tools, constraints, and the evidence that counts as success.
Versioned environment - 02
Generate
Run diverse model rollouts inside the same controlled environment.
Rollout traces - 03
Measure
Combine deterministic checks with calibrated model judges.
Scores and reasons - 04
Improve
Turn verified outcomes into the learning signal for post-training.
New checkpoint - 05
Release
Test the checkpoint on sealed tasks and record the decision.
Release record
Your task data, weights, checkpoints, and evaluation records stay in your environment.
The entire evidence trail remains portable.
Bring us the task your model must master.
We will help encode it, train against it, and build the evidence required for release.