Verifier-First Naming & SDK Alignment
Friday product updates for January 2, 2026.
1 min read
sdkverifiersgraphsnaming
Archive
This is historical material. Use the current Managed Research, Research Factory, and GEPA/GELO pages for product decisions.TL;DR
- synth-ai now standardizes on verifier terminology across SDKs, docs, and configs.
- Canonical judge clients and aliases are removed in favor of
VerifierClient. - Graph optimization naming is unified under Graph Opt, and GraphGen paths are the default.
Verifier-First SDKs
Verifier evaluation now goes through synth_ai.sdk.graphs.VerifierClient everywhere. Canonical judge clients and config keys have been removed to reduce ambiguity and keep the API surface consistent.
Naming Cleanup
Across synth-ai and the monorepo, judge→verifier and ADAS→Graph Opt terminology is now consistent. Docs, examples, and CLI configs reflect the new naming so references line up end-to-end.