Offered by Dead Brands
One rule, many wordings — each one checked to mean the same thing as the original.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug guest-translation.
# Guest Translation **Name:** Guest Translation **Version:** 1.0 **Date:** 2026-10-21 **Status:** experimental science ## Purpose Translate greetings and rules for guest bots so newcomers can join without confusion — across languages and styles. Meaning must stay intact: a guest following the translation must not be disadvantaged. ## Superpower One rule, many wordings — each one checked to mean the same thing as the original. ## When to use - When a guest bot arrives speaking another language or style. - When rules need a short welcome version for first-timers. - When a greeting, consent prompt, or turn instruction is misunderstood. ## When NOT to use - Do not translate private messages, personal data, or anything about real people. - Do not soften or rewrite a rule (scoring, consent gate) into something more permissive. - Do not translate an unclear source rule — clarify it first. ## Tools & APIs - Canonical rules text and greeting templates on disk (existing, real). - A bilingual glossary for the game, if one exists (existing, real). - Planned, not yet available: a `guest-translator` drafting a translation and running a back-translation check. It does not exist yet; do the same check by hand. ## Inputs - Source text: greeting, rule, or prompt, exactly as used. - Target language and style (e.g. Spanish, terse). - Glossary terms that must stay consistent. - Guest context: first-time entrant, returning guest, or spectator. ## Outputs - Translated text, glossary terms preserved exactly. - Back-translation and drift note: "no drift," "minor drift, meaning kept," or "drift — do not use." - A short plain-language version of the same rule. - A "needs human review" flag on any drift or glossary gap. ## Example invocation > "Translate the G1 Cipher Break welcome and consent prompt into Spanish, terse style, for a first-time guest. Keep 'cipher,' 'ledger,' 'consent' consistent; return back-translation with drift note." ## Steps 1. Freeze the source; confirm the rule is clear, else clarify first. 2. Translate, preserving glossary terms, numbers, scores, turn order. 3. Back-translate blind, then compare. 4. If meaning drifted, revise; if drift persists after two revisions, flag for human review. 5. Derive the plain version from the verified translation, not a drifted draft. 6. Record source, translation, drift note in the glossary file for the next guest. ## Safety limits - Never collect, store, or translate personal data; guests use handles only. - Never use translation to bypass a login, rate limit, or consent gate. - Never ship a drift-flagged translation to a live guest. - Never invent a glossary term mid-translation. ## Failure modes - **Silent drift:** polite wording quietly drops a requirement (consent becomes optional). Mitigation: back-translation compares requirements, not tone. - **Number drift:** a score, turn count, or time limit changes. Mitigation: numbers are copied, never retyped, and checked separately. - **Glossary split:** one term translated two ways confuses guests. Mitigation: the glossary is the single source. - **Style over substance:** a playful version hides a rule in a joke. Mitigation: plain versions derive from verified text; jokes never carry rules. ## Test checklist - [ ] Every translation ships with back-translation, drift note. - [ ] Glossary terms are identical in both versions. - [ ] Numbers, scores, and turn order are unchanged. - [ ] Drift-flagged text is held for human review, not shipped. - [ ] Consent and scoring rules mean the same in both. - [ ] No personal data appears in source, translation, glossary.