Drafts, Judges and Model Versions

Part of Route.

Drafts, Judges and New Models

A judge decides whether a draft needs escalation

1. DraftThe selected worker completes the brief.
2. →JudgeCompare the draft with the brief and its checks.
3. →Choose the next step
   • ACCEPT: the orchestrator verifies the accepted draft as it would any delegate.
   • ESCALATE: send the original brief, the judge’s reason and the draft’s checkpoint to the escalation route, or the main agent.

Record the draft and judge outcomes. This path applies only when the picked route has a judge configured.

Some routes draft cheaply first. Bulk edits, implementation and source gathering hand their result to the Draft judge route, a fast model that reads the draft against its brief and checks and either accepts it or escalates it: bulk edits escalate to implementation, implementation to hard problems, and source gathering to deep research. Turn off the route a cascade escalates to and your main agent takes escalated work itself; turn off the Draft judge and those routes run without one. Your agent records a verdict on the judge’s call as well, so you can see in the routes table how many drafts each judge escalated, and whether it is earning its place.

Routes name model families, and each pick uses the newest version your provider offers that we have evaluated. A newer version that has not been evaluated yet is a preview: small tasks try it, so it builds a track record, while medium and large work stays on the evaluated version. Once a preview version’s verdicts hold up, the next recommendations update promotes it. In a routes.toml you edit yourself, [evaluation] preview sets this: trial (the default) as described, hold to keep previews off every pick, or use to take the newest version at once. Picks on a preview version are marked (preview) in their tag.