Recipes / Quality

Translation Quality Strategy

A practical guide to dialing in Meridian translation quality for production workloads. Covers domain glossaries, confidence thresholds, and human-in-the-loop review patterns that scale from prototype to global launch.

1. Pick the right quality tier

Meridian exposes three tiers: draft, standard, and premium. Draft is throughput-optimized for bulk content. Standard is the default for user-facing strings. Premium routes through the adaptive ensemble and is appropriate for marketing copy, legal text, and any string a customer will read more than once.

2. Attach a domain glossary

Domain glossaries lift quality more than any model swap. Upload a CSV of source-target term pairs via the dashboard or the SDK, then reference it by ID at request time. The router pins glossary matches before sampling, so brand names, product SKUs, and regulated phrases never drift.

3. Gate on confidence

Every response carries a confidencescore and an alternatives array. Route anything under 0.85 to a human reviewer queue. In practice this catches the long-tail idioms and ambiguous source strings that otherwise leak into prod.

Example request

// Meridian translation quality config
import { translate } from '@meridian/sdk';

const result = await translate({
  source: 'en',
  target: 'ja',
  text: 'Whisk eggs until frothy.',
  domain: 'culinary',
  quality: 'premium',
  glossary: 'baking-terms-v3',
});

console.log(result.confidence); // 0.97
console.log(result.alternatives); // [...]