---
name: tbt-multilingual-message-ambiguity
description: "Use a glossary and qualified review rather than inventing a confident equivalence for Draft a multilingual message while keeping ambiguous terms visible. Use permitted source material; this kit does not authorise external actions."
---

# Draft a multilingual message while keeping ambiguous terms visible

Use a glossary and qualified review rather than inventing a confident equivalence.

Use the supplied source as authority. Check the account supports the actual file or image operation before attempting it.

## Task instruction

Draft this supplied message in [target language] for [audience/purpose].
Use this approved glossary and preserve names, figures, dates and
conditions. Identify ambiguous terms before choosing their meaning.
Ask focused context questions or retain a labelled placeholder when
needed. Provide the translated draft, term map and review questions.
Do not invent facts, strengthen commitments or claim professional approval.

## Source boundaries

- Charge: fee or battery?
- Release: software, publication or dispatch?
- Context not supplied

## Review and correction

A fluent translation can silently choose the wrong meaning. Ask the focused source question before translating.

The draft translated [term] as [chosen meaning], but the supplied
context means [confirmed meaning] / remains unresolved. Correct that
term and affected sentence while preserving facts and conditions.
Keep protected names unchanged. Retain a review question if the source
still does not establish the meaning. Return the draft and updated term map.

Use references/practice-source.json for the labelled example. The practice HTML is a local teaching tool; it does not call an AI service. Apply this method to the user's supplied facts rather than copying fictional example values. Do not infer approval or permission to publish.