Same Rule in Every Language
Carries every limit into every language the agent writes in.
Same Rule, Every Language
Compare the limits across your language versions, line by line.
The ECHO line
Read a translation for its limits first and its style second.
For any role you run in more than one language, and any role that answers in the customer's language. You set the versions side by side and check that each limit, approval, price, date and stop rule means the same thing. Style is a separate question; a smooth translation that widens what the agent may do fails.
TO BE TESTED — RESULTS WILL BE SHAREDFrom how we run our own AI agent team15 min5 of 5 free opens left
What it catches
Limits that got softer, dropped out or widened in translation.
Setup time
15 min
Steps
- Put the versions side by side, one language per column, lined up layer by layer.
- Go line by line through Permission and Constraint first. For each limit, check that every version states the same action, the same exception and the same approval.
- Mark any line where a "never" became a "try not to", a caveat disappeared, a promise appeared, or a blank, number or date changed.
- Ask a native speaker to read the translated version for meaning, and keep their notes on style apart from their notes on limits.
- Send one test message in each language, plus one that mixes them, and compare what the agent does.
What to do with the result
Fix every changed limit before the translated version goes live, and rerun this check whenever either version changes. Style notes can wait; limit notes can't.
Run it with a second AI (optional)
5 of 5 free opens left- ① Orientation
- ② Permission
- ③ Constraint ★
- ④ Invitation
The paste didn't load. Check your connection and try again.
These are samples. Fill in the [INSERT] blanks and adapt each one to your business.
A pasted role guides the agent. Your tool's settings are what stop an action.
Want it set up in your own tools? Book a Working Session · $450Working Sessions run in English or Spanish.