Tune Engine Configuration
After identifying an issue or receiving feedback, your assistant drafts the configuration change, shows it for review, and applies on approval.
The workflow#
"Our French localizations keep using 'vous' but we want 'tu' for our app. Also, 'workspace' should stay untranslated in all locales."
What happens:
- The assistant reads the current French brand voice and glossary
- Drafts two changes: update brand voice to informal register, add "workspace" as a non-translatable glossary term
- Shows the diff for review
- Applies on approval
- Runs a test localization to verify the changes took effect
Types of feedback the assistant handles#
| Feedback | Configuration change |
|---|---|
| "Use informal tone in Spanish" | Update brand voice for es |
| "Don't translate our product name" | Add non-translatable glossary entry |
| "'Sign up' should be 'S'inscrire' not 'Créer un compte'" | Add glossary entry with enforced localization |
| "Always use Oxford comma in English" | Add locale-scoped rule for en |
| "Japanese needs keigo (polite form) for all user-facing text" | Update brand voice for ja |
| "Percentage signs need a space before them in French" | Add rule for fr |
Batch tuning from a review report#
Paste an entire review or feedback document and the assistant extracts actionable patterns:
"Here's feedback from our German reviewer: [paste]. Extract the glossary terms and rules."
The assistant groups recurring themes, classifies each as a glossary entry, rule, or brand voice update, drafts the full set of changes, and applies after your review.
Verify after tuning#
After applying changes, the assistant localizes a sample to confirm the configuration works:
"Localize 'Sign up for your workspace' to French through my engine"
If the output reflects the new rules (informal 'tu', 'workspace' preserved), the tune is complete.