Triage Localization Bugs
When a localization comes out wrong, your assistant can inspect the engine's configuration, identify the root cause, and propose the fix - all in one conversation.
The workflow#
"The German localization of 'data processing agreement' came out as 'Datenverarbeitungsvereinbarung' but our legal team requires 'Auftragsverarbeitungsvertrag'. Why?"
What happens:
- The assistant reads the engine and what it applies - glossaries, rulesets, predefined rules, brand voice, and the model chain for the locale pair
- Searches every glossary the engine applies for the term
- Reports the root cause: "The term isn't in any glossary the engine applies - the model chose a valid but non-standard localization"
- Recommends the fix: "Add a glossary term to enforce the legal team's preferred wording"
- Applies it after you approve
When to use this#
- A user or reviewer reports a bad localization
- You notice inconsistent terminology across localizations
- A locale keeps getting the wrong tone or register
- You want to know which model handles a locale pair and what it falls back to
What the assistant inspects#
| Signal | What it checks |
|---|---|
| Wrong terminology | Glossary coverage - is the term defined in a glossary the engine applies? |
| Wrong tone/register | Brand voice - does the engine apply one, and does it have a variation for the locale? |
| Rule violation | Rulesets and predefined rules - does a rule cover it, and is it scoped to the right locale? |
| Model choice | Model chain - which model handles the pair, and what is the fallback? |
To see what the engine actually received and returned for a specific request, open the request in the dashboard or read it through observability in the API.
Triage → Fix#
Triage identifies the cause. The fix depends on what's broken:
- Missing glossary term → "Add 'data processing agreement' → 'Auftragsverarbeitungsvertrag' to the glossary for
de" - Wrong brand voice → "Update the German brand voice to use formal register"
- Missing rule → "Add a rule for
deabout legal terminology conventions" - Model limitation → "Try a different primary model for
en → delegal content"
Your assistant can apply the fix immediately after you approve it - one conversation from bug report to resolution.