Translation rules

Write reusable instructions, select predefined conventions, and keep shared requirements consistent across requests.

A translation requirement often concerns a relationship rather than a word: keep a variable intact, preserve a qualification, or use the right form of address for the audience. Rules express instructions that recurring translations should follow.

In the Studio 2.5 navigation, open Studio 2.5 → Knowledge → Rulesets. Otherwise, use the corresponding section in Infrastructure. Existing resource links still work.

A ruleset is an organization-owned collection of named rules. Each rule contains instruction text and target-locale scope. Attach the ruleset to the localization engines that need it, so several workflows can use the same requirement.

Express a requirement precisely #

Name the rule so another person can understand its purpose, then describe observable behavior. “Preserve {orderId} exactly, including its braces and casing” gives the model and reviewer a clearer requirement than “Handle variables correctly.” For formal address, include the locale, audience, and situation where it applies.

Use a glossary for product terminology and brand voice for broader style. Keeping those roles separate makes contradictions easier to find. When the requirement affects acceptance, define a measurement for the result as well as an instruction for generation.

Choose predefined or custom guidance #

The predefined catalog supplies curated conventions through the API and account MCP. Inspect an entry's name, description, category, and locale to understand its purpose. The catalog does not expose its server-side prompt text, and its API operations do not imply a dashboard catalog editor.

Alternatives in the same locale and catalog group are mutually exclusive. Choose the convention intended for that work. Setting predefined selections replaces the selection as a set, so include every entry that should remain selected.

For a requirement outside that baseline, create or choose a custom ruleset, save the rule text and locale, and attach it to the intended localization engines. Read back both the rule and the attachment: saving the resource and attaching it are separate operations with separate permission checks.

Understand which instructions combine #

All matching rules accumulate. A wildcard instruction and a matching regional instruction can both enter the prompt; the regional instruction does not erase the broader one. Predefined guidance precedes custom instructions, allowing custom material to refine the baseline. That order expresses priority to the model but does not resolve every contradiction reliably.

If the output violates a rule, check its saved text, engine attachment, and locale matching, then look for conflicting rules, terminology, or voice. Context retrieval explains how to compare that guidance with the submitted context and output. Narrow or remove a conflict before making the instruction longer.

Change the shared requirement deliberately #

Check the attached localization engines before editing a ruleset. When only one workflow needs a different convention, give it a separate resource or detach the existing one. Per-resource grants can provide access to one ruleset, but broader organization permissions remain additive; see Roles and permissions.

Detach to stop one localization engine selecting the ruleset. Remove all attachments before deleting the shared container. Deleting a localization engine preserves the ruleset.

Rerun a representative source and locale after an edit and compare the output with the saved instruction. Earlier translations do not regenerate when the rule changes. Decide which corrections become rules explains when a valid correction is broad enough to become a requirement for later work.